Branch links can be used together with Facebook ads, allowing you to track ad-driven installs on the Branch dashboard and deep link those new users directly to content the first time they open your app. Refer to Facebook's Ad Guide to learn more.
Facebook's Ad Platform supports numerous campaign types and a shared set of advertisement formats. To help you navigate Facebook's Advertisement Platform we created this guide detailing how to use Branch links in all major Facebook ad types.
This documentation supports the following Facebook Ad Campaigns:
|Facebook Campaign Category||Campaign Type/Objective||Link users to||Branch Documentation Link||Branch Ad Format|
|Awareness||Brand Awareness||Web||link||Cross-platform Display|
|Consideration||Traffic||Web or App||link||Cross-platform Display|
|Consideration||App Installs||App||link||App Only: Installs|
|Consideration||Video Views||Web||link||Cross-platform Display|
|Consideration||Lead Generation||Web x||link||Cross-platform Display|
|Conversion||Conversions||Web or App||link||Cross-platform Display|
|Conversion||Product Catalogue Sales||Web or App||link||Cross-platform Product Links|
[x] Facebook has indicated that links are not supported in all placements.
Standard vs Custom Events
Please follow the Tracking Commerce, Content, Lifecycle and Custom Events guide when implementing event tracking in the Branch SDK. When tracking any of the Facebook events that are mapped to the Branch
customevent, use the event name from the table below; e.g.
|Facebook Event Name||Branch Event Name|
|Branch Data||Facebook Data|
|Branch Key-Value Pair||Facebook MMP Key-Value Pair||Facebook event(s) supported|
Currently Facebook appears to only support sending one fb_content_id (etc) per event, whereas Branch allows you to send many. To provide as much functionality as possible, we choose the first content_item and search it for key-value pairs that can be sent to Facebook.
You can see analytics on impressions, clicks, installs, opens and conversion events on various pages of the Branch Dashboard.
- If you're seeing discrepancies, please see Common Sources of SAN Reporting Discrepancies.
If you have signed Facebook's "Advanced Mobile Measurement" agreement ("Data Use Terms for Advanced Mobile App Measurement"), then you can get device level data out via:
Agreement not Signed
If you have not signed this agreement, any event attributed to a Facebook ad will look like an organic event when accessed via Webhooks, the Daily Export API, and CSV Exports.
- We can no longer show non-aggregated view-through data via Branch Dashboard and Exports, and this data will appear as "undisclosed" in exports. View-through data will only be provided at an aggregated level through our reporting interfaces or through Facebook’s reporting interfaces and APIs.
- We cannot send device-level Facebook attribution data to third parties.
- We cannot send events attributed to Facebook via Data Integrations. Please instead consider analyzing this data in-house (using Webhooks, the Daily Export API, or CSV Exports), or using the Branch Dashboard for all of your analytics and attribution needs.
- This data is also not returned in the deep link session initialization callback within the app. If you have analytics needs that are not met by the Branch Dashboard, please contact us and include "Facebook MMP + Feature Request" in the subject.
x] You must have signed Facebook's "Advanced Mobile Measurement" agreement ("Data Use Terms for Advanced Mobile App Measurement") to view this data.
Here is the page where you can see which ad accounts have signed the AMM agreement:
On July 1st, Facebook introduced a new Limited Data Use (LDU) feature to support customer compliance with the California Consumer Privacy Act (CCPA). This feature enables you to limit how Facebook uses the data of California users collected by you or by third parties on your behalf.
If the Limited Data Use feature is enabled, Facebook has indicated it will process such data in accordance with their role as a “service provider” under the CCPA, with respect to personal information from residents in California; i.e. Facebook will limit use of that data subject to their State-Specific Terms.
By default, Branch’s Facebook integration has the Limited Data Use feature enabled. This means that Branch sends Facebook the LDU flag as enabled with your Branch conversion data by default. Therefore, conversion metrics (e.g installs or other down funnel events) for California users will not be available in your reporting. NOTE: You will still see aggregate click, impression, and cost data for users in California.
However, Branch has provided a customer-controlled toggle in the event you desire to disable the Limited Data Use feature in your dashboard configuration. We recommend that you consult with your legal counsel to understand any implications of disabling the Limited Data Use feature for the Facebook integration as they pertain to CCPA or other state specific data protection laws, and to determine whether disabling the Limited Data Use feature will meet your needs.
To disable the Limited Data Use feature:
In the left-hand navigation panel under Channels & Links, click on Ads and then click Partner Management.
Find and select Facebook using the Ad Partners search feature.
On the Ad Partner settings: Facebook page, click on the Events Config tab.
On the Event Config tab, scroll down to the bottom and deselect Limited Data Use (LDU) Flag.
We also have a document with FAQs and Advanced Options for Facebook Ads. We recommend starting with one of the guides above, then jumping into the FAQ and Advanced Options when you have questions or need to troubleshoot.
Updated 2 months ago
|Facebook Ads FAQs|