Documentation

Support

Unity Ads User Acquisition

Campaigns

Attribution

Open User Acquisition dashboard

Unity Ads User Acquisition

AppsFlyer advanced ad metrics and data-sharing reference

Explore AppsFlyer's Enriched Engagement ad metrics and ad revenue data-sharing options.
Read time 3 minutesLast updated 16 hours ago
AppsFlyer offers unique ad metrics and Ad revenue options. Review the following information to ensure you configure your AppsFlyer data-sharing options correctly.

Enriched Engagement

AppsFlyer’s Enriched Engagement Types (EET) provide additional logic for deeper user-engagement tracking, which can cause discrepancies between AppsFlyer and Unity metrics.

Engagement Type

AppsFlyer Definition

Unity Ads Equivalent

Counted As (AppsFlyer)

Counted As (Unity)

Engaged ViewA meaningful interaction within rewarded or skippable video ads
  • Rewarded video: completed
  • Interstitial: 10 s or longer View
ImpressionVideo completion event
Engaged ClickA click where the user stays in-context (no redirect)Tap on playable or video+playable adClickInteraction event
For more information, refer to About Enriched Engagement Types in the AppsFlyer Help Center.

Ad revenue

AppsFlyer supports two methods for passing ad revenue data to Unity. Refer to the following table for the advantages of each option based on your campaign goals and requirements:

AppsFlyer solution

Supported Ad Revenue campaigns

Advantages

AppsFlyer subscription requirement

Notes

Postbacks
  • Day-zero (D0)
  • Day-seven (D7)
Nearly real-time ad revenue dataROI360 AdvancedAd revenue postbacks are required for D0 Ad Revenue campaigns with Unity.
UA signals
  • D7
Accurate and complete ad revenue dataROI360 AdvancedWhile you can run D7 campaigns with AppsFlyer postbacks, the recommended best practice is to send ad revenue data using UA signals. UA signal reports provide more accurate and complete ad revenue values needed for D7 campaigns.

Ad revenue postbacks

You can send ad revenue event postbacks with AppsFlyer's ROI360 product, which includes both UA signals and ad revenue postbacks (impression-level ad revenue postbacks). Ad revenue postbacks can be used to run any Ad Revenue ROAS campaign, and are required for D0 Ad Revenue campaigns.

Custom ad revenue event postbacks

Another way to pass ad revenue data from AppsFlyer is to opt for custom ad revenue events forwarded as AppsFlyer custom postbacks. This is a non-ROI360 option. However, you manage custom ad revenue events yourself, and custom events might be more prone to integration errors or data quality issues because this is a non AppsFlyer-revenue event. This solution can works with any ad revenue return on ad spend (ROAS) campaign goal (D7 or D0). Using custom in-app postbacks might consume your in-app package with AppsFlyer and therefore meet your capping limit. Reach out to your AppsFlyer representative for more information on your plan and package details. For more information, refer to AppsFlyer's documentation on in-app event postback configuration. If you use custom events, ensure that you correctly configure a custom server-to-server integration with AppsFlyer. If your integration isn't set up correctly, AppsFlyer can't send your custom event postback to Unity. Refer to AppsFlyer's Server-to-server events API for mobile documentation for more information.

User Acquisition signals

AppsFlyer also supports passing ad revenue data through User Acquisition (UA) signals. Although the UA Signals report doesn't provide real-time data, the data it provides is more accurate because the value of an impression can change over time. After enabling UA signals in the AppsFlyer dashboard, you can use this feature to forward ad revenue data to Unity for D7 Ad Revenue ROAS campaigns. While you can run D7 campaigns using AppsFlyer postbacks, the recommended best practice is to send ad revenue data using UA signals because the data is more accurate. To enable UA signal reports, refer to AppsFlyer's documentation on how to Share Ad Revenue Data with UA Partners.