Set up TKO

TKO is an analytics partner integrated with Adjust. Our integration lets TKO receive data measured in Adjust through automated callbacks. Use this data with the partners' tools for analytics and insights.

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

Before you begin

Requirements

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

Select TKO and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > TKO. 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 TKO.
  4. Select Next.

Enable data sharing

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

  1. Turn on Enabled

Once you enable data sharing with TKO, Adjust automatically sends TKO 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 TKO 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 TKO through callbacks. TKO may use this information to optimize performance.

To send additional data, you can review and customize the following:

Sessions

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

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets TKO 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.

In-app revenue (from in-app purchases)

Sharing in-app revenue lets TKO receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.

Map events

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

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with TKO. This lets you:

  • Set individual events to manage campaign strategies for each platform.
  • Customize data sharing per platform.

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with TKO.
  3. Under Partner event, you need to select the TKO event that corresponds to the Adjust event.
    1. For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
      • Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
      • Select Use global mapping to map the same events for all platforms.
    2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
  4. Select Apply.

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

Map all events

If TKO supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now TKO will receive in-app event data for all your linked events.

Map parameters

You usually need to map parameters to share custom data with TKO.

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to TKO. This lets TKO receive custom event details for each of your linked events.

Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To share partner parameters to TKO, follow these steps.

  1. Set up partner parameters within the Adjust SDK.
  2. Under Set your data sharing options, select Parameters.
  3. Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
    1. Select Map parameter.
    2. In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
    3. In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.
Note:

If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.

Enable TKO for your app

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

Select Enable partner to enable TKO for your app. Analytics partners don't work with links for campaigns. Once enabled, our integration sends attribution and in-app event data via automated callbacks.

List of all parameters forwarded to TKO

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

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{android_id}Android ID (Android only)
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{device_name}Device model number
{environment}Current Adjust SDK environment setting
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{ip_address}Device IP address
{label}Value of the Adjust "label" parameter sent on click
{language}Device two-character language code
{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
{partner_parameters}Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
{referrer}Google Play Store referrer (Android only)
{reftag}Random device reference tag
{region}Device region code
{reporting_currency}Dashboard reporting ISO 4217 currency code
{reporting_revenue}Revenue, as reported in the Adjust Dashboard, in whole currency units
{revenue_float}Revenue, as sent from Adjust SDK, in whole currency units
{sdk_version}Adjust SDK version (per app)
{timezone}Device time zone
{tracking_limited}1 if tracking is limited, 0 if not
{user_agent}Incoming raw user agent
{activity_kind}Type of user activity
{adgroup_name}Adgroup name, as taken from the tracker
{app_name}Name of the app
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{click_time}Attributed click timestamp
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{impression_based}1 if impression-based engagement, 0 if not
{impression_time}Attributed impression timestamp
{install_begin_time}App download began timestamp (Android and Google Play Store only)
{install_finish_time}App download completion timestamp
{installed_at}Install (i.e., first app open) timestamp
{network_name}Network name, as taken from the tracker
{reattributed_at}Reattribution timestamp
{rejection_reason}Reason for a rejected attribution
{store}Target store of click
{tracker}6-character Adjust tracker token