Reporting options, broken down per store, are limited to Overview, Cohort, and raw data at present.Organic installs will reflect organic installs of APKs from all stores under one dashboard.Attribution accuracy: Re-installs from different stores don't result in inflated install numbers.Reach out to your CSM asking them to add the necessary SFDC feature flag. Overview, Cohort and raw data reports include the field. Reporting options available having install_app_store field Hence the attribution links will be different. The app ID is the channel name appended to the android package name.Create these using the Active integrations page.A unique link is required for each store.To redirect to the correct store, use af_r to set the redirect URL.Links are the same irrespective of the store.When working with OneLink this method is recommended. The store name is set in the manifest/APK.In the case of Google Play Store, this is blank.Uniquely identifies the store providing the app by download.If the APK has a channel setting but there is no app with this setting, traffic is attributed to the default app, being the app with a blank channel setting being Google Play Store.The unique dashboard identifier is -xyz_device_store. Example: The Android package name is and the channel is xyz_device_store.The combination of Android package name and channel uniquely identifies each AppsFlyer dashboard.When adding the App in the AppsFlyer dashboard using the Android Out-of-Store APK option, set the channel.Use the same (identical) package name irrespective of the option selected. This means you have as many dashboards as stores providing the app. Dashboard per store: Multiple dashboards-each store has its own dashboard.Single dashboard: One dashboard that combines data from all stores, including Google Play Store.

For apps marketed in China, see Attributing Android apps in the Chinese domestic market.AppsFlyer Android attribution supports all device identifier types including GAID and OAID.

Download app store android