![]() Note: Don't change the Android package name. The AF_STORE parameter isn't case-sensitive. The identification of the download store is by way of the AF_STORE parameter set in the SDK, as described in this section. There is no concept of a channel parameter here. In the single dashboard method, all stores have identical Android package names. The Android package name determines which dashboard will contain the attribution data. Do so via the Active integrations page in the usual manner. Prepare attribution links with the app ID combined with the channel name. The assumption is that the app is already active in AppsFlyer. Set the value in the individual APK prepared for the store and when adding the app in AppsFlyer.ĭon't set a channel for the Google Play Store APK. If the app is already in Google Play Store use the existing package name. The identical package name for all dashboard options The table is used by the developer to prepare the APKs.Use the naming table that follows to map the channels and stores.Decide on the naming convention for the channel and install_app_store parameters.The tasks are divided between the marketer and developer.įor the Dashboard-per-store option repeat the tasks for each store. The workflow that follows lists the activities required to set up the desired option. This is to avoid discrepancies (more common when comparing data with SRNs). Make sure the partners you're working with are active ( Activate partner is turned on) in all dashboards.Use Cohort to display combined reports of all stores together.View organic and non-organic installs and in-app event data per store (channel) on separate app dashboards in AppsFlyer.Attribution accuracy: Re-installs are counted, which results in less accurate attribution.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 -xyzdevicestore. Example: The Android package name is and the channel is xyzdevicestore.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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |