Set up TrafficGuard

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

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

Basic setup

To turn on Adjust’s integration with TrafficGuard, 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 TrafficGuard
  4. Enter your IDENTIFIER and MEASUREMENT API KEY (contact your TrafficGuard representative for help finding these)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

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

  • install
  • rejected install
  • session
  • event

Advanced setup

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

Forward in-app revenue

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

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

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

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

 

Note: Link at least one revenue event to TrafficGuard 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 TrafficGuard, follow these steps.

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

Now TrafficGuard 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 TrafficGuard.

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 TrafficGuard, 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 > TrafficGuard
  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 TrafficGuard name.
  7. Select Save

Now TrafficGuard 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 TrafficGuard receive app event data. You can link every app event in Adjust to a preset TrafficGuard name or a custom event name.

To forward app events to TrafficGuard, follow these steps.

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

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

List of all parameters forwarded to TrafficGuard

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

Placeholder Information
{activity_kind} Type of user activity
{adgroup_name} Adgroup name, as taken from the tracker
{api_level} API level (Android only)
{app_id} Store App ID or Google Play Store
{app_name} Name of the app
{app_version_raw} App version number (Android), build
{app_version_short} App version number (Android), release
{app_version} App version number (Android), build
{campaign_name} Campaign name, as taken from the tracker
{city} Device city
{click_attribution_window} Attribution window settings for device matching (hours)
{click_time_hour} Attributed click timestamp, rounded to the nearest hour
{click_time} Attributed click timestamp
{connection_type} Internet connection type
{conversion_duration} Time between click and install or reattribution in seconds
{country_subdivision} Device subdivision of country, e.g., state
{country} Device two
{cpu_type} CPU type
{created_at_hour} Activity timestamp, rounded down to the nearest hour
{created_at_milli} Activity timestamp with millisecond placeholders
{created_at} Activity timestamp
{creative_name} Creative name, as taken from the tracker
{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
{engagement_time_hour} Engagement timestamp rounded to the nearest hour
{engagement_time} Engagement timestamp
{environment} Current Adjust SDK environment setting
{gps_adid} Google Play Store advertising ID
{idfa} ID for advertisers (iOS only)
{impression_attribution_window} Attribution window settings for impression matching (hours)
{impression_based} 1 if impression
{impression_time_hour} Attributed impression timestamp, rounded to the nearest hour
{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_hour} Install (i.e., first app open) timestamp rounded to the nearest hour
{installed_at} Install (i.e., first app open) timestamp
{ip_address} Device IP address
{is_organic} 1 if organic traffic, 0 if non
{is_reattributed} 1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed
{language} Device two
{last_time_spent} Length of user's last session, in seconds
{lifetime_session_count} Number of sessions recorded across entire user lifetime
{match_type} Attribution method
{network_name} Network name, as taken from the tracker
{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)
{reattributed_at_hour} Reattribution timestamp, rounded to the nearest hour
{reattributed_at} Reattribution timestamp
{referral_time} User landed on app Play Store page timestamp (Android and Google Play Store only)
{referrer} Google Play Store referrer (Android only)
{region} Device region code
{rejection_reason} Reason for a rejected attribution
{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
{revenue_usd_cents} Revenue, in US cents
{revenue_usd} Revenue, in US dollars
{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