Attribution Window Setup
  • 09 May 2024
  • 1 Minute to read
  • Dark
    Light

Attribution Window Setup

  • Dark
    Light

Article summary

Attribution Window Setup Guide

Tenjin has expanded its attribution configuration capabilities, now allowing advertisers to set attribution windows at both the App level and the App + Ad Network level.
You can customize settings for both click-through and view-through attribution at the App level and App + Ad Network level. This setting provides greater flexibility and control, enabling precise optimization of your apps and advertising network channels for improved attribution results.

To customize the attribution window settings please follow these steps below -

  1. Go into CONFIGURE (at the top of the main menu) → Apps and select the App and click on ‘Attribution’ tab.
    image.png

App Attribution Window

  1. In the Attribution tab, you will see ‘App Attribution Windows’ setting up at the top. Here you can edit the App window for -
    1. Click-Through Attribution
      1. Device Matching (Default 7 days)
      2. Turn on/off Probabilistic Matching (On by default)
    2. View-Through Attribution
      1. Device Matching (Default 1 hour)
      2. Turn on/off Probabilistic Matching (On by Default)

image.png

App + Ad Network Attribution Window

  1. If you want to use a non default attribution window for a specific network, you can do this under this section. For this, select the Channel from the dropdown. For e.g. Google Ads
  2. Now you will see the ‘App x Ad Network Attribution Windows’ settings section. (This will override the App settings you did on Step 1)
  3. Turn ‘On’ Override App Settings toggle on the top right to make changes at the Ad Network level, and change the window.

image.png

NOTE

App + Ad Network Attribution Window settings will override the settings done on the App Attribution Window. If you make no changes, Tenjin will continue using default app attribution window settings.

If you have any questions or issues, please contact us at support@tenjin.com


Was this article helpful?

What's Next