At a glance
| Field | Detail |
|---|---|
| What | Connect AppLovin to an MMP and define event postbacks. |
| Who it matters to | App buyers using AppsFlyer or Adjust. |
| Where | The selected app's partner integration; Adjust lists Axon by AppLovin. |
| When it applies | Before launch or when auditing missing post-install signals. |
| Action | Review activation, event mapping, sharing scope and delivery evidence. |
An AppLovin MMP integration needs a defined path from the app event to the network's postback. The official AppsFlyer and Adjust guides describe separate controls for activation, event mapping and data sharing. Our suggested approach is to document each control before using the integration's output to assess acquisition performance.
Prepare the app and credentials
Use the documentation for your MMP when completing its fields. These prerequisites come from AppsFlyer's AppLovin guide and Adjust's setup guide.
| MMP | Prerequisite or input | Suggested check |
|---|---|---|
| AppsFlyer | An AppLovin account and its SDK key | Confirm access to the account and select the intended app. |
| AppsFlyer | The event name received from the app SDK or server-to-server integration | Record the source name and corresponding partner identifier. |
| Adjust | Admin, Editor or Custom Editor permissions, plus SDK KEYS | Confirm the operator can configure the integration. |
| Adjust | Events mapped to corresponding partner events | Identify the events to share for each platform. |
Treat the event list as a measurement specification. Record what each event means in the app before mapping it to a partner label. An internal purchase name and a network event identifier serve different roles; keeping both in the review record makes later troubleshooting more precise.
Connect through your MMP
In AppsFlyer, select the app, find AppLovin through Partner Integrations and activate the partner. AppsFlyer says activation must remain enabled while working with the partner. Its integration guide requires the SDK key in both the general and in-app event settings. Enable in-app event postbacks and add the events to map.
AppLovin's AppsFlyer instructions locate the key under Account > Keys in the AppLovin dashboard. They also specify a Lifetime in-app event postback window. Review that setting explicitly when checking an existing integration against the network's instructions.
In Adjust, open Campaign Lab, choose Partners, then add Axon by AppLovin and select the app. Enter the SDK KEYS and configure data sharing. Adjust supports platform-specific or global sharing settings and event mappings. Review the setup, create the link and share it for campaign placement. Adjust states that creating the link enables the integration and data sharing.
Define the event payload and audience
AppLovin's AppsFlyer instructions distinguish event purpose from payload contents:
| App event category | AppLovin mapping | Included data |
|---|---|---|
| App opens | landing | No values or revenue |
| Revenue events | checkout | Values and revenue |
| Other events | postinstall | No values or revenue |
That guide specifies sharing from all media sources, including organic. AppsFlyer's postback configuration documentation explains that partner-only sharing limits postbacks to users attributed to that partner. With broader sharing, postbacks for other partners do not contain attribution data. Keep the scope of received postbacks distinct from the scope of users acquired by AppLovin.
AppsFlyer also distinguishes sending an event without parameters, sending parameters without revenue, and sending parameters with revenue. Revenue sharing requires a populated revenue field; enabling the option cannot supply a missing value. Event names are case-sensitive, and adding a custom name in the dashboard does not implement that event in the app.
For Adjust, revenue sharing requires mapping the events that generate revenue. Unmapped events are not shared. Our suggested check is to review the event map and revenue setting together before treating the connection as ready.
Verify recording and delivery separately
AppsFlyer's troubleshooting guide supports this diagnostic sequence:
| Problem | Documented check or next step |
|---|---|
| Event absent from AppsFlyer | Check Activity or raw data and the SDK configuration. |
| Event recorded but no expected postback | Check activation, event mapping, conditions, sharing scope and postback window. |
| Postback sent but absent from the partner platform | Inspect the relevant Postbacks report under Raw Data Export, then contact the partner. |
Check the configuration that applied when the event occurred. AppsFlyer identifies Audit log as a way to review whether partner activation was enabled then. It also notes that events outside the postback window can remain recorded without being sent.
For iOS, review privacy settings separately. AppsFlyer says unsupported or unconfigured Advanced Privacy can prevent aggregated postbacks. A missing postback therefore needs investigation before it becomes evidence of missing app activity.
What to review
- Check the selected app, credentials and configuration owner.
- Compare source event names with partner mappings, including capitalization.
- Review all-source versus partner-only sharing and revenue payload choices.
- Check platform-specific settings before applying a shared configuration.
- Keep evidence of event recording and postback delivery with the configuration review.
Use the measurement data-path review to connect these checks to your event definitions and reporting basis.



