Attribution Models

What is an Attribution Model?

Users are exposed to numerous advertisements prior to installing an app or making an in-app purchase (conversion). Throughout this user journey, the act of clicking or viewing an ad is considered a 'Touchpoint', whereas specific actions such as app installation or in-app purchase is considered as 'Conversion'. Attribution Model is a methodology that analyzes which touchpoint(s) is/are responsible for inducing a user to install an app or to perform target conversion events.

image__2_.png

Airbridge Attribution Model

There are a variety of attribution models namely Last Click, First Click, Linear and more. Airbridge employs Last Click Attribution Model by default with several attribution rules and touchpoint priority rules together. This means, even though a touchpoint is the last touchpoint, it needs to meet other rules such as fulfilling the attribution rule or it being the highest priority. Out of all the valid touchpoints recorded up to the converted event, the final selected touchpoint that satisfies all the rules is called the 'Winning Touchpoint'.

 


Attribution Rules for Mobile App Conversion Events

1. Attribution Rule for Install Events

Attribution Process

Highest credit and priority will be given to the touchpoint that meets the following attribution requirements.

Requirements:

  1. It must neither be a fraudulent install event nor a fraudulent touchpoint.
    • Airbridge provides a variety of safeguards to detect and analyze potential fraudulent conversion events. You can also separately check whether these events fall into the fraud validation rule that you configured previously in Airbridge dashboard.
    • Fraudulent install event will be recorded as unattributed.
  2. Only the touchpoints occur within the lookback window will be reviewed for attribution.
    • Lookback window is a period of time after an ad is clicked or viewed (touchpoints) within which an install event can be attributed to the ad. For instance, if the lookback window is set to 7 days, the touchpoints that occurred within 7 days prior to the conversion will be reviewed for eligibility as a winning touchpoint. The lookback window for install can be configured in the dashboard.
    • See Lookback window for Install setting 

Order of Priority

Airbridge prioritizes touchpoint attribution for the install events based on the rules below. Should several touchpoints hold equal priority, the latest created touchpoint will take the credit in accordance with the Last Click Attribution Model.

  1. Touchpoints are prioritized based on its collected path.

    1. The highest priority goes to the touchpoint generated by Airbridge Tracking Link or Self-Attribution Network(Google Ads, Apple Searchads.. ).

    2. The second priority goes to the touchpoint collected via automatic UTM parsing function.

    3. The third priority goes to the Call-To-Action button (web to app connectivity) in the Airbridge Web SDK installed web page.

         See [setDownloads, setDeeplinks setting]

  2. 'Click' are always given higher priority over 'Impression'.

  3. Device Matching (Referrer, Deeplink Matching, or ID Matching) are always given higher priority over the Fingerprint matching as Device Matching has higher accuracy.

Attribution Scenarios

  • Scenario 1

___________________1.png

  1. Must be within lookback window

    → 'A Channel' Click is eliminated.

  2. 'Click' has higher priority than 'Impression'

    →'B Channel' Impression is eliminated.

  3. The latest touchpoint will take the credit in case of touchpoints holding the same priority level.

    → 'B Channel' Click is eliminated.

  4. ⇒ The winning touchpoint for install event goes to 'C Channel' Click.

 

2. Attribution Rules for Deep-Linking Events

Attribution Process

________________________.png

Deep-linking event generally occurs almost instantly (less than 1 second) right after the tracking link is clicked. Thus, the 'click' touchpoint will be the winning touchpoint. However, it can also be recorded as 'unattributed' if that touchpoint was detected as fraudulent or the deep-linking event occurred without a tracking link (i.e. travels from page to page within an app).

Requirements

  1. It must NOT be a fraudulent deep-linking event.
    • Airbridge provides a variety of safeguards to detect and analyze potential fraudulent conversion events. You can also separately check whether these events fall into the fraud validation rule that you configured previously in Airbridge dashboard.
    • Fraudulent install events will be recorded as unattributed.

 

3. Attribution Rules for In-App Events

Attribution Process

Airbridge defines in-app events as subsequent events that only occur after app-install or deep-linking event. Hence, the attribution for subsequent events is credited to the last install or deep-linking event immediately before the subsequent event occurs.

Requirement

  1. It must NOT be a fraudulent in-app event.
    • Airbridge provides a variety of safeguards to detect and analyze potential fraudulent conversion events. You can also separately check whether these events fall into the fraud validation rule that you configured previously in Airbridge dashboard.
    • Fraudulent in-app events will be recorded as unattributed.
  2. Only in-app events that occur within the attribution window for the Install or Deep-linking event can be attributed.
    • Attribution Window is a period of time after an in-app event occurred within which install and deep-linking events can be attributed to the in-app event. If the attribution window for install event is set to 10 days, in-app events that occurred within 10 days followed by install event will be considered for attribution.
    • See Attribution Window Setting 

Attribution Scenarios

  • Scenario 1

    _______________________1.png

    • The above is the most basic in-app event attribution scenario. 'Sign-up' and 'Sign-in' events are attributed to App install event as they occurred within the attribution window. However, 'Add to Cart' and 'Purchase' event will be recorded as 'unattributed' as they failed to fall into the attribution window.
  • Scenario 2

    _______________________2.png

    • The default attribution window for install and deep-linking event is 30 days and 3 days respectively. In the above scenario, 'Sign-in' and 'Purchase' events will be attributed to the Install event. On the other hand, 'Add to Cart' event will be attributed to deep-linking event as deep-linking event is more recent event for 'Add to Cart' event.

 


Attribution Rules for Web Conversion Events

Attribution Process

  1. When a user visits an Airbridge Web SDK-installed website, our Web SDK automatically fetches the touchpoints that induced the user to visit the website. The possible touchpoint path is described as the following:
    1. 'Website visit' event via Airbridge Tracking Link.
    2. UTM information of the visited website address via UTM automatic parsing feature.
  2. The collected website visit touchpoints will be attributed to the web conversion event.
  3. If there was no touchpoint that induced the user to visit a website, the web conversion event will be recorded as unattributed.

Requirements

  1. Only the web conversion event that occurs within the attribution window will be attributed.
    • Attribution Window is a period of time after an web conversion occurred within which a website visit touchpoint can be attributed to the web conversion. If the attribution window is set to 3 days, the website touchpoint that occurred within 3 days after the website visit event will be attributed to web conversion event.
    • The default attribution window for web visit touchpoint is 3 days.
    • See Web Visit Touchpoint Attribution Window setting

Order of Priority

Web Conversion Events are prioritized based on its path of touchpoints. In case any touchpoint has the same priority, the latest created touchpoint will take the credit in accordance with the Last Click Attribution Model.

  1. The highest priority goes to the Airbridge Tracking Link of the website visit.
  2. The second priority goes to the touchpoint collected via automatic UTM parsing function.

Attribution Scenarios

  • Scenario 1

    _________________________________1.png

    • This is one of the scenarios where a user visits a website with Airbridge's Web SDK installed, and then performed series of in-app events. Any in-app events within the attribution window of 3 days, will be attributed to the website visit touchpoint (Tracking link 'click'). However, the rest of the in-app events out of attribution windows (in this scenario, 'Purchase' event) will be recorded as unattributed.
  • Scenario 2

    _________________________________2.png

    • This is a scenario where a user visited the website several times. The attribution for 'Sign-in event' will be given to the 'visit website' for the first time. And the attribution for 'Add to Cart' and 'Purchase' event will be given to the second website visit.

Was this article helpful?
0 out of 0 found this helpful