Advertisers who are used to working with Google Analytics (GA) can easily supplement GA information with rich mobile attribution data from AppsFlyer, for both iOS and Android apps.
For every new install or in-app event AppsFlyer can automatically send a postback with the following attribution data to GA:
- Media source name (utm_source)
- Campaign name (utm_campaign)
- Google search Keywords (utm_term)
- Country code (Geo)
- App ID
- App Name
- Bundle ID
- App version
- CID (Advertising ID for Android or IDFA for iOS)
- Type (install / in-app event)
- Event name (as sent from AF SDK)
AppsFlyer also sends all organic installs and events data to GA. Please note that organic data has no source information associated with it.
Configuring Google Analytics on AppsFlyer's Dashboard
For each app you want to send the attribution data from:
- Click Integrated Partners on the left menu bar
- Begin entering Google Analytics Solutions and then click the Google Analytics Solutions logo
- From the Google Analytics admin window, copy your Tracking ID
- From AppsFlyer's Partner Integration Configuration window select Enable to integrate and send all installs to Google Analytics.
- Paste the Tracking ID in the Account_ID field.
- Click Save & Close to finish if you only want to send mobile installations data to GA.
- To send your mobile users’ in-app events data to GA click the In App Events tab
- Select All in-app events option from the drop-down box
- Paste your Tracking ID on the Account ID box
- Select the Map all SDK events option or manually select the specific events to be sent to GA
- Click Save & Close.
AppsFlyer and Google Analytics SDKs
If your app has both the AppsFlyer and GA SDKs integrated in it, then you must set the Client ID (CID) parameter value to match between the two SDKs. GA’s SDK creates a unique CID upon initialization, while for AppsFlyer the value sent as CID is the unique Device ID (GAID for Android and IDFA for iOS). If these values are not matched, data reported on GA’s platform is duplicated.
To avoid duplicate data reporting you must perform ONE of the following options:
- Set the CID value to the unique Device ID (GAID or IDFA) of the new user.
- Set the “Customer User ID” value with the generated CID value.
Warning - Make sure to extract the CID from GA's SDK and set “Customer User ID” value BEFORE calling the startTracking method to avoid duplicate install events.
If you choose the first option leave the "Enable sending CustomerUserID" button toggled to "off" (see below).
For the second option you must toggle the button to "On".
The correct time to perform the tracking, as described, is after the new version has been submitted and updated by the majority of your active users.
If your app has only the AppsFlyer’s SDK, then no code changes are required.
Migrating from the Old UTM Parameters System
AppsFlyer also supports an older integration method with Google Analytics.
If your app is already using the older integration method it has to be disabled first or the result is duplicate results on GA when both methods are activated at the same time. Contact AppsFlyer Support or your CSM to perform the switch over between the two methods to avoid any duplicates or loss of data.
NOTE: As with all 3rd party platforms, Google Analytics receives all Facebook and Twitter data labeled as “organic” due to their T&Cs.
Custom Dimensions on Google Analytics
There is another available method for sending AppsFlyer's attribution data to Google analytics, that is set up on GA and not on AppsFlyer's dashboard. You can read about it here.
Advertisers that use the new integration with Google Analytics don't need to use the custom dimensions method.