Temporary attribution reporting

With Adjust’s support for temporary attribution, you can measure time-sensitive campaigns. In this guide, you can find information on how to view temporary attribution data.

View your temporary attribution data

You can view your temporary attribution data aggregated in Datascape or at a user-level via raw data exports.

In Datascape

Temporary Attribution users are not separated from other users in cohorts. Be aware of this as you analyze your data, especially when looking at the organic link.

Cohorts for temporary attribution

Recap

For this reason, depending upon the time period you are looking at, you may see some fluctuation in your cohort size. This is especially important when looking at organic users.

To tell if temporary attribution has changed your cohort size, you can compare its size over a certain period to that of day 0.

Tip:
Set your Attribution Source filter in Datascape to Dynamic. This means reattributions are taken into account, and is the correct setting for temporary attribution. If this filter is set to First, then users are shown against the link of their initial install, which overwrites any engagements’ temporary attribution window.

In raw data

Temporary attribution data is best analyzed in your raw data.

Placeholders

You can receive raw, unaggregated temporary attribution data using raw data exports. To do this, add the following placeholders to your CSV definition for cloud storage uploads or to your callback URL.

PlaceholderValue returned
{attribution_ttl}Reflects the temporary attribution window of the engagement.
  • For impressions: the impression-based attribution window.
  • For clicks: the click-based attribution window.
  • For installs: the temporary attribution window of the current attribution source.

The value returned is in hours.
{reattribution_attribution_ttl}Reflects the temporary reattribution window of the engagement.
  • " " if none is set.
  • For impressions: the impression-based temporary reattribution window.
  • For clicks: the click-based temporary reattribution window.
  • For reattributions: the temporary reattribution window of the current reattribution source.

The value returned is in hours.
{attribution_expires_at}Unix timestamp of when the current temporary attribution expires.
  • " " if never.
{reattribution_fallback_type}Reflects the engagement's reattribution fallback type.
  • " " if no temporary reattribution fallback set.
{last_fallback_time}Timestamp of when the user moved to the fallback source.
  • This placeholder is the only way of identifying users who are organic via fallback

When using temporary attribution, this is how we define and treat the {last_tracker}:

  • It is the link the device was on when the reattribution happened.
  • Before the fallback it acts like a typical reattribution.
  • After the fallback it is reset and acts like the reattribution never happened.
  • If it's temporarily reattributed and falls back to organic or the previous install attribution, it is " " (null).
  • If its temporarily reattributed and falls back to a previous reattribution, it is previous last link.