At a glance
| Field | Detail |
|---|---|
| What | Configure which app events, user populations and revenue data reach Liftoff. |
| Who it matters to | App advertisers connecting a mobile measurement partner (MMP) to Liftoff. |
| Where | AppsFlyer, Adjust and Branch integrations; Branch lists iOS and Android support. |
| When it applies | During integration setup or a review of existing postback sharing. |
| Action | Check the selected events and sharing scope, then verify recording and delivery. |
Liftoff postbacks require decisions about event selection, attribution source and payload contents. Our suggested approach is to document those choices before enabling the integration, then check the app event and its delivery separately. The official guides below describe different controls, so follow the section for your existing MMP.
Check prerequisites
| MMP | Documented prerequisite | Suggested preparation |
|---|---|---|
| AppsFlyer | An account with Liftoff. | Confirm the app and partner account before integration. |
| Adjust | Admin, Editor or Custom Editor permissions. | Confirm who can change sharing settings. |
| Branch | Ad partner integrations enabled for the account, admin access, SDK event tracking and active Liftoff campaigns. | Check plan availability and the implemented events. |
These requirements come from the AppsFlyer setup guide, Adjust setup guide and Branch setup guide. Branch states that integration availability varies by plan.
Connect the app and select events
AppsFlyer
In Collaborate > Partner Integrations > Marketplace, select the app, find Liftoff and select Integrate. Turn on Activate partner in the Integration tab and keep it active while working with Liftoff.
Enable In-app event postbacks, choose selected events or all events, set each event's sending option and payload, then save. AppsFlyer notes that reporting all events excludes af_app_opened. Generate attribution links in the Attribution link tab and send them to Liftoff. These steps follow AppsFlyer's Liftoff documentation.
Adjust
In Campaign Lab > Partners, select New partner > Liftoff, choose the app and enable data sharing. Select the attribution sources to share, then map the Adjust events to the corresponding Liftoff events. Unmapped events are not shared.
For purchase revenue, enable in-app revenue sharing and map the revenue-generating events. Review the app, sharing choices, destinations and attribution settings before creating the link, then share it with Liftoff. Follow the Adjust integration guide for the actual configuration.
Branch
This section applies to the new Branch experience. Navigate to Configuration > Ad Partners > Liftoff and select Enable Liftoff. Branch says postback activation requires no credentials and automatically activates its standard event set.
Place the Branch Ad Link in the Liftoff campaign to configure click and impression tracking. Cost-data setup is separate. Branch documents these distinctions in its Liftoff guide.
Compare sharing controls before saving
| Integration | Source-backed control | Limitation | Suggested check |
|---|---|---|---|
| AppsFlyer | Share event data without values, with values excluding revenue, or with values including revenue. | Revenue is included only if present in the event. | Check the payload choice against the intended outcome. |
| Adjust | Share only Liftoff-attributed data or data from all attribution sources; map events by platform. | Unmapped events are not forwarded. | Review each platform's event selection. |
| Branch | Send all events controls whether active postbacks include unattributed events. | Turning it off limits active postbacks to attributed events. | Review this control alongside each postback's status. |
The AppsFlyer and Adjust controls are documented in their setup guides above. For Branch, use the general integration guide. It also describes adding a postback through Postback config > Add new postback, selecting the event and choosing Create. Its URL preview exposes the values that will be sent.
Our interpretation: event selection and attribution-source scope deserve separate sign-off. Selecting a purchase event does not, by itself, document whether revenue or unattributed activity should be shared.
Verify recording and delivery separately
Adjust's Testing Console guide describes checking a test device's attribution and event activity. Use a device without the app installed and not already saved in Adjust, follow the Adjust link, install and open the app, then inspect the device in Testing Console. Enter its advertising ID and select View device data. After clearing a device between tests, reinstall before triggering events.
For AppsFlyer, check event recording in the Activity dashboard or raw data, then inspect the relevant Postbacks report under Reports > Raw Data Export. Its troubleshooting guide distinguishes missing app events from postbacks sent but absent in the partner's platform.
For Branch, its Liftoff guide recommends checking Liveview for app events, Analysis dashboards filtered to Liftoff, and Liftoff reporting for forwarded events. Our suggested acceptance record should capture both sides of that check.
Investigate missing postbacks
AppsFlyer's troubleshooting guide supports these checks:
| Symptom | Documented possible cause | Suggested check |
|---|---|---|
| Expected postbacks are absent | Partner activation or event postbacks were off. | Check both toggles, including their state when the event occurred. |
| An event is recorded but not forwarded | Event configuration, a condition or the postback window prevents sending. | Review the event's configuration and applicable window. |
| A sent postback is absent in Liftoff | The partner platform is not displaying it. | Preserve the sending evidence and contact the partner. |
AppsFlyer also documents SDK sharing filters and restrictions on third-party data sharing. Review those limits when selecting a broader source population; an all-sources setting does not establish that every user's data can be forwarded.
What to review
- Check the app, platform and exact events selected for Liftoff.
- Review attributed-only versus broader sharing independently from event selection.
- Check revenue inclusion and event recording before accepting delivery as verified.
- Keep a record of the settings and the evidence from both platforms.
Use the measurement data-path review to document event definitions and the reporting basis alongside these checks.



