conversion_bridge_meta_event_type

Description

The conversion_bridge_meta_event_type filter allows you to change the event type name used by the Meta Pixel before it renders the fbq() tracking call. This runs after Conversion Bridge has already mapped the internal event type to Meta's standard event name (e.g., form_submit → Lead, purchase → Purchase).

Changing the event type here affects whether Meta fires a standard event (fbq("track", ...)) or a custom event (fbq("trackCustom", ...)). If the returned value is not one of Meta's standard event names, it automatically becomes a custom event.

This filter only affects the Meta Pixel (browser-side). To also change the event type for the Conversions API (server-side), use the conversion_bridge_meta_api_event_type filter.

Usage

add_filter( 'conversion_bridge_meta_event_type', 'my_hook_function', 10, 3 );

add_filter( 'conversion_bridge_meta_event_type', 'my_hook_function', 10, 3 );

Parameters

1. $event_type (string) The Meta event type name after Conversion Bridge's mapping (e.g., Lead, Purchase, ViewContent)
2. $event (array) The original event data array from Conversion Bridge
3. $track_method (string) The current tracking method — standard or custom

Example

Send form submissions as a custom event (custom_form_submit) instead of Meta's standard Lead event. This is useful when you want to distinguish Conversion Bridge form submissions from other Lead events in your Meta reporting:

add_filter(
    'conversion_bridge_meta_event_type',
    function( $event_type, $event, $track_method ) {

        if ( 'Lead' === $event_type ) {
            return 'custom_form_submit';
        }

        return $event_type;
    },
    10,
    3
);

add_filter(
    'conversion_bridge_meta_event_type',
    function( $event_type, $event, $track_method ) {

        if ( 'Lead' === $event_type ) {
            return 'custom_form_submit';
        }

        return $event_type;
    },
    10,
    3
);