What is AppsFlyer's Attribution Model?

What is Mobile Attribution?

Determining that a mobile app install, or post-install event, is the result of a particular media source engagement

Mobile attribution is essential for optimizing user acquisition and re-engagement efforts and results.

All players in the mobile marketing ecosystem, from Google Play and iTunes, to ad networks such as Facebook and Twitter and onto the mobile tracking companies, have their own mobile attribution models. Therefore, by definition all players count installs and events differently.

This is why it is important to understand the attribution model of any relevant player you work with, and first of all AppsFlyer, the globally recognized mobile attribution authority.

What is a Mobile App Install?

AppsFlyer's attribution model states that an install is recorded only after the user downloads and launches the mobile app. Therefore, the time stamp of an app install is always the first launch.

In contrast, ad networks regard the engagement time as the install time, while app stores use the download time.

AppsFlyer's Attribution Methods

There are several different attribution methods AppsFlyer uses, depending on the device platform and availability.

Install Referrer (Android only)

AppsFlyer uses the Google Play referrer parameter which delivers the original URL clicked before redirecting to Google Play. This is the primary method for Android and is only available if the Android app is stored in the Google Play Store and not on out-of-store markets.

Device ID Matching

The ad network, which has access to the user's device, sends the device ID to AppsFlyer on the Click URL, or when notifying AppsFlyer an impression has been served. This allows AppsFlyer to match the click Device ID with the device's ID fetched by AppsFlyer's SDK.

Device ID matching is the primary attribution method on iOS.

Available IDs are IDFA or hashed Sha1 IDFA for iOS devices, and GAID or hashed Sha1 GAID for Google Play apps. Out of store Android markets use Android ID or IMEI device IDs for ID matching.

Device ID Matching for SRNs

Upon the first app launch, AppsFlyer checks whether the app is configured to receive traffic from several networks, which are called SRNs (Self-Reporting Networks). These networks include Facebook, Snapchat, Google AdWords, Twitter and a few more such networks.

AppsFlyer queries all SRNs configured for the app, using the unique device ID of the new install. That is done via dedicated MMP (Mobile Measurement Partner) APIs, which SRNs enable AppsFlyer to use. Based on the returned answers, AppsFlyer can attribute new users to SRNs.

Fingerprinting

The fingerprint is established and captured by gathering different parameters about the device. The fingerprinting information is first gathered at the time of the click. At the time of app launch it is gathered again and matching is attempted. The information retrieved includes device related parameters such as IP address and OS version, but no personally identifiable information(PII).

Fingerprinting is a statistical matching method, and not based on a unique ID. Therefore, it always loses to clicks with referrer or ID matching methods, if they also occur within the look back window.

Click-Through Attribution

Upon the ad click AppsFlyer opens a click lookback window, which lasts 7 days by default. Installs occurring within the lookback window are considered as non-organic and are attributed to the media sources. Beyond the lookback window, they are considered as organic installs.

AppsFlyer recommends using 7-day click lookback windows, which is the industry standard. However, you can customize the time period to 1-30 days based on the agreement you have with your media sources. For example, Facebook uses a 28-day click-through lookback window, Twitter uses 14 days and Google AdWords uses 30 days. You can match AppsFlyer's click-through lookback window to any of these values.

Attribution Type

Attribution Method

Clicks Lookback Window

Range

Recommended (default)

Click-Through

(All Integrated Partners)

Referrer, ID Matching

1 – 30 Days

7 Days

Fingerprinting

Fixed

1 Day

The click fingerprinting attribution lookback window is limited to a maximum of 24 hours on iOS, and a lot less on Android, to maintain a high level of accuracy.

Advanced Attribution Topics

Assisted Installs

AppsFlyer fully attributes only one media source per install, usually according to the last ad click or the last ad impression (if there were no clicks).

Assisted Installs (AKA multi-touch attribution) are installs where the Media-Source/Campaign did not have the last touch, but did touch the user before the install and this took place within their attribution lookback window.

The assisting networks get credit as contributors to the install on AppsFlyer's dashboard and raw data.

Re-Installs

The app was already installed, has been uninstalled and then re-installed after the re-attribution window from the original install date has passed.

Re-installs within the re-attribution window are therefore not attributed to any media source, including organic. However, any performed in-app events by reinstalling devices are attributed to organic.

the For device testing and multiple installations, you must white list the device on AppsFlyer's database or else only the first install is recorded. To Whitelist a device for ongoing testing purposes, click here for more information.

Retargeting Attribution

A user who re-installs an app within the re-attribution window (90 days by default) is considered a re-attribution and appears as such in the AppsFlyer Retargeting Dashboard, if acquired from a retargeting campaign.

App Updates

When existing users update their app, AppsFlyer does not consider them as new users, nor show it in any way on the dashboard. You can see the distribution of your new app versions and more on the SDK information page.

The only exception to this rule is when an app, that has an active user base, first introduces AppsFlyer's SDK. When existing users update to the new version, which includes AppsFlyer's SDK, AppsFlyer shows them as new organic users.