Set up ACTIN

ACTIN is an analytics network integrated with Adjust. Our integration lets ACTIN receive attribution and in-app event data through automated callbacks. Use this data with the partners' tools for analytics and insights.

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

Before you begin

Requirements

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

Credentials

ACTIN TOKEN

  • For help finding your credentials, contact your ACTIN representative.

Select ACTIN and your app in Campaign Lab

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

Enable data sharing

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

  1. Enter your ACTIN TOKEN.

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

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

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 ACTIN by default:

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

Send additional data

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

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

In-app revenue (from in-app purchases)

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

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets ACTIN 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 ACTIN will receive your app’s session activity.

Map parameters

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

Map events

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

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with ACTIN.
  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 ACTIN will receive in-app event data for each of your linked events.

Map parameters

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to ACTIN. This lets ACTIN 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 ACTIN, follow these steps.

  1. Set up partner parameters within the Adjust SDK: iOS, Android
  2. Check the Parameters data sharing checkbox.
  3. Map your events.
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 ACTIN 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 ACTIN 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 ACTIN

ACTIN 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)
{api_level}API level (Android only)
{city}Device city
{click_attribution_window}Attribution window settings for device matching (hours)
{country_subdivision}Device subdivision of country, e.g., state
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{deeplink}Deeplink URL appended to click URL
{device_name}Device model number
{device_type}Device type
{environment}Current Adjust SDK environment setting
{fire_adid}Fire OS advertising identifier
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{idfv}Uppercase iOS ID for vendors
{impression_attribution_window}Attribution window settings for impression matching (hours)
{ip_address}Device IP address
{isp}Device internet service provider
{language}Device two-character language code
{mac_md5}Uppercase MAC MD5 hash
{match_type}Attribution method
{nonce}Random lowercase alphanumeric string (unique per callback)
{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
{postal_code}Device postal code of IP address
{random_user_id}Random user ID (per device)
{random}Random number (unique per callback)
{reattribution_attribution_window}Attribution window settings for reattribution (hours)
{reftag}Random device reference tag
{reporting_currency}Dashboard reporting ISO 4217 currency code
{reporting_revenue}Revenue, as reported in the Adjust Dashboard, in whole currency units
{revenue}Revenue, as sent from Adjust SDK in cents
{sdk_version}Adjust SDK version (per app)
{session_count}Number of sessions recorded by current Adjust SDK
{time_spent}Length of user's current session, in seconds
{timezone}Device time zone
{tracking_enabled}1 if tracking is enabled, 0 if not
{tracking_limited}1 if tracking is limited, 0 if not
{user_agent}Incoming raw user agent
{win_adid}Windows advertising identifier
{win_hwid}Windows Store hardware ID
{win_naid}Windows Store network adapter ID
{win_udid}Windows Phone unique device ID
{activity_kind}Type of user activity
{adgroup_name}Adgroup name, as taken from the tracker
{app_id}Store App ID or Google Play Store
{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
{connection_type}Internet connection type
{conversion_duration}Time between click and install or reattribution in seconds
{created_at_milli}Activity timestamp with millisecond placeholders
{creative_name}Creative name, as taken from the tracker
{engagement_time}Engagement timestamp
{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
{is_organic}1 if organic traffic, 0 if non-organic
{last_session_time}Last session timestamp
{network_name}Network name, as taken from the tracker
{reattributed_at}Reattribution timestamp
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{reinstalled_at}Reinstall timestamp
{rejection_reason}Reason for a rejected attribution
{store}Target store of click
{time_to_reinstall}Time between latest app uninstall and subsequent reinstall in seconds
{time_to_uninstall}Time between app install (or latest reinstall) and subsequent uninstall in seconds
{tracker_name}Current tracker name
{uninstalled_at}Uninstall timestamp (estimation based on last session time)