Introduction to passing ad revenue data with Appsflyer
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 |
| Nearly real-time ad revenue data | ROI360 Advanced | Ad revenue postbacks are required for D0 Ad Revenue campaigns with Unity. |
| UA signals | D7 | Accurate and complete ad revenue data | ROI360 Advanced | While you can run D7 campaigns with AppsFlyer postbacks, the recommended best practice is to send ad revenue data using UA signals. Data Locker’s UA signals report provides more accurate and complete ad revenue values needed for D7 campaigns. |
Sending ad revenue event postbacks to Unity
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.
Send 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 (AF S2S). This is a non-ROI360 option and is not a premium product cost. However, custom ad revenue events are controlled by you and might be more prone to integration errors or data quality issues, since this is a non AppsFlyer-revenue event. This solution can be used to run any ad revenue ROAS campaign type (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’ve correctly configured 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.
Sending UA signals to Unity
AppsFlyer also supports passing ad revenue data through UA signals with Data Locker. Ad revenue reports from Data Locker help you utilize UA signals to inform your Ad Revenue campaigns. After enabling UA signals in the AppsFlyer dashboard, you can use this feature to forward ad revenue data to Unity and enable D7 Ad Revenue ROAS campaigns on both Android and iOS. To enable Ad Revenue reports, refer to AppsFlyer’s documentation on how to Set the Ad Revenue report in Data Locker.
Important: Data Locker data is more accurate than streaming data because mediation platforms don’t know the exact revenue of impressions for eCPM floors at impression time. Only ad networks have the data of the exact revenue of impressions for eCPM floors at impression time, which is generally available with a delay. Real-time data is an estimate, but Data Locker allows for enough time to report on the accurate and complete data from the network.