Set up Mintegral

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

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

Before you begin

Requirements

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

Select Mintegral and your app in Campaign Lab

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

Enable data sharing

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

  1. Turn on Enabled

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

  • install
  • session
  • 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 Mintegral by default.

  • install
  • session
  • event
  • rejectedInstall

Send additional data

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

In-app revenue (from in-app purchases)

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

Ad revenue (from ad views)

Ad revenue sharing lets Mintegral receive user ad revenue data. This lets Mintegral use ad revenue data to optimize your user targeting and campaigns.

Growth solution:

This feature is available with Adjust’s RevWorks package. To purchase our RevWorks package, contact your sales representative.

To share ad revenue to Mintegral, select one or more Ad Revenue Sources.

  • If you leave this field empty, we send ad revenue data from all integrated mediation sources.

Sessions

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

Map parameters

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

Map events

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

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Mintegral.
  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 Mintegral 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 Mintegral. This lets Mintegral 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 Mintegral, 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.

Configure your link and settings

You have the option to set your:

Create your link and share it with Mintegral

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 Mintegral.

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

List of all parameters forwarded to Mintegral

Mintegral 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)
{city}Device city
{click_attribution_window}Attribution window settings for device matching (hours)
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{device_name}Device model number
{device_type}Device type
{event_name}Event name, as set in the Dashboard
{fire_adid}Fire OS advertising identifier
{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}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
{mac_sha1}Uppercase MAC SHA-1 hash
{match_type}Attribution method
{mcc}Mobile country code: three-digit code identifying a device's country. Use with the mobile network code to identify a device's carrier.
{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
{revenue_usd}Revenue, in US dollars
{revenue}Revenue, as sent from Adjust SDK in cents
{sdk_version}Adjust SDK version (per app)
{tracking_limited}1 if tracking is limited, 0 if not
{user_agent}Incoming raw user agent
{adgroup_name}Adgroup name, as taken from the tracker
{app_id}Store App ID or Google Play Store
{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
{conversion_duration}Time between click and install or reattribution in seconds
{created_at}Activity timestamp
{device_manufacturer}Device manufacturer name
{impression_based}1 if impression-based engagement, 0 if not
{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
{network_type}Network type
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{rejection_reason}Reason for a rejected attribution
{ad_impressions_count}Number of mobile ads served to end users
{ad_revenue_network}Ad network that displayed the ad
{ad_revenue_unit}Ad unit that generated the revenue
{ad_revenue_placement}User placement, as defined on the platform
{oaid_md5}OAID MD5 hash
{oaid}OAID device ID
{ad_mediation_platform}Mediation platform name