Web-to-app attribution

 

At a glance: Explaining web-to-app attribution and how to use the web-to-app page to analyze it.

Introduction

If one of you're marketing goals is converting users from web to app, web-to-app attribution (W2A) can help you analyze your efforts and performance.

Such analysis helps you understand where potential app users are coming from. It also helps you allocate resources to specific web media sources that prove efficient in bringing users that install your app.

Accessing W2A attribution data

To see the W2A data analysis use one of the following methods:

Option A:

  1. In AppsFlyer, select an app that is part of a Brand Bundle.
  2. Select People Based Analytics.
    The People-based analytics page opens and W2A data displays.

Option B:

  1. In Appsflyer, go to My apps, click View brand bundles.
  2. Choose a Brand Bundle Name
  3. Click View people-based analytics.
    The People-based analytics page opens W2A data displays. 

Data coverage in W2A

Data in W2A only shows organic installs or installs that follow a click on a smart banner or custom link. It doesn't show installs coming from AppsFlyer integrated partners. See the following table:

Web traffic type Install type Install shown in website traffic sources chart
Paid / Owned / Earned Organic / Custom link / Smart banner Yes
Paid / Owned / Earned Click coming from an AppsFlyer integrated partner No

Data freshness in W2A

Data in W2A is subject to change and is finalized only 7 days after the install.

For example, if you're looking at installs for September 30, the data for these installs is only finalized on October 8. On October 8, W2A shows the final decision for installs and the contribution of web media sources for them.

The reason is that it provides higher rates of matching. 

 Example

PBA matches an install to touchpoints using a customer user ID (CUID). To perform matching, a user must have a web user and a mobile user, both with the same CUID.

Scenario 1: A user visits a website and signs up. Then, they install the app but only log in after 3 days. 

The user,

  • Receives the web CUID after signing up and logging in to the website.
  • Downloads and installs the app.
  • After three days, they log in to the app and are assigned a mobile CUID.
  • PBA matches the install to website visits (touchpoints). 
    • Initially PBA can't match the install as there isn't a mobile CUID.
    • PBA matching is only available when the mobile CUID is created (in this case, 3 days later).
    • PBA waits up to seven days for the mobile CUID to be created.

Scenario 2: A visits the website, installs the app and signs up. Then, they visit the website and log in.

The user,

  • Downloads and installs an app.
  • Signs up and logs in to the app and receives a mobile CUID.
  • After four days, they log into the website and get their web CUID.
  • PBA matches the install to website visits (touchpoints). 
    • Initially PBA can't match the install as there isn't a web CUID.
    • PBA matching is only possible when the web CUID is created (in this case, 4 days later).
    • PBA waits up to seven days for the web CUID to be created.

Filtering data in the W2A page

You can filter data by the following:

      • Date range
      • Media source - only filters web media sources, not mobile media sources that are shown in the web-to-app report table.
      • Geo
      • Media type
        • Paid - media sources that you pay to advertise your website.
        • Owned - owned media sources such as email, SMS, viral posts.
        • Earned - Direct traffic or traffic coming from search engines.
      • Mobile platform
        • iOS
        • Android
      • Install type
        • Organic - an install that is not attributed to any click or impression.
        • Smart banner - an install that follows a click on a smart banner on your website.
        • Custom link - an install that follows a click on a custom link.

Filter the data to zoom in and out and to compare different media sources or Geos for example.

Installs by website traffic source

The W2A page includes Installs by website traffic source. This is a breakdown of installs by contributing media sources.

Traffic type

The breakdown in Installs by website traffic source shows the distribution of traffic type for installs:

      • Referred - the percentage of installs following user traffic from web media sources to your website.
      • Organic - Installs following direct user traffic to your website.
      • No website traffic - Installs without preceding traffic to your website.

installs_break_down_traffic.png

Top media sources

Click Top media sources. on the right-hand corner above install breakdown bar. Clicking on it switches the view from traffic distribution to distribution among the top media sources. The breakdown only shows referral traffic.

installs_break_down_top10_sources.png

Top website traffic sources

Another component in the W2A page is the top website traffic sources chart.

Using the chart

You can use the chart to get a high-level view of web traffic that drives installs. You can look at peaks and fluctuations in the table to get a sense of how web media sources are doing in terms of driving traffic that converts to installs.

This chart shows a daily breakdown of the top website traffic sources that drive app installs.

To compare traffic from different media sources on the same day, hover over the chart on that day.

top_media_sources.png

Filtering traffic sources

You can filter out traffic sources from the chart to choose which media sources you want to compare. To exclude sources from the chart, uncheck the box next to the traffic source in the list on the right-hand side of the chart.

exclude_media_sources.png

Web-to-app report table

The web-to-app report table shows data related to web media sources that contribute towards installs.

The table consists of the following:

Installs:

      • Total - Total number of installs following a user visit from this web media source. The install is associated with the web media source if it's a single source or last source.
      • Single source - When the web media source is the only web media source in the user journey to install. No other web media sources are present in the user journey to install.
      • Last source - When the web media source is the last web media source in the user journey to install. Other web media sources are present in the user journey but are attributed as assists.

Assists:

      • First source - The first web media source in a series of touchpoints in the user journey.
      • Intermediate source - The web media source is in the user journey between the first and last touchpoint.

Total impact - All the installs that the web media source is involved in and contributes to, whether as a single, first, last or intermediate touchpoint.

Impact ratio - The sum of installs and assists divided by the number of installs. Impact ratio helps you understand the wider contribution of a web media source. It allows to quickly assess the positive lift of a media source, in assisting other media sources to convert users.

Drill down to campaign level

You can drill down into campaign-level performance for each web media source. To do so, in the web-to-app report table click on the desired media source. The column header changes to Web campaign and listed under it are the different campaigns for that web media source.

Mobile media sources

Web media sources are part of the user journey to install but are only considered contributing media sources. The media source that the install is attributed to is always a mobile media source. To see the mobile media source that the install is attributed to toggle on Show mobile sources.

Exporting data

You can export the table by clicking Export CSV on the top-right hand corner of the table.

web-to-app-report-table.png

  1. Go to the dashboard of an app that belongs to the brand bundle.
  2. In the left-hand menu, choose People Based Analytics.
  3. The People-based analytics page opens and shows W2A data.

Alternatively, you can do that from the my apps page:

  1. In your AppsFlyer account, from the my apps page, click View brand bundles.
  2. Choose the desired bundle.
  3. Click View people-based analytics.
  4. The People-based analytics page opens and shows W2A data.

Data coverage in W2A

Data in W2A only shows organic installs or installs that follow a click on a smart banner or custom link. It doesn't show installs coming from AppsFlyer integrated partners. See the following table:

Web traffic type Install type Install shown in website traffic sources chart
Paid / Owned / Earned Organic / Custom link / Smart banner Yes
Paid / Owned / Earned Click coming from an AppsFlyer integrated partner No

Data freshness in W2A

Data in W2A is subject to change and is only finalized 7 days after an install.

For example, if you're looking at installs for September 30, the data for these installs is only finalized on October 8. On October 8, W2A shows the final decision for installs and the contribution of web media sources for them.

The reason is that it provides higher rates of matching. 

 Example

Basics: PBA matches an install to touchpoints using a customer user ID (CUID). To perform matching, the user must have a web user and a mobile user, both with the same CUID.

Scenario: A user visits a website several times. Each visit originated from a different media source.

The user,

  • Downloads the app.
  • Three days later, they log into the app and are assigned a CUID.
  • PBA matches their install to web visits (touchpoints). 
    • Initially there is no CUID so PBA can't match the install.
    • Consequently, PBA waits seven days for a CUID to be available.

The opposite is also applicable. A user visits the website several times and then installs the app. But they only sign up and log in at the app. After 4 days, the user also logs into the website and get their CUID. When they log in, PBA matches the install to previous website visits (touchpoints). 

PBA can't match the install right way because at there is no CUID to match to at install time.. The CUID for both mobile user and web user is only available after 4 days from the install.

Filtering data in the W2A page

You can filter data by the following:

  • Date range
  • Media source - only filters web media sources, not mobile media sources that are shown in the web-to-app report table.
  • Geo
  • Media type
    • Paid - media sources that you pay to advertise your website.
    • Owned - owned media sources such as email, SMS, viral posts.
    • Earned - Direct traffic or traffic coming from search engines.
  • Mobile platform
    • iOS
    • Android
  • Install type
    • Organic - an install that is not attributed to any click or impression.
    • Smart banner - an install that follows a click on a smart banner on your website.
    • Custom link - an install that follows a click on a custom link.

Filter the data to zoom in and out and to compare different media sources or Geos for example.

Installs by website traffic source

The W2A page includes Installs by website traffic source. This is a breakdown of installs by contributing media sources.

Traffic type

The breakdown in Installs by website traffic source shows the distribution of traffic type for installs:

  • Referred - the percentage of installs following user traffic from web media sources to your website.
  • Organic - Installs following direct user traffic to your website.
  • No website traffic - Installs without preceding traffic to your website.

installs_break_down_traffic.png

Top media sources

Click Top media sources. on the right-hand corner above install breakdown bar. Clicking on it switches the view from traffic distribution to distribution among the top media sources. The breakdown only shows referral traffic.

installs_break_down_top10_sources.png

Top website traffic sources

Another component in the W2A page is the top website traffic sources chart.

Using the chart

You can use the chart to get a high-level view of web traffic that drives installs. You can look at peaks and fluctuations in the table to get a sense of how web media sources are doing in terms of driving traffic that converts to installs.

This chart shows a daily breakdown of the top website traffic sources that drive app installs.

To compare traffic from different media sources on the same day, hover over the chart on that day.

top_media_sources.png

Filtering traffic sources

You can filter out traffic sources from the chart to choose which media sources you want to compare. To exclude sources from the chart, uncheck the box next to the traffic source in the list on the right-hand side of the chart.

exclude_media_sources.png

Web-to-app report table

The web-to-app report table shows data related to web media sources that contribute towards installs.

The table consists of the following:

Installs:

  • Total - Total number of installs following a user visit from this web media source. The install is associated with the web media source if it's a single source or last source.
  • Single source - When the web media source is the only web media source in the user journey to install. No other web media sources are present in the user journey to install.
  • Last source - When the web media source is the last web media source in the user journey to install. Other web media sources are present in the user journey but are attributed as assists.

Assists:

  • First source - The first web media source in a series of touchpoints in the user journey.
  • Intermediate source - The web media source is in the user journey between the first and last touchpoint.

Total impact - All the installs that the web media source is involved in and contributes to, whether as a single, first, last or intermediate touchpoint.

Impact ratio - The sum of installs and assists divided by the number of installs. Impact ratio helps you understand the wider contribution of a web media source. It allows to quickly assess the positive lift of a media source, in assisting other media sources to convert users.

Drill down to campaign level

You can drill down into campaign-level performance for each web media source. To do so, in the web-to-app report table click on the desired media source. The column header changes to Web campaign and listed under it are the different campaigns for that web media source.

Mobile media sources

Web media sources are part of the user journey to install but are only considered contributing media sources. The media source that the install is attributed to is always a mobile media source. To see the mobile media source that the install is attributed to toggle on Show mobile sources.

Exporting data

You can export the table by clicking Export CSV on the top-right hand corner of the table.

web-to-app-report-table.png

Was this article helpful?