Set up AdTriba

AdTriba is an Adjust module partner. Our integration lets AdTriba receive attribution and app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to AdTriba. Then, use our advanced setup instructions to customize what information AdTriba receives.

Basic setup

To turn on Adjust’s integration with AdTriba, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select Add (+icon) next to AdTriba
  4. Enter your TRACKER ID (contact your AdTriba representative for help finding this)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. AdTriba will receive callbacks for these activities:

  • click
  • event
  • install
  • reattribution
  • session

Advanced setup

Choose which data AdTriba receives from Adjust by customizing your setup.

Forward in-app revenue

Revenue forwarding lets AdTriba receive revenue amounts along with your revenue event data.

To forward in-app revenue to AdTriba, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > AdTriba
  3. Turn on In-App Revenue Forwarding

Now AdTriba will receive the revenue amount for every tracked transaction.

 

Note: Link at least one revenue event to AdTriba before turning on Revenue Forwarding

 

Forward sessions

Adjust does not automatically send session callbacks due to the high volume of sessions.

To forward in-app sessions to AdTriba, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > AdTriba
  3. Turn on Session Forwarding

Now AdTriba will receive your app’s session activity.

 

Forward custom data

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to AdTriba.

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

To forward partner parameters to AdTriba, follow these steps.

  1. Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
  2. In the Adjust dashboard, find your app and select your app options caret (^)
  3. Select Partner Setup > AdTriba
  4. Turn on Parameter Forwarding
  5. Select Partner Parameter Mapping
  6. In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding AdTriba name.
  7. Select Save

Now AdTriba will receive custom event details for each of your linked events.

 

Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.

 

Forward app events

Event linking lets AdTriba receive app event data. You can link every app event in Adjust to a preset AdTriba name or a custom event name.

To forward app events to AdTriba, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup >AdTriba > Event Linking
  3. Find the event you want to link and update the field with a AdTriba event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

Now AdTriba will receive app event data for each of your linked events.

List of all parameters forwarded to AdTriba

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

Placeholder Information
{adgroup_name} Adgroup name, as taken from the tracker
{adid} Adjust device ID (all platforms)
{android_id} Android ID (Android only)
{app_id} Store App ID or Google Play Store
{app_name_dashboard} Name of the app in the Adjust Dashboard
{app_version} App version number (Android), build
{campaign_name} Campaign name, as taken from the tracker
{click_time} Attributed click timestamp
{country} Device two
{created_at} Activity timestamp
{creative_name} Creative name, as taken from the tracker
{currency} Original ISO 4217 currency code sent from Adjust SDK
{device_name} Device model number
{device_type} Device type
{engagement_time} Engagement timestamp
{environment} Current Adjust SDK environment setting
{gclid} Google click ID
{gps_adid} Google Play Store advertising ID
{idfa} ID for advertisers (iOS only)
{idfv} Uppercase iOS ID for vendors
{impression_based} 1 if impression
{installed_at} Install (i.e., first app open) timestamp
{ip_address} Device IP address
{is_organic} 1 if organic traffic, 0 if non
{label} Value of the Adjust "label" parameter sent on click
{language} Device two
{last_time_spent} Length of user's last session, in seconds
{last_tracker} 6
{mac_sha1} Uppercase MAC SHA
{match_type} Attribution method
{network_name} Network name, as taken from the tracker
{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
{random_user_id} Random user ID (per device)
{random} Random number (unique per callback)
{reattributed_at} Reattribution timestamp
{referrer} Google Play Store referrer (Android only)
{reftag} Random device reference tag
{revenue} Revenue, as sent from Adjust SDK in cents
{store} Target store of click
{time_spent} Length of user's current session, in seconds
{timezone} Device time zone
{tracker} 6
{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