Important Attribution reminders

There are a few things you should know about Attribution in order for it to work properly with your campaigns.

Facebook Developer Account

If you will be utilizing the Localytics integration with Facebook, you will need to include the AdSupport Framework as detailed in the Localytics iOS integration guide. You'll also need an active Facebook Developer Account.

Entering the Facebook App ID

To enable Facebook attribution, you must edit each respective app in the Localytics Administration tab and include the Facebook Developer Application ID. Your Facebook Developer Application ID can be found by logging in to your Facebook Developer Account and clicking Apps.

AdSupport Framework (iOS only)

In order for your app to be able to access the device identifiers that are required for most iOS acquisition to work, you must include AdSupport.framework as discussed in the iOS Integration Guide. You've likely already done this, but it's worth checking just to be sure.

Google Play Services SDK (Android only)

In order for your app to return the Google Advertising ID (GAID from devices running your app, you must include the Google Play Services SDK 4+. The use of GAID is not yet a requirement for app analytics on Android. However, if your Android app serves in-app advertising, your Google account manager may require your app to use GAID in place of Android ID.

If you use a code obfuscation tool (e.g. ProGuard), please be sure to configure ProGuard such that the file paths to both the Localytics SDK and the Google Play Services SDK are exempt from obfuscation. More information can be found at the full Google Play Services SDK setup instructions.

MobileAppTracking by TUNE SDK

If you will be utilizing the Localytics integration with MobileAppTracking by TUNE, you will want to install the most recent version of the MAT SDK and have an active MAT account.