Setting up multi-store Android attribution

The Android package name determines which dashboard will contain the attribution data. In the single dashboard method, all stores have identical Android package names. There is no concept of a channel parameter here.

The identification of the download store is by way of the AF_STORE parameter set in the SDK, as described in this section.  The AF_STORE parameter isn't case-sensitive. For example, ABC, abc, Abc.  

To prepare the APK:

1. Create a copy of the App build. Note: Don't change the Android package name. 
2. To identify the individual store use one of the following methods:
   • Manifest method: Add the following within the <application> tag of the AndroidManifest.xml to identify the store. Set the AF_STORE parameter to the app store name.

     <application>
        ...
        <meta-data android:name="AF_STORE" android:value="EnterStoreNameHere"/>
        ...
     </application>

     --OR--
   • API method: Prepare a separate APK for each alternative app store. Call the setOutOfStore API to set the AF_STORE value. Set a unique value for each store.
     

     AppsFlyerLib.getInstance().setOutOfStore("EnterStoreNameHere")

The value set here appears in AppsFlyer raw data install_app_store field. This field is available in:

• Overview dashboard
• Cohort dashboard
• Raw data reports (Raw data reports are an AppsFlyer premium feature)

1. In AppsFlyer, from the side menu, select Collaborate > Active Integrations
2. Choose the ad network.
3. In the Attribution Link tab, set the Out-of-store URL parameter. This populates the af_r macro on the attribution link to redirect users to the correct app store landing page. For example, &af_r=http://www.destinationurl.com The default URL is set in the App Settings page. If the option isn't available in the App Settings page, ask your CSM to enable it for you. 
4. Populate the af_r macro with the store landing page URL.
5. Set additional attribution link parameters.
6. Out-of-store media sources make use of ID matching for attribution and the AppsFlyer Probabilistic modeling serves as a fallback method.
7. Add one or more user ID placeholders to the link URL:
   • android_id
   • advertising_id
   • oaid
8. Copy the attribution link and give it to the ad network partner.

The Android package name combined with the channel parameter set in the manifest determines which store dashboard will contain the attribution data. 

To prepare a separate APK/manifest for each store:

• Add the following within the <application> tag of the AndroidManifest.xml to identify the store. Set CHANNEL parameter to the app store name. 

  <application>
       ...
       <meta-data android:name="CHANNEL" android:value="EnterStoreNameHere"/>
       ...
  </application>

  Note: Parameters are case-sensitive. For the channel name you must use upper or lower-case letters only (a-z or A-Z). No other characters, such as hyphen (-) or underscore (_), are permitted.

Add a dashboard (app) identified by the combination of the Android package name and channel set in the APK/manifest. Example: Android package name is com.myapp and the channel name is abcstore then the unique dashboard name is com.myapp—abcstore. 

To add a dashboard per store in AppsFlyer:

1. In AppsFlyer, from the side menu, select Settings > My apps, and click Add app.
2. Select Android > In 3rd-party store.
3. Complete:
   • Android package name: The package name is exactly as it displays in the app package. 
   • Channel name: Unique identifier (store name) to differentiate between dashboards having the same package name. Verify that you use the same value in the APK prepared for the store.
     Note: For the channel name you must use upper or lower-case letters only (a-z or A-Z). No other characters, such as hyphen (-) or underscore (_), are permitted.
   • App URL:
     • Contains the default URL download address that populates the af_r macro in attribution links. Enter the URL where the APK is hosted or its landing page URL. 
     • You can change this per attribution link when you create them. 
     • If you leave this field blank, you won't be able to set the default page in the future.
4. Click Next. 
5. Follow the instructions in the interface to complete adding the app. 

Non-organic installs

To test non-organic installs:

1. Use an Android device that does not have your app installed or register the device.
2. Generate a test attribution link using a OneLink link. Use test as the Media source name ("&pid=test").
3. Add an advertising ID being GAID, OAID, or Android ID to the click URL.

   http://app.appsflyer.com/com.greatapp?pid=test
   &af_r=http://www.destinationurl.com&advertising_id=b5a3-78d9b5-0f12345-xxxx

   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 attribution SDK embedded and launch it.

Organic installs

To test organic installs:

1. Use an Android device that does not have your app installed or that is registered.
2. Install the updated beta version app with AppsFlyer attribution SDK embedded and launch it.
3. Check the results:

Expected results

Prepare new APKs for the stores by using the single dashboard method instructions contained in this article.

1. Configure a URL link to the app in your Meta app settings, under the Android section.
2. Log in to Meta as the app admin, go to https://developers.facebook.com/apps/, and choose the app.
3. Go to settings and find your Android settings, or if you have not already configured Android, add the platform.
4. Fill out the required details, including the Amazon app store URL specific to your app.
   
   
5. In the AppsFlyer dashboard, under Active Integrations, select Meta ads, and enter the same Facebook App ID you use when recording Meta In-Store Mobile App Install Ads with AppsFlyer.

In addition to the Overview dashboard, you can use the following reporting methods in AppsFlyer.

• Cohort:
  • Combine multiple dashboards (apps) in a single report
  • View the performance of each dashboard by breaking it down by install_app_store
• Pull API (for single app method): Pull API installs raw data does not contain the Install App Store by default. To include the column add the following to the Pull API call: &additional_fields=install_app_store
• Custom dashboard (for multiple apps method): If you use the multi-dashboard approach, use the custom dashboard to combine performance data from several apps in one place. 

• Referrer attribution is supported in relation to Google Play and the third-party stores listed here. 
• For most third-party app stores, no other setting or configuration is required. For Xiaomi, an extra dependency needs to be configured. Learn more
• Attribution by third-party store referrer is reflected in raw data reports as follows:
  • Match type: the name of the third-party store attributed. For example, huawei_referrer.
  • Contributor: If the user engaged with multiple app stores before installing the app, AppsFlyer considers these engagements as contributors. The install is awarded to the last-click engagement. Example:
    • A user clicks on an ad served by Google and is redirected to the Play Store. The user doesn't download the app.
    • The user clicks on another ad and is redirected to the Samsung Galaxy store. The user downloads and installs the app.
    • Attribution is awarded to the ad network causing the user to be redirected to the Samsung Galaxy store; Google is recognized as a contributor. 

Third-party Android stores having referrer attribution integrations with AppsFlyer