Skip to main content
Airbridge supports integration with Meta ads Conversions API. With the integration, you can send the Airbridge events to Meta ads via postbacks for campaign optimization. To implement the integration, navigate to [Integration]>[Ad Channel Integration] and select Meta ads.
Attention
  • Event duplication will occur if you’re also collecting events using the Meta SDK or Pixel.
  • Events will not be sent to Meta Ads via postback if you’re using the Airbridge Restricted SDK.

​
Integration Setup

You need to submit the credentials required for the integration and configure the event mapping.

​
Submit credentials

You need to get the following credentials from the Meta Ads Manager. For more details on the credentials, refer to the Meta ads documentation.
  • Pixel ID
  • Access Token
  1. Log in to your Meta Ads Manager and navigate to [Events Manager] in the left menu bar.
  1. Navigate to [Data Sources].
  1. Select the pixel you want to connect with the Conversions API and click Settings.
  1. Find the Pixel ID under “Dataset ID.”
Scroll down to find the Access Token under the “Conversions API” section. If you don’t have an Access Token yet, click Generate access token to create one.
Navigate to the [Conversions API] tab in the Meta ads page in the Airbridge dashboard and enter the Pixel ID and Access Token in the respective fields.

​
Complete event mapping between Meta ads and Airbridge events

Review the following before you proceed.
  • The following events cannot be sent to Meta ads via Conversions API:
    • Deeplink Open (App)
    • Deeplink Pageview (App)
    • Uninstall (App)
    • Ad Impression (App)
    • Order Canceled (App)
  • Only events containing fbclid are sent to Meta ads. If you previously used another third-party platform, you may notice fewer events being sent after switching to Airbridge. This is expected behavior, as the sending conditions differ.
  • Only attributed events are sent, including the events attributed to ad channels other than Meta ads.
NoteUnmapped events will not be sent to Ad Channels even after enabling the integration. Make sure to map all Airbridge events you want to send to Ad Channels.
After submitting the credentials, move to step 2 and map the Airbridge events you want to send via postbacks with the Meta ad events you want to pair. At least 1 event pair must be set to save the mapping table. App events can be mapped to web events, too. Click Add to add new event pairs. You can choose to map the events manually or to import the event mapping configured for channel integration. When you are done, click Save to save the mapping table.
When selecting Map the events manually, you can select an Airbridge event from the drop-down menu and select a Meta ads event to map with. When selecting an Airbridge event with the “Preset” tag, the preset Meta ads event will be automatically mapped. If needed, you can select a different Meta ads event to map with. In this case, the “Preset Off” tag will appear. By clicking Preset on the right, the event pair will revert to the preset version.
When selecting Import event mapping from channel integration after clicking Add, you can import the event mapping saved for channel integration with Meta ads.
Read on to learn more about presets and custom events.
App EventsWeb Events
For any Airbridge event, regardless of whether it is premapped to a certain Meta ads event, you can use a Meta ads custom event name for mapping, which can be found at the bottom of the Meta ads event drop-down list.
The Meta ads custom event name is automatically generated, prefixed with “abr_”, and if the Airbridge event name includes a period, it will appear as an underscore in the Meta ads custom event name.For example, the “complete_tutorial” event, an Airbridge standard event, can be mapped with the Meta ads custom event name, “abr_complete_tutorial_APP” or “abr_complete_tutorial_WEB”. For the “hello.Airbridge” event, an Airbridge custom event, you can map it with the Meta ads custom event name, “abr_hello_Airbridge_APP” or “abr_hello_Airbridge_WEB”.
NoteIf the name of an Airbridge custom event exceeds 40 characters or contains special symbols, this event won’t be processed correctly when sent as a Meta Ads custom event. For example, if an Airbridge custom event named “Hello?” is sent as a Meta Ads custom event, it will be transmitted as “abr_Hello?”.Since the name contains a question mark (?), it cannot be identified as an event in Meta Ads. To send such Airbridge custom events to Meta Ads and make them identifiable as events, map them to Meta Ads standard events instead of custom events.
If you want to change the saved event mapping, click Edit. To change events from the mapping table, click on the event you want to change and select a new event from the drop-down list. To add new event pairs, click Add and select the events manually or Import event mapping from channel integration. If you import the event mapping from channel integration to edit an existing event mapping, note that the imported mapping table overrides existing event pairs. To delete event pairs, click the [minus] icon.

​
Enable the Conversions API Integration

Once you are done with steps 1 and 2, switch on the [Enable integration] toggle. Upon switching on the toggle, Airbridge starts sending the mapped events to Meta ads via postbacks through the Conversions API. If the Airbridge events sent through the Conversions API are used for your Meta ads campaign optimization, be careful when disabling the integration because it may have a direct impact on your campaign results. It may take up to 24 hours for events to appear on the Meta Ads Dashboard. When switching on the [Enable integration] toggle, the [Extended Privacy Control] toggle will appear. To learn about the Extended Privacy Control, refer to the article below.