At a glance: Compare AppsFlyer ROI360 ad revenue data with mediation and user acquisition partner data.
Data needs to be received and processed before it becomes available in dashboards and reports. The time it takes for data to become available depends on the ROI360 package you have, as well as partner integration type, data freshness, and report type.
The following sections explain when and how to compare ROI360 ad revenue data in AppsFlyer reports to the data you may see in partner dashboards and reports.
Compare AppsFlyer data with mediation partner data
Integration type | Data type | What data can be compared to what |
---|---|---|
S2S API | Device-level |
|
SDK | Device-level |
|
SDK | Impression-level | Compare data in the mediation partner revenue dashboard to:
|
SDK and S2S (freshness to accuracy) | Impression-level (via SDK) | Compare data in the mediation partner revenue dashboard to:
Note: Since ad revenue data is mutable and it's possible that not all app users updated to the latest version with the ad revenue SDK connector, comparing AppsFlyer data to mediation partner data may result in differences. |
SDK and S2S (freshness to accuracy) | Device-level (via S2S API) |
|
Comparing AppsFlyer data with user acquisition partner data
ROI360 Advanced is required for user acquisition partners to have ad revenue data (via ad revenue postbacks or UA signals) available for comparison.
Integration type | Data type | Partner data source | What data can be compared to what |
---|---|---|---|
S2S API | Device-level | UA signals |
|
SDK | Device-level | UA signals |
|
SDK | Impression-level | Ad revenue postbacks | Compare data in the user acquisition partner revenue dashboard to the:
|
SDK and S2S (freshness to accuracy) | Impression-level (via SDK) | Ad revenue postbacks | Compare data in the user acquisition partner revenue dashboard to the:
|
SDK and S2S (freshness to accuracy) | Device-level (via S2S API) | UA signals |
|