Ad Attribution & Analytics
πΉ Tools to use: AppsFlyer, BFG SDK
What is Ad Attribution?β
Attribution is the act of determining what caused a user to install an app or to perform post-install acts like re-engagement and re-attribution. There are two types of attribution:
- Non-Organic Attribution occurs when a user interacted with an outside media source (such as clicking on an ad)
- Organic Attribution occurs when the user installs (or re-installs) the game without any outside intervention
Games published by Big Fish use AppsFlyer to track and attribute the install and post-install events for paid and non-paid marketing channels. AppsFlyer enables the Big Fish marketing and user acquisition teams to analyze the success of campaigns and optimize their spending for your game, and use the data to drive audience growth.
Before continuing, ensure you meet the following pre-requisites:
- Integrate the BFG SDK (Unity | Native Android | Native iOS)
- Enable AppsFlyer
Setting up OneLinkβ
AppsFlyer uses OneLink to create links with attribution, redirection, and deep linking capabilities that convert owned or paid media users into app users. OneLinks can also be set up to auto-detect the platform and redirect the user to the correct app store, so only one link is needed for both iOS and Google.
Work with your Big Fish producer to set up a OneLink link in the AppsFlyer portal and define a vanity domain specific to your game. The universal OneLink link will then direct users via Android App Links, iOS Universal Links, and the defined URI scheme to the appropriate location based on the device that is used.
Here is an example of a OneLink link set up in AppsFlyer:
Additional Steps for Androidβ
Update intent filters
Your Big Fish producer will send you a code snippet of an intent filter to put into manifest file of your app. An intent filter determines the type of requests that come from another app component (such as AppsFlyer). To complete setup for OneLink on Android, copy the intent-filter into the relevant <activity>
on your AndroidManifest.xml file. The snippet contains the following values:
- The
host
value, provided by your Big Fish producer. - The four-character pathPrefix, an auto-generated value from the AppsFlyer portal that is unique to your game.
Here is an example of the code snippet for an intent filter:
<intent-filter android:autoVerify="true">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="https"
android:host="bfgsdk.onelink.me"
android:pathPrefix="/yryN" />
</intentfilter>
Testing Non-Organic Attribution Behaviorβ
To perform testing for non-organic attribution, you must first set up your testing devices as follows.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.developer.associated-domains</key>
<array>
<string>applinks:bfgsdk.onelink.me</string>
</array>
</dict>
</plist>