Mintegral

Guide · 30 Oct 2026

Mintegral MMP integration: verify event mapping before launch

A setup checklist for app buyers using Adjust or Branch, with separate checks for links, forwarded events, and Mintegral event review.

G2P Media · · 5 min read

Mintegral MMP integration: verify event mapping before launchMintegral

At a glance

FieldDetail
WhatConnect an MMP, map forwarded events to Mintegral events, and verify each stage.
Who it matters toApp acquisition teams using Adjust or the new Branch experience with Mintegral.
WhereThe MMP dashboard and Mintegral AppGrowth; follow the route for your MMP.
When it appliesDuring setup or investigation of missing install and in-app event postbacks.
ActionTrace a test event through the MMP and Mintegral before treating setup as complete.

Mintegral MMP integration requires checking what the measurement partner sends and how Mintegral interprets it. Mintegral's documentation says events standardized by an MMP still need manual mapping to Mintegral events. Our suggested approach is to document the outgoing event name, its intended meaning, and the corresponding Mintegral event together. This gives the buyer a concrete setup record to verify. See the Event Mapping Guide.

Check prerequisites

Use the requirements for your chosen route. Adjust and Branch have separate account permissions and testing tools; completing either dashboard's connection does not establish that every intended event is arriving.

PrerequisiteDocumented requirement or capabilitySuggested check
Adjust accessAdmin, Editor, or Custom Editor permissions are required.Confirm the person configuring Mintegral has an eligible role.
Branch accessAd partner integration availability depends on the Branch plan; Branch admin permissions and Mintegral admin access are required.Confirm account access before assigning setup work.
Event identityMintegral maps received postback event names to its own event definitions.Record the name leaving the MMP, including any standardization.
Adjust test deviceAttribution testing starts with a device without the app installed and not already saved in Adjust.Prepare the device before testing the campaign link.

These checks come from the Adjust setup guide, Branch setup guide, Mintegral mapping guide, and Adjust Testing Console documentation.

Adjust route

In Campaign Lab, select Partners, then New partner and Mintegral, and choose the app. Enable data sharing, select the events to share, and map them to the corresponding partner events. Adjust explicitly says unmapped events are not shared. For purchase revenue, its guide also requires mapping the revenue-generating events and enabling in-app revenue sharing.

Review the selected app, sharing options, destinations, and attribution settings before creating the link. Adjust produces click and impression URLs to share with Mintegral. These are documented setup actions, rather than evidence that downstream reporting has passed verification. Follow Adjust's Mintegral instructions.

Branch route

In the new Branch experience, navigate to Configuration > Ad Partners > Mintegral and enable the integration. Branch says activation needs no credentials and automatically enables postbacks, including INSTALL. Additional events require further postback configuration. Create a Branch Ad Link for the campaign.

Branch uses global app attribution settings by default, with a partner-specific override available. Review that choice separately from event delivery so the team knows which settings govern the connection. See Enable Mintegral (New).

Map the received event in Mintegral

In AppGrowth, open User Acquisition > Delivery Setting > Manage Event. Match the received name to the intended Mintegral event. Its definitions distinguish account registration, trial starts, purchases, and other advertiser-defined actions. Choose by the action's meaning rather than assuming every conversion represents a purchase.

Mintegral's Adjust guide describes alternative locations for mapping a purchase event to Purchase: in Adjust or in Mintegral. It says that purchase-name mapping does not need to be repeated in both locations. Keep this scoped instruction separate from the broader task of checking the final mapping visible in AppGrowth. See Mintegral's Adjust Tracking guide.

Mapping also initiates a review process once postback data is available. Mintegral says a failed mapping review does not stop ad delivery. Our interpretation is that continued delivery is insufficient evidence of a correct event setup. Follow the status message and resolve disputed classifications with the account team. See the review process documentation.

Verify the path and troubleshoot

For Adjust, click the test link, install and open the app, then inspect the device in Testing Console using its advertising ID. Check attribution and event activity. If you clear the device between tests, Adjust says to reinstall before triggering an in-app event. This verifies the MMP stage; it should be followed by a check in Mintegral.

Problem or observationDocumented distinctionSuggested check or fix
Adjust shows no clickMintegral's Adjust guide points to the tracking link.Check that the tested URL is correct.
Adjust shows a click but no installMintegral's guide points to the promoted app's SDK integration.Investigate the app integration before changing event mapping.
Adjust shows click and install, but Mintegral reports no postbackMintegral's guide points to install postback configuration.Review the Mintegral install postback settings in Adjust.
Mintegral shows no data for reviewA mapped event without incoming postbacks cannot enter review.Check event forwarding and receipt before expecting a review result.
An event passes review, then its mapping changesMintegral says changing a passed mapping triggers another review.Recheck status after changing the event classification.

The diagnostic sequence follows Mintegral's Adjust guide and mapping review documentation.

For Branch, verify app events in Liveview, inspect attributed installs and events filtered to Mintegral in Analysis, and confirm forwarded events in Mintegral reporting. Branch documents these as separate checks. A universal event-arrival deadline is not specified in the cited documentation. See Branch's verification guidance.

What to review

  • Check the app and platform attached to the campaign link.
  • Compare the outgoing event name with the Mintegral mapping and business action.
  • Check purchase revenue sharing separately from event-name mapping.
  • Keep MMP receipt, Mintegral receipt, and mapping-review status as separate verification records.

These are suggested acceptance checks. Use an event and reporting data-path review to keep the definitions consistent when handing the setup from measurement owners to buyers.

Discuss your app.

Discuss your app