AppsFlyer's Attribution Model

  • Advertisers
  • Ad Networks

mobile user journey

What is Mobile Attribution?

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.

An Attribution Model is a rule, or set of rules, used to determine how credit for an event is assigned to touchpoints in conversion paths. All players in the mobile marketing ecosystem, from Google Play and iTunes, to ad networks such as Facebook and Twitter and onto the mobile measurement companies, have their own mobile attribution models. Each player, by definition, counts installs and events differently.

It is important, to understand the attribution model of a player you work with, and most important to understand the AppsFlyer attribution model for AppsFlyer is the globally recognized mobile attribution authority.

What is a Mobile App Install?

AppsFlyer's attribution model is that an install is recorded only after the user downloads and launches the mobile app. This means that 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

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 in an out-of-store market.

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:

  • iOS devices: IDFA, hashed Sha1 IDFA
  • Google Play: GAID, hashed Sha1 GAID
  • Out of store Android markets: Android ID, IMEI device IDs

Device ID Matching for Self Reporting Networks 

Upon the first app launch, AppsFlyer checks whether the app is configured to receive traffic from several networks, called Self-Reporting Networks (SRN). These networks include Facebook, Snapchat, Google Ads, Twitter, etc. 

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

Fingerprinting

The fingerprint is established 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.

Fingerprinting is a statistical matching method and is 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.

For the same reason, the attribution window for fingerprinting is much shorter than the other methods. However, AppsFlyer determines the fingerprinting attribution window dynamically, based on the type of the user's network and the uniqueness of the IP address.

IP_uniqueness.png

TV Attribution

AppsFlyer supports attributing organic installs to TV or radio campaigns under the TV media source. An organic install is TV attributed when all of the following occur:

  • The download, install, and the first launch together takes place a short time after the commercial is aired.
  • The user is physically located in the country where the ad is aired. The option to limit to a specific city is permitted.

Methods of TV attribution:

  • File Loading
  • TV Integrated Partners
  • Shazam

See Integrating with TV Attribution Measurement Partners

Pre-installs

AppsFlyer supports attributing app installs when the app was installed on the device prior to the user purchasing the device.

Because there is no preceding user engagement, click-through, or view-through, installations are attributed on the first launch using AppsFlyer's SDK API. See Configuring and Testing Pre-install Campaigns for Android

User Engagement Attribution Types

AppsFlyer records and uses two types of different user engagement attribution types: click-through and view-through. Click each item below to view the details.

Click-Through Attribution

Most attributed mobile installs come from user clicks on ads: banners, videos, interstitials etc.

Upon the ad click, AppsFlyer opens a click lookback window with a default duration of 7 days. Installs that occur during the lookback window duration are considered as non-organic and are attributed to media sources. Installs that occur out of the lookback window are considered as organic installs.

click-through-lookback.png

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 Ads 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.

For more information about AppsFlyer's lookback windows, click here.

View-Through Attribution

New installs by users who have viewed mobile ads, but have not clicked on them, can be attributed to the ad networks that served the ads.

The lookback window for view-through attribution, which is much shorter than for click-through attribution, is also configurable in the AppsFlyer dashboard.

To enable the view-through attribution, you must select it in the configuration window.

view-through-lookback.png

This is especially helpful for video ad networks that traditionally have low CTRs on their video ads, but also for traditional ad networks serving regular ads.

Attribution Type

Attribution Method

Range

Recommended
(default)

View-Through

(Selected Integrated Partners)

ID Matching

1 Hour - 2 Days

1 Day

In cases where both a click and an impression have occurred, the click always prevails, as it is an active engagement.

For more information on View-Through Attribution, click here.

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.

For more information, click here.

Re-Installs

AppsFlyer records new app installations on a device when:

  • The app was never previously installed OR
  • 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.

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.

For more information, click here.

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.

Was this article helpful?
9 out of 10 found this helpful

Page Contents: