At a glance
| Field | Detail |
|---|---|
| What | Connect acquisition event postbacks to Unity Ads and collect LevelPlay ad revenue through the chosen MMP. |
| Who it matters to | App buyers using Adjust or AppsFlyer, especially when ad revenue informs campaign optimization. |
| Where | Unity Ads acquisition campaigns and LevelPlay revenue measurement. |
| When it applies | During integration setup or investigation of missing events and revenue. |
| Action | Verify revenue collection and outbound event sharing separately before reviewing campaign performance. |
Unity Ads postbacks and LevelPlay revenue collection serve different parts of measurement. Unity describes LevelPlay impression-level revenue as monetization data available in attribution dashboards, including Adjust and AppsFlyer. AppsFlyer separately documents sending ad revenue events to Unity Ads for optimization. Our suggested approach is to verify each connection independently, then check that the intended revenue reaches the buying campaign. Unity's LevelPlay overview and AppsFlyer's campaign guide establish those distinct functions.
Check access before setup
| Connection | Prerequisite | Suggested check |
|---|---|---|
| Adjust to Unity Ads | GAME ID and Admin, Editor, or Custom Editor permissions in Adjust. | Confirm access to the relevant app and partner settings. |
| AppsFlyer to Unity Ads | A Unity Ads account and Game ID. | Match game_id to install attribution. |
| LevelPlay revenue through Adjust SDK | RevWorks access and the mediation SDK plugin. | Review platform-specific SDK requirements before implementation. |
| LevelPlay revenue through Adjust API | RevWorks, mediation credentials, and the correct iOS Bundle ID in AppView. | Confirm which account and app the connection will cover. |
These requirements come from Adjust's Unity Ads setup, AppsFlyer's integration instructions, and Adjust's SDK and API revenue documentation. Confirm collection access and outbound sharing access separately: Adjust's Unity Ads page also identifies its Ad Revenue package as a requirement for sharing ad revenue with Unity Ads.
Connect acquisition events
If you use Adjust
Open Campaign Lab, select Partners, and add Unity Ads. Choose the app, enable the integration, and enter GAME ID. Review data-sharing sources and map each intended Adjust event to its corresponding partner event; Adjust says unmapped events are not shared.
Enable in-app revenue sharing for revenue amounts accompanying purchase events. For ad revenue, review the selected Ad Revenue Sources: leaving that field empty shares all integrated mediation sources. Review destinations and attribution settings, create the link, and provide the generated campaign URLs to Unity Ads. These steps follow Adjust's setup guide.
If you use AppsFlyer
Open Collaborate, Partner Integrations, and Marketplace. Select the app, find Unity Ads, and activate the partner. Keep activation enabled while working with it.
Enter game_id, enable in-app event postbacks, and add the events to share. Review user-source selection and revenue inclusion. AppsFlyer documents af_ad_revenue mapped to ad_revenue and warns against sending the same event under multiple names. Generate attribution links for the partner. AppsFlyer's instructions describe these controls.
Choose the LevelPlay revenue connection
LevelPlay supplies revenue information at device and impression level. Our interpretation is that the collection method should match the reporting decision's timing and detail requirements; simply seeing a revenue total does not establish which collection route supplied it. Unity's overview explains the underlying revenue scope.
| Approach | Source-backed capability | Limitation | Suggested check |
|---|---|---|---|
| Adjust SDK connection | Sends impression-level revenue in real time. | Requires a mediation plugin in the app implementation. | Check the released app contains the plugin and impression listener. |
| Adjust API connection | Retrieves revenue aggregated at device level. | Collection is scheduled daily and data may be revised. | Match reporting expectations to delayed collection. |
| Both connections | API collection operates at account level, including across platforms. | Overlapping SDK and API revenue can create duplicates. | Apply Ad Revenue Sources filters to the intended dataset and partner sharing. |
For the SDK route, Adjust instructs LevelPlay users to enable Ad Revenue Measurement and configure a listener for ad-unit impression data. Its plugin passes revenue to the Adjust SDK and then Adjust's servers. Adjust also notes that older app versions without the plugin can explain early discrepancies. Adjust SDK documentation.
For the API route, obtain the Secret Key and Refresh Token from My Account in LevelPlay. Connect the mediation account through Adjust DataWorks or arrange activation with the account manager. Adjust then pulls revenue for reporting in Datascape. Its documentation permits later revisions, so our suggested check is to record the retrieval method alongside the reporting period. Adjust API documentation.
Verify delivery and investigate gaps
Unity's dashboard checks for install data within two days of campaign launch and post-install event data within seven days. These are documented integration validation checks. Our suggested review should also inspect event identity and revenue content, rather than treating receipt alone as a complete measurement sign-off. Unity troubleshooting.
| Problem | Documented explanation | Suggested review or fix |
|---|---|---|
| Unity receives no installs | Integration settings or Game ID may be incorrect. | Match the advertiser Game ID and review sharing of attributed, unattributed, and organic installs. |
| Ad revenue is treated as purchases | Unity warns that this mapping can disrupt optimization. | Keep ad_revenue separate from purchase for the Adjust and AppsFlyer routes discussed here. |
| AppsFlyer event is missing from selection | AppsFlyer suggests triggering it on a device with a non-organic installation. | Trigger and recheck, or use its custom-event mapping option. |
| Adjust revenue appears duplicated | Account-level API collection can overlap SDK collection. | Review Ad Revenue Sources filters before using the total. |
The explanations above follow Unity, AppsFlyer, and Adjust.
What to review
- Check the app and advertiser Game ID across install attribution and event sharing.
- Compare purchase and ad revenue mappings with the campaign's intended outcome.
- Review collection access, outbound sharing, and selected revenue sources separately.
- Check SDK deployment coverage and API timing before interpreting missing revenue.
- Keep acquisition attribution, monetization revenue, and outbound postback evidence in the review record.
Our suggested measurement review can help align event definitions and the reporting basis for that record.



