Comparing ROI360 ad revenue data with partner data

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. 

Comparing AppsFlyer data with mediation partner data

Integration type Data type What data can be compared to what
S2S API Device-level
  • Compare the total revenue displayed in the AppsFlyer activity dashboard or the total revenue displayed in the single version ad revenue reports via Data Locker to the mediation partner total revenue data.
  • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
  • Don't compare ad revenue event counts (reported in af_ad revenue events) with impression counts.
SDK Device-level
  • Compare the total revenue displayed in the AppsFlyer activity dashboard or the total revenue displayed in the single version ad revenue reports via Data Locker to the mediation partner total revenue data.
  • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
  • Don't compare ad revenue event counts (reported in af_ad revenue events) with impression counts.

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 Impression-level

Compare data in the mediation partner revenue dashboard to:

  • The impression-level revenue report in Data Locker.
    • Compare on the day of the revenue event (Day 0).
    • Relevant only for ROI360 Advanced customers.
  • Device-level ad revenue in the single version ad revenue reports via Data Locker.
    • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
  • Aggregated revenue displayed in the activity dashboard.
    • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
SDK and S2S (freshness to accuracy) Impression-level (via SDK)

Compare data in the mediation partner revenue dashboard to:

  • Revenue displayed in the activity dashboard or the total revenue displayed in the single version ad revenue reports via Data Locker.
    • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
  • The impression-level revenue report in Data Locker.
    • Compare on the day of the revenue event (Day 0).
    • Relevant only for ROI360 Advanced customers.

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)
  • Compare the total revenue displayed in the AppsFlyer activity dashboard or the total revenue displayed in the single version ad revenue report via Data Locker to the mediation partner total revenue data.
  • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
  • Don't compare ad revenue event counts (reported in af_ad revenue events) with impression counts.

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
  • Compare the total revenue displayed in the AppsFlyer activity dashboard or the total revenue displayed in the single version ad revenue reports via Data Locker to the UA partner total revenue data.
  • Wait until the day after the revenue event (Day 0+1) to compare data.
  • Don't compare ad revenue event counts (reported in af_ad revenue events) with impression counts.
SDK Device-level UA signals
  • Compare the total revenue displayed in the AppsFlyer activity dashboard or the total revenue displayed in the single version ad revenue reports via Data Locker to the UA partner total revenue data.
  • Wait until the day after the revenue event (Day 0+1) to compare data.
  • Don't compare ad revenue event counts (reported in af_ad revenue events) with impression counts.
SDK Impression-level Ad revenue postbacks

Compare data in the user acquisition partner revenue dashboard to the:

  • AppsFlyer cohort dashboard/report.
    • Group data by the specific media source (UA partner).
    • Look at total revenue for af_ad_revenue events when filtering by a specific date. This allows comparing the ad revenue generated from installs that occurred on a certain reporting date to the ad revenue reported on postbacks related to those installs.
    • Wait until the day after the revenue event (Day 0+1) to compare data.
  • AppsFlyer activity dashboard/single version ad revenue reports via Data Locker.
    • Group data by the specific media source (UA partner).
    • Look at total revenue for af_ad_revenue events when filtering by a specific date. This allows comparing the ad revenue generated from installs that occurred on a certain reporting date to the ad revenue reported on postbacks related to those installs.
    • Wait until the day after the revenue event (Day 0+1) to compare data.
SDK and S2S (freshness to accuracy) Impression-level (via SDK) Ad revenue postbacks

Compare data in the user acquisition partner revenue dashboard to the:

  • ROI360 ETL Ad revenue SDK impression-level report.
    • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
  • Raw data postbacks in-app event report.
    • Wait until the day after the revenue event (Day 0+1) to compare data, so that both AppsFlyer and the mediation partner have time to process the data.
SDK and S2S (freshness to accuracy) Device-level (via S2S API) UA signals
  • Compare the total revenue displayed in the AppsFlyer activity dashboard or the total revenue displayed in the single version ad revenue reports via Data Locker to the UA partner total revenue data.
  • Wait until the day after the revenue event (Day 0+1) to compare data.
  • Don't compare ad revenue event counts (reported in af_ad revenue events) with impression counts.