Set up AdTiming

AdTiming is an ad network integrated with Adjust. Our integration lets AdTiming receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with AdTiming for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with AdTiming.

Before you begin

Requirements

iOS / Android / Windows / Unity / React Native / Flutter / Adobe Air / Cordova / Marmalade / Xamarin / Cocos2d-x / Titanium / Corona

Select AdTiming and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > AdTiming. Select Next to move to the next screen.
  3. In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with AdTiming.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with AdTiming. To enable data sharing:

  1. Turn on Enabled

Once you enable data sharing with AdTiming, Adjust automatically sends AdTiming the following data, by default:

  • install
  • session
  • uninstall
  • reinstall
  • reattributionReinstall
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution

Set your data sharing options

If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:

  1. Separate data sharing options at the platform-level by selecting Use platform-specific settings.
  2. Set the same data sharing settings for multiple platforms by selecting Use global settings.

Now, under What will be shared by default?, review the activities that Adjust shares with AdTiming by default.

  • install
  • session
  • uninstall
  • reinstall
  • reattributionReinstall
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution

Send additional data

Choose the amount and type of data that you want to share with AdTiming through callbacks. AdTiming may use this information to optimize performance.

  1. Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with AdTiming:
  • Data from all attribution sources
  • Only data attributed to AdTiming

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets AdTiming receive your app’s uninstall and/or reinstall data measured by Adjust.

Note:

For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.

Sessions

Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means AdTiming will receive your app’s session activity.

Map events

Map events that you want to share to the values that AdTiming can receive. Data for unmapped events is not shared with AdTiming.

Under Map events, follow these steps to choose the in-app events you want to directly send to AdTiming.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with AdTiming.
  3. In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to. You might have to map an event to several values.
  4. Select Apply.

Now AdTiming will receive in-app event data for each of your linked events.

Configure your link and settings

You have the option to set your:

Create your link and share it with AdTiming

In the Setup review screen, you can review your choices. You can also go back and make changes to:

  • Your selected app
  • Data sharing options
  • Link structure parameters
  • User destinations
  • Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with AdTiming.

Once you’ve created your link, share it with AdTiming for placement in campaigns.

List of all parameters forwarded to AdTiming

AdTiming requires Adjust to send the following parameters (data points) with your callbacks:

PlaceholderInformation
{android_id}Android ID (Android only)
{city}Device city
{country_subdivision}Device subdivision of country, e.g., state
{country}Device two-character country code
{device_name}Device model number
{device_type}Device type
{environment}Current Adjust SDK environment setting
{event_name}Event name, as set in the Dashboard
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{ip_address}Device IP address
{is_reattributed}1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed
{language}Device two-character language code
{match_type}Attribution method
{mcc}Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier.
{mnc}Mobile network code: two-digit code. Use with the mobile country code to identify a device's carrier.
{os_name}Device operating system
{os_version}Operating system version number
{region}Device region code
{sdk_version}Adjust SDK version (per app)
{session_count}Number of sessions recorded by current Adjust SDK
{timezone}Device time zone
{user_agent}Incoming raw user agent
{activity_kind}Type of user activity
{app_id}Store App ID or Google Play Store
{app_version_short}App version number (Android), release-version-number for the bundle (iOS)
{click_time}Attributed click timestamp
{connection_type}Internet connection type
{cpu_type}CPU type
{created_at}Activity timestamp
{device_manufacturer}Device manufacturer name
{engagement_time}Engagement timestamp
{hardware_name}Hardware name
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{network_type}Network type
{reattributed_at}Reattribution timestamp
{reinstalled_at}Reinstall timestamp
{oaid}OAID device ID
{att_status}App Tracking Transparency Status. Possible values are 0 (Not determined), 1 (Restricted), 2 (Denied), 3 (Authorized), unknown