At a glance: Attribution and data for different markets can be recorded on either a single dashboard (as a single app) or on separate dashboards (as multiple apps) on AppsFlyer. This article describes the differences between the two recording solutions and provides instructions for setup and testing.
AppsFlyer provides attribution recording solutions for Android apps supplied by both out-of-store and Google Play Store.
To enable organic and attributed installs to be assigned to an out-of-store market, such as Amazon or Baidu use one of the following methods:
- Single app: means that in AppsFlyer there will be only one app and all data will be shown as part of that app.
- Multiple apps: mean that in AppsFlyer each store is represented as a different app.
Both methods require that the developer prepare a separate APK for each out-of-store market which supplies the app. The difference between the methods is mainly the way AppsFlyer displays the information in the dashboard and reports. See also out-of-market attribution in China.
Single app
View the combined results of your marketing efforts across different markets, Google Play store and out-of-store markets, within a single app dashboard.
The attribution raw data contains the Install App Store value. When not empty, the value is the name of the out-of-store market that brings the new install, as set by the developer in the manifest/APK. Otherwise, the install is attributed to the Google Play store.
Important!
The single app solution is best suited when you want to view all non-organic installs and in-app events from all markets under a single app dashboard on AppsFlyer.
Note that with this solution the out-of-store market name is currently only in the non-organic and organic raw data reports. Make sure your account has access to raw data or upgrade it before implementing this method.
Multiple apps
View the organic and non-organic installs and in-app events data per market on separate app dashboards on AppsFlyer.
With this solution, each market entails a different APK, as well as designated attribution links. The results are displayed per market and not in a single app dashboard.
Important!
- Multiple apps solution is best for advertisers that prefer knowing the out-of-store markets where their organic users came from, to seeing the results under a single app.
- There are vendors that own markets, Android devices or Android browsers. In some cases, this causes the download of APKs from the wrong stores, which may deeply affect the accuracy of the attribution when using the Multiple apps solution.
Setup
To set up attribution recording for out-of-store markets, with either method, follow the instructions that follow.
Preparing an app version
The marketer's task on the AppsFlyer platform
No action is needed.
The results are displayed under your existing app's dashboard.
- Click the Add App button on the My Apps tab
- Select Android out of store APK (Standalone, Amazon, etc.)
- Insert your Android Package Name (eg. com.greatapp) and the Channel Name you are planning to promote your application on.
Developer's task
For each market you plan to advertise in, except Google Play:
- Create a copy of your app's build.
-
Use the following API:
AppsFlyerLib.getInstance().setOutOfStore("baidu");Or add the following line to the AndroidManifest.xml file:
<meta-data android:name="AF_STORE" android:value="baidu" />Where the value (in the above example "baidu") represents the store name for this specific APK.
-
To retrieve the value currently set for the out-of-store setting, use the following API
AppsFlyerLib.getInstance().getOutOfStore(getApplicationContext());Note
Migrating from multiple apps method to single app method?
1. Remove the CHANNEL line from your manifest file
2. Ensure that AF_STORE value is the same value you used for the Channel.
For each market you plan to advertise in, except Google Play:
- Create a copy of your app's build.
- Add to the Android manifest.XML the line below using the exact channel name you just used for adding the app to the AppsFlyer platform.
<meta-data android:name="CHANNEL" android:value="example_channel_name" />Note
The channel definition MUST take place within the <application>..</application> tags.
Example
<manifest>
.
.
<application>
.
.
<meta-data android:name="CHANNEL" android:value="example_channel_name" />
</application>
</manifest>
Important!
The channel name is case sensitive. Make sure the value in the manifest and the value entered in the dashboard are identical.
Creating the out-of-store attribution links (both methods)
When creating attribution links for out-of-store markets it is essential to always include the af_r macro, which redirects users to the correct market based on its URL value.
Integrated partners attribution links
- Go to Integrated Partners Configuration and choose the network you want to work with.
- Fill in the attribution link parameters
- Copy the click URL and paste it in an external editor (Notepad, Word, etc.)
- Add the landing page parameter (af_r), with the link to your app on the out-of-store market, e.g.,
&af_r=http://www.destinationurl.com - Out of store media sources make use of ID matching for attribution, while AppsFlyer's Fingerprinting serves as a fallback method.
Add either, or both, of the following macros to the URL:
android_id={ANDROID_ID_GOES_HERE}- OR -
advertising_id={GOOGLE_ADVERTISING_ID_GOES_HERE}Example 1
Android ID:http://app.appsflyer.com/com.greatapp-amazon?pid=Ad_network&android_id={ANDROID_ID_GOES_HERE}
&af_r=http://www.destinationurl.comExample 2
Google Advertising ID:
http://app.appsflyer.com/com.greatapp-amazon?pid=Ad_network
&advertising_id={GAID_GOES_HERE}&af_r=http://www.destinationurl.comCustom attribution links
You can record out-of-store installs coming from your owned media, such as email or SMS campaigns, by creating custom attribution links.
The link MUST include the landing page parameter (af_r), e.g., &af_r=http://www.destinationurl.com
Because it's not possible to extract device IDs from owned media, do not use the the android_id and advertising_id parameters with these links.
Amazon apps on Facebook
In order to drive users to the Amazon app store from Facebook, follow these instructions.
- Configure a URL link to the app in your Facebook App's Settings, under the Android section.
- Log in to Facebook as the app’s admin, go to https://developers.facebook.com/apps/ and choose the app.
- Go to settings and find your Android settings, or if you have not already configured Android, add the platform.
- Fill out the required details, including the Amazon app store URL specific to your app.
- In the AppsFlyer dashboard, under Integrated Partners, select Facebook, and enter the same Facebook App ID you use when recording Facebook In-Store Mobile App Install Ads with AppsFlyer.
- When setting up Advert Sets on Facebook, choose “Amazon Appstore”.
Please note that this screenshot is taken from the Facebook Power Editor, and may be presented differently in FMP platforms.
Testing
Non-organic out-of-store install test
1. Use an Android device that does not have your app installed or that is whitelisted.
2. Generate a test attribution link using Custom Media Source Configuration (instructions here). Use "test" as the Media source name ("&pid=test").
3. Add GAID or Android ID to the click URL.
Examples
Google Advertising ID:
http://app.appsflyer.com/com.greatapp?pid=test
&af_r=http://www.destinationurl.com&advertising_id=b5a3-78d9b5-0f12345-xxxxAndroid ID:
http://app.appsflyer.com/com.greatapp?pid=test
&af_r=http://www.destinationurl.com&android_id=2af62be48902xxxx4. Send the attribution link to yourself via email and click on it. Once redirected, do not install from the store. Instead, install the updated beta version app with AppsFlyer's attribution SDK embedded and launch it.
5. Checking the results:
- Check your app's installation raw data report under the Export Data page.
- You should see one installation conversion with the “test” media-source. Under the column titled Install App Store you should see the name of the store as it appears on the manifest.xml file.
- You can also see the param "af_installstore":"STORE_NAME" in the logs of the install.
- Go to the dashboard of the app that is specific to the tested store.
- Check your app's installs raw data report under the Export Data page or look at the overview page of the app.
- You should see one installation conversion with the “test” media-source.
Organic out-of-store install test
1. Use an Android device that does not have your app installed or that is whitelisted.
2. Install the updated beta version app with AppsFlyer's attribution SDK embedded and launch it.
3. Checking the results:
Check your app's overview page for a new organic install (under the “organic” media-source). At present, with the single app method, there is no indication as to the origin of organic installs.
- Go to the dashboard and overview page of the app that is specific to the tested store.
- You should see one installation conversion under “organic” media-source.
Installs attributed to the default app
If you create an out-of-store app but don't add an app for it in your AppsFlyer account, installs are attributed to the default app in your AppsFlyer account. If there is no default app, installs are attributed not at all.
More ways to get the data
Pull API (for single app method)
The regular Pull API call for the installs raw data report does not contain the Install App Store column. However, you can use the Pull API call to get this column by adding to the used URL: &additional_fields=install_app_store
Custom dashboard (for multiple apps method)
You can use AppsFlyer's custom dashboard to concentrate the marketing results from several or all of your apps, including apps for out-of-store markets.