Set up Cognant

Cognant is an ad network integrated with Adjust. Our integration lets Cognant receive attribution and in-app event data through automated callbacks.

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

Before you begin

Requirements

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

Credentials

MZ CODE

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

Select Cognant and your app in Campaign Lab

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

Enable data sharing

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

  1. Enter your MZ CODE.

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

  • click
  • install
  • session
  • reattribution
  • event

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 Cognant by default.

  • click
  • install
  • session
  • reattribution
  • event

Send additional data

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

  1. Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Cognant:
  • Data from all attribution sources
  • Only data attributed to Cognant

Sessions

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

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Cognant 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 Cognant can receive. Data for unmapped events is not shared with Cognant.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with Cognant. 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 Cognant.

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

Map all events

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

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

Map parameters

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

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

Configure your link and settings

You have the option to set your:

Create your link and share it with Cognant

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
  • Link structure parameters
  • User destinations
  • Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Cognant.

Once you’ve created your link, share it with Cognant for placement in campaigns.

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:

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{android_id_md5}Lowercase Android ID hex MD5 hash
{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
{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)
{inactive_user_definition}Inactivity period required for reattribution (hours)
{ip_address}Device IP address
{isp}Device internet service provider
{label}Value of the Adjust "label" parameter sent on click
{language}Device two-character language code
{last_time_spent}Length of user's last session, in seconds
{mac_md5}Uppercase MAC MD5 hash
{mac_sha1}Uppercase MAC SHA-1 hash
{match_type}Attribution method
{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)
{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
{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
{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
{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
{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_dashboard}Name of the app in the Adjust Dashboard
{app_name}Name of the app
{app_version_raw}App version number (Android), build-version-number for the bundle (iOS)
{app_version_short}App version number (Android), release-version-number for the bundle (iOS)
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{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
{created_at_hour}Activity timestamp, rounded down to the nearest hour
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{engagement_time_hour}Engagement timestamp rounded to the nearest hour
{engagement_time}Engagement timestamp
{impression_based}1 if impression-based engagement, 0 if not
{installed_at_hour}Install (i.e., first app open) timestamp rounded to the nearest hour
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{last_tracker_name}A reattributed user's previous tracker name
{last_tracker}6-character Adjust tracker token of a reattributed user's previous tracker
{network_name}Network name, as taken from the tracker
{reattributed_at_hour}Reattribution timestamp, rounded to the nearest hour
{reattributed_at}Reattribution timestamp
{rejection_reason}Reason for a rejected attribution
{store}Target store of click
{tracker_name}Current tracker name
{tracker}6-character Adjust tracker token
{google_ads_adgroup_id}Google Ads adgroup ID
{google_ads_campaign_id}Google Ads campaign ID
{google_ads_campaign_name}Google Ads campaign name
{google_ads_campaign_type}Google Ads campaign type
{google_ads_creative_id}Google Ads creative ID
{google_ads_keyword}Google Ads search keyword
{google_ads_matchtype}Google Ads search keyword and match type
{google_ads_network_subtype}Google Ads network subtype
{google_ads_network_type}Google Ads network type
{google_ads_placement}Google Ads ad placement
{google_ads_video_id}Google Ads video ID