Integration Summary

(See Partner Integrations Glossary)

Setup Instructions

To set up Facebook attribution tracking for an application:

Prerequisites

• Make sure your app is integrated with Singular via an SDK or S2S integration (see Getting Started with the Singular SDK/S2S).
• Accept Facebook’s Advanced Mobile Measurement Agreement. To accept the agreement or check your status, see Facebook Advanced Mobile Measurements.

1. Set up Facebook Install Ads

• Register the application on Facebook: To run Facebook Mobile App Install Ads, the application must be registered with Facebook. Visit the Facebook App Dashboard to set up your application.
• Create a Facebook Mobile Install Ad: Singular supports tracking Mobile Install Ads on Facebook's Audience Network. To create your ad, consult the Facebook Mobile App Install Ads tutorial.

2. Add the Facebook App ID to your Singular Account:

• Retrieve your Facebook App ID from your Facebook App Dashboard.

  

• In Singular, go to Attribution > Partner Configuration and type "Facebook" in the search box.

• Confirm you have signed the Facebook Advanced Mobile Measurement agreement. This allows Singular to share Facebook data with any of your connected BI tools.

  

• Enter your Facebook App ID. You can add multiple Facebook App IDs by separating them with a comma:

  

• View-through tracking is enabled by default. If you want, you can deselect it:

  

• Save the integration.

  Note: By saving the Facebook integration configuration here, Singular automatically tracks installs and sessions to Facebook. This corresponds to the mobile_app_install and fb_mobile_activate_app events. You do not need to configure these events separately in step 5.

3. Send Event Postbacks to Facebook (Optional)

Singular supports sending event notifications to Facebook with all of Facebook's requirements.

• First, select enable sending in-app events to Facebook by selecting All.

• Next, map your In-app events:

  • Select the event name on the left field, according to the name used in the SDK, and map the name to one of Facebook's predefined conversion events.
  • Check the Send value checkbox if relevant (for example, revenues). If not checked, only counts of the event will be sent.

See also: Using the Facebook SDK and Singular SDK/S2S in the Same App.

4. Set Up Facebook In-App Event Requirements

Some Facebook in-app events require certain arguments to be passed to be processed by Facebook:

For example, if you are sending an SDK event called "Click" and would like to map it to the Facebook Event Name "AdClick", ensure that "ad_type" is being sent in the "Click" event:

Android Example:

Singular.event("Click", "ad_type", "banner");

iOS Example:

[Singular eventWithArgs:@"Click", @"ad_type", @"banner", nil];

5. Tracking Facebook Mobile App Installs in Singular

After completing the steps above to enable Facebook Attribution Tracking, you can see the results of your Facebook's Audience Network campaigns in your Singular Reporting. Each install attributed to a Facebook Mobile App Install Ad will automatically be reported based on the Campaign Name, Ad Set, and Ad Group Name created in Facebook's Platform.

Attributions from ads within Facebook's App will be reported with the publisher "Facebook." Attributions from Instagram will show Instagram as their publisher. Attributions from Partner Mobile Apps on Facebook's Audience Network will show Audience Network as their publisher:

Click-Through Tracking

As with all click attribution, Facebook click-through attribution refers to the ability to credit an ad campaign for an install if an individual has clicked on an ad before that install. When a user clicks an ad, installs the app, and later launches the app, it’s assumed that the click led to the download and that installation is attributed to that specific ad. Click–through attribution is always given credit for an install if there are clicks in the attribution window. If there are no clicks, then view-through tracking is applied.

View-Through Tracking

View-through refers to the ability to credit an ad campaign for an install even if no one has clicked on an ad. The idea behind view-through is that it makes a causal contribution to driving an install even if the viewer does not click the ad.

Singular supports view-through tracking for Facebook. By tracking Facebook view-through as part of your app attribution and measurement, you will be able to make smarter decisions about campaigns, creative executions, and more. With Facebook view-through, the last ad impression is credited with an install if there are no ad clicks to which you can attribute that install. View-through is increasingly becoming an invaluable measurement metric for evaluating and optimizing campaigns. View-through attribution & reporting will not affect your media costs for Facebook CPM or CPC campaigns. Rather, view-through measurement gives you another valuable tool to improve your decision-making and optimization.

Singular view-through tracking utilizes the Facebook 1 day view window. Note that view-through attribution is enabled by default.

Data Mapping

Facebook values are mapped to Singular reporting dimensions as follows:

When running a Facebook report, Singular will also match the SDK data with the marketing data provided by Facebook Ads API, including:

• Spend by Campaign
• Spend by Creative, including the image or video
• Account ID

Partner Data Policies

As a Facebook Mobile Measurement Partner, Singular adheres to the following data handling requirements required by Facebook:

Data Retention

Facebook user-level data is removed after 6 months of original attribution.  After 6 months, users attributed to Facebook are treated/marked as "Organic" and reflected as such in both aggregate and user-level reporting in Singular.

Data Access

Access to user-level view-through data is not allowed in the interest of protecting end-user privacy.  Any field normally identifying an attributed Facebook view-through attribution is marked as "Unattributed" for any data processed after April 22nd, 2020. 

California Consumer Privacy Act

Starting July 2020, Facebook allows advertisers to notify Facebook if end-users choose to limit or allow data processing for California users, using a "limit data use" flag. Learn more in Facebook's developer documentation.

Singular uses the limitDataSharing value passed to Singular SDK and S2S in integrations with CCPA-compliant partners such as Facebook. When Singular.limitDataSharing(true), Facebook will "limit data use" for this user in Facebook targeting if they are a California resident. If a limitDataSharing value is not explicitly provided, Singular defaults to notifying Facebook that "limit data use" should be applied for California residents.

For implementation details and examples, see our iOS SDK, Android SDK, and S2S API guides.

FAQ

How does Singular track Facebook installs?

As a Facebook Mobile Measurement Partner, Singular has a unique line of communication with Facebook that enables attribution tracking. After the download of an application with Singular's SDK and Facebook Attribution Tracking enabled, Singular receives information about which installs originated from Facebook.

Are communications between Singular and Facebook secure?

Singular uses all the necessary security measures required by Facebook to ensure communications between Singular and Facebook are secure. We also comply with all of the privacy policies set forth by Facebook to protect your data.

I'm still not seeing Facebook attributed installs. Where can I get help?

If you've followed the setup steps but still aren't seeing Facebook attributed installs after performing your test, contact Singular's Support Team for additional help. Provide your account name, the applicable application, and your Facebook App ID in your initial email to help ensure a quick resolution.

Do I need to set the AdvertiserTrackingEnabled (ATE) flag?

As part of the updates related to iOS 14, Facebook announced new guidelines for using the Advertiser Tracking Enabled flag with MMPs. Your integration with Singular already implements this flag, and no action is required in your Singular SDK implementation.