Languages 

Set up Mintegral

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

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

Basic setup

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

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select the add (+) icon next to Mintegral
  4. Turn on Enabled
  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 Mintegral to launch your campaign.

Mintegral will receive callbacks for these activities:

  • install
  • session
  • event
  • rejectedInstall

Advanced setup

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

Forward in-app revenue

In-app revenue forwarding lets Mintegral receive revenue amounts along with your revenue event data.

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

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

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

Note: Link at least one [revenue event] to Mintegral before turning on In-App Revenue Forwarding.

Forward sessions

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

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

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

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

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

Now Mintegral 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 in-app events

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

To forward in-app events to Mintegral, follow these steps.

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

Now Mintegral will receive in-app event data for each of your linked events.

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
{device_name}Device model number
{device_type}Device type
{event_name}Event name, as set in the Dashboard
{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
{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