Channel Integration - Meta Ads
Written by Jeongwon Kim,Note
Your Meta ads performance data is available as "facebook.business" channel data in Airbridge.
Track and measure your Meta ads and send postbacks to Meta for campaign optimization.
The Facebook MMP Integration consists of 2 steps: providing the Facebook App ID to Airbridge and setting up the in-app event postback.
Facebook App ID: The Facebook App ID is required to measure the app performance of your Meta ads by allowing Airbridge to receive the last touchpoint of the converted event attributed to Facebook Ads.
In-app event postback setup: The in-app event postback lets you forward Airbridge in-app events to a registered Facebook app, use them to optimize your Facebook campaigns, or create a lookalike audience for your retargeting campaigns.
Providing the Facebook App ID to Airbridge is required for the MMP integration, but the postback setup is optional.
Attention
Facebook MMP integration can be conducted without Facebook SDK integration. However, the deferred deep linking only works with Facebook SDK integration.
Deferred deep linking is available for Android apps or iOS apps with versions earlier than 14.5. Due to the ATT(App Tracking Transparency) privacy guidelines, deferred deep linking won't work on iOS versions 14.5 and later, regardless of the Facebook SDK integration or the ATT state of the user.
The Facebook App ID is required for the integration, whereas the Install Referrer Decryption Key is optional. By providing the Install Referrer Decryption Key to Airbridge, you can implement the Google Play Install Referrer (GPIR) and the Meta install referrer (MIR) to gain enhanced visibility into your meta campaign performance.
1. Navigate to [Integrations]>[Ad Channel Integration]>[Facebook Business]>[Integration]. Switch on the Facebook MMP integration toggle.
2. Sign in to your Meta for Developers account and find your app. Copy the App ID.
3. Paste the App ID into the Facebook App ID field in Airbridge. Once the App ID is submitted, you can measure your meta ad campaigns in Airbridge.
4. The Install Referrer Decryption Key is optional. Refer to this article to learn about the Install Referrer.
Attention
To collect the Meta install referrer data, the Airbridge Android SDK must be properly configured by your developer before entering the decryption key.
With the postback, you can send in-app events tracked by Airbridge to Meta and leverage Airbridge data to optimize your Meta campaigns and create audiences for retargeting campaigns.
You can find the events sent via postback on the Facebook Event Manager page.
Attention
The in-app event postback setting allows the Airbridge SDK to send in-app events to Facebook without implementing Facebook SDK. If you have already set up app event tracking in your Facebook SDK, this may duplicate your event data on Facebook.
Please check out this article for more details.
Switch on the In-app event postback toggle on the in-app event postback setting page.
Note
The Facebook MMP Integration toggle must be switched on, and the Facebook App ID must be provided before setting up the in-app event postback.
To disable the postback, switch off the toggle. When the toggle is switched off, Airbridge stops sending data to Facebook.
Attention
Note that disabling the postback may impact your Meta ad campaign optimization.
Airbridge events you send via postback must be mapped with Meta ad events. Airbridge provides a pre-set mapping list.
Note
When the MMP Integration toggle is switched on and the Facebook App ID is provided to Airbridge, the following data is automatically sent to Meta ads. This is not a configurable option. The event names in the parenthesis are the Meta ad event names.
Install (Install App)
Deeplink Open (Activate App)
Deeplink Pageview (abr_deeplink-pageview)
Airbridge events (Preset) | Meta ads events |
|---|---|
Open (App) | Activate App |
Add To Cart (App) | Add to Cart |
Sign-up (App) | Complete Registration |
Product View (App) | View Content |
Order Complete (App) | Purchase |
Search Results (App) | Search |
Sign-in (App) | abr_sign_in |
Sign-out (App) | abr_sign_out |
Home Screen (App) | abr_home_screen |
Product Catalog (App) | abr_product_catalog |
Order Cancel (App) | abr_order_cancel |
Note
When the MMP Integration toggle is switched on and the Facebook App ID is provided to Airbridge, the following data is automatically sent to Meta ads. This is not a configurable option. The event names in the parenthesis are the Meta ad event names.
Install (Install App)
Deeplink Open (Activate App)
Deeplink Pageview (abr_deeplink-pageview)
You can keep the default mapping of Airbridge standard events, modify the mapping setting, or delete unnecessary event mappings. Even if you change any of the default mapping settings, you can revert to the default setting by clicking the [reset] icon at any time.
If your Airbridge events don't match with any existing Facebook standard events, Airbridge can send these events by mapping them with Facebook custom events.
To do so, select Airbridge standard or custom event to map and choose "Facebook Custom Event," which is located at the bottom of the Facebook event list.
When mapping Airbridge events to Facebook custom events, they are sent to Facebook with the event name modified by the two rules below.
The prefix
abr_is added to your event name to distinguish it from Airbridge events.(e.g., your event name: complete_tutorial → Facebook custom event name: abr_complete_tutorial)
Facebook doesn't allow a period in the event name, so any event names containing a period will be replaced with an underscore before forwarding to Facebook.
(e.g., your event name: complete.tutorial → Facebook custom event name: abr_complete_tutorial)
Airbridge events forwarded to Facebook must adhere to the Facebook event name rules:
Maximum 40 characters.
Only letters, numbers, spaces, underscores, and hyphens are allowed.
Airbridge events that don't adhere to the naming rules won't be mapped properly or not sent to Facebook.
In situations where you can't follow Meta's naming rules, you may map your events to one of the unused Facebook standard events as an alternative option.
If you are already using in-app event tracking via Facebook SDK, duplicate events will occur. Therefore, use either of the below methods to avoid duplicate reporting on Facebook.
Stop event tracking via Facebook SDK.
Disable in-app event postback from the Airbridge dashboard.
Note
Meta supports deduplication for only app installs. If you have been tracking events via the Meta SDK and Airbridge sends install events to Meta, the installs won't be duplicated.
We highly recommend that you track your app events via Airbridge SDK only, as this allows you to send them to other ad networks besides Facebook. To disable event logging via Facebook SDK, follow these steps in the Facebook App dashboard:
Go to the Facebook App Dashboard, and select your app.
On the left-hand menu, click [Setting]>[Basic Setting].
Select the OS type, and switch off the "Log In-App Events Automatically" toggle.
To disable Automatic Event Logging in the Facebook SDK in your app code, follow these instructions below:
Attention
User data sent to Meta may include IP Addresses. Before switching on the AEM toggle, check whether the AEM protocol does not violate any data-sharing policies of the third-party platforms you are using.
The Aggregated Event Measurement (AEM) is Meta’s protocol that allows for the measurement of web and app events from iOS 14 and later devices.
When the toggle is switched on in Airbridge, Airbridge sends user data to Meta regardless of whether a user has opted in or out for data tracking to enable Meta’s AEM for App Promotion Campaigns.
You can view the lookback window and the attribution window set for Meta ads measurement in the [Attribution Rules] tab. Click Go to edit page to edit the settings.
Refer to this article to learn about the attribution window in Airbridge.
Airbridge Data | Facebook Data | Example |
|---|---|---|
Channel | facebook.business | facebook.business |
Campaign | Facebook Campaign Name | AOS Install Campaign |
CampaignType | In the case of AAA campaign operation, 'Automated App Campaign' will be displayed. | Automated App Campaign |
AdGroup | Facebook Ad Set Name | Female user purchased in last 7 days |
AdCreative | Facebook Ad Name | Video |
CampaignID | Facebook Campaign ID | 23847486484930218 |
AdGroupID | Facebook Ad Set ID | 23847486490951350 |
AdCreativeID | Facebook Ad ID | 23847486494102155 |
Content | Campaign goal | PRODUCT_CATALOG_SALES |
SubPublisher | Platform name | |
SubSubPublisher1 | Ad format within the platform | instagram_stories |
SubSubPublisher2 | Ad-related unique ID that the user clicked or viewed | 23848170884980258 |
SubSubPublisher3 | Whether the install was from a Facebook paid channel | TRUE |
IsViewThrough | Whether the attributed touchpoint was view-through (impression) | FALSE |
Airbridge Event | Facebook Standard Event | Facebook |
|---|---|---|
Open (App) | Activate App | abr_open |
Sign-up (App) | Complete Registration | abr_sign_up |
Sign-in (App) | abr_sign_in | abr_sign_in |
Sign-out (App) | abr_sign_out | abr_sign_out |
Home Screen (App) | abr_home_screen | abr_home_screen |
Product Catalog (App) | abr_product_catalog | abr_product_catalog |
Search Results (App) | Search | abr_search_results |
Product View (App) | View Content | abr_product_view |
Add To Cart (App) | Add to Cart | abr_add_to_cart |
Order Complete (App) | Purchase | abr_order_complete |
Order Cancel (App) | abr_order_cancel | abr_order_cancel |
Airbridge Event | Facebook Standard Event | Facebook |
|---|---|---|
CUSTOM_EVENT_NAME | - | abr_CUSTOM_EVENT_NAME |
Note that the Airbridge events, the Sign-in (App), Sign-out (App), Home Screen (App), Product Catalog (App), and Order Cancel (App) events are mapped to Facebook custom events as there are no matching Facebook standard events to map.
Note
Sending uninstall event data to Meta is currently not supported.
In line with Meta's Privacy Policy, from the Meta ads data imported to Airbridge through MMP integration and cost integration, fewer than 1,000 Meta ads impressions or fewer than 100 installs attributed to Meta will be masked and displayed as the following instead.
Privacy Block: All data is masked; only "Privacy Block" will be displayed.
+α, ±α: Data is partially masked.
With the deprecation of Meta's Advanced Mobile Measurement (AMM) program, user-level attribution data is no longer available in raw data and only available in aggregate data on Airbridge reports.
When switching on the AEM toggle in Airbridge, Airbridge starts sending user data to Meta. The user data may include IPs. It is advised to check the data-sharing policies of your third-party platforms.
If you are sending data via server-to-server integration, make sure the user identifier and IP are sent. Otherwise, the AEM won’t be available for your Meta campaigns.
The AEM can be used for Meta re-engagement campaigns regardless of whether the AEM toggle is switched on or off in Airbridge.
Was this page helpful?