Set up Cognant

Cognant is a network and Adjust module partner. Our integration lets Cognant receive attribution and app event data through automated callbacks.

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

Basic setup

To turn on Adjust’s integration with Cognant, 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 Cognant
  4. Enter your MZ CODE (contact your Cognant representative for help finding this)
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to Cognant to launch your campaign.

Cognant will receive callbacks for these activities:

  • click
  • install
  • session
  • event
  • reattribution

Advanced setup

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

Only forward data attributed to Cognant

Adjust sends Cognant your installs and reattributions across all ad platforms.

To stop Cognant from receiving data attributed to other ad platforms, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Cognant
  3. Turn on Attributed Only

Now Cognant will only receive data attributed to their own platform.

 

Forward in-app revenue

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

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

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

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

 

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

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

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

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

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

To forward app events to Cognant, follow these steps.

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

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

Partner specific setup instructions

When you activate the module, you will be able to choose which endpoint you want the callbacks to be sent to. You can enable the toggles for “Staging Endpoint Only” and “Production Endpoint Only”.

You are able to have one or both of the endpoint toggles enabled. Please remember that if both toggles ARE OFF, NO CALLBACKS will be sent.

List of all parameters forwarded to Cognant

Cognant 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
{adid} Adjust device ID (all platforms)
{adwords_adgroup_id} Google AdWords adgroup ID
{adwords_campaign_id} Google AdWords campaign ID
{adwords_campaign_name} Google AdWords campaign name
{adwords_campaign_type} Google AdWords campaign type
{adwords_creative_id} Google AdWords creative ID
{adwords_keyword} Google AdWords search keyword
{adwords_matchtype} Google AdWords search keyword and match type
{adwords_network_subtype} Google AdWords network subtype
{adwords_network_type} Google AdWords network type
{adwords_placement} Google AdWords ad placement
{adwords_video_id} Google AdWords video ID
{android_id_md5} Lowercase Android ID hex MD5 hash
{android_id} Android ID (Android only)
{api_level} API level (Android only)
{app_id} Store App ID or Google Play Store
{app_name_dashboard} Name of the app in the Adjust Dashboard
{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_referer} Referrer header from click
{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
{created_at_hour} Activity timestamp, rounded down to the nearest hour
{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
{gclid} Google click ID
{gps_adid_md5} Lowercase hex MD5 hash of Google Play Store advertising ID
{gps_adid} Google Play Store advertising ID
{idfa_md5_hex} IDFA hex MD5 hash
{idfa_md5} IDFA base64 MD5 hash
{idfa_upper} Uppercase IDFA
{idfa} ID for advertisers (iOS only)
{idfv} Uppercase iOS ID for vendors
{impression_attribution_window} Attribution window settings for impression matching (hours)
{impression_based} 1 if impression
{inactive_user_definition} Inactivity period required for reattribution (hours)
{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
{isp} Device internet service provider
{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_name} A reattributed user's previous tracker name
{last_tracker} 6
{mac_md5} Uppercase MAC MD5 hash
{mac_sha1} Uppercase MAC SHA
{match_type} Attribution method
{network_name} Network name, as taken from the tracker
{nonce} Random lowercase alphanumeric string (unique per callback)
{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
{publisher_parameters} Custom publisher parameters collected by the Adjust SDK (never displayed in Adjust Dashboard)
{random} Random number (unique per callback)
{reattributed_at_hour} Reattribution timestamp, rounded to the nearest hour
{reattributed_at} Reattribution timestamp
{reattribution_attribution_window} Attribution window settings for reattribution (hours)
{referrer} Google Play Store referrer (Android only)
{reftag} Random device reference tag
{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_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)
{search_term} Google organic search term
{store} Target store of click
{time_spent} Length of user's current session, in seconds
{timezone} Device time zone
{tracker_name} Current tracker name
{tracker} 6
{tracking_enabled} 1 if tracking is enabled, 0 if not
{tracking_limited} 1 if tracking is limited, 0 if not
{tweet_id} Unique tweet ID
{twitter_line_item_id} Twitter line item ID
{user_agent} Incoming raw user agent
{win_hwid} Windows Store hardware ID
{win_udid} Windows Phone unique device ID