Skip to main content

​
Creating a Revenue Report

The User Count in the sub-rows is always smaller or equal to the total User Count. This is because the User Count in the sub-rows is the number of unique users aggregated during the specific time range the sub-row represents, whereas the total User Count in the top rows is the number of unique users aggregated during the entire configured date range. The same logic applies to Paying Users, which is a sub-metric.
Example
Let’s say a user interacted with your app as described below.
  • Day 0: Installed app after viewing an ad. Completed an order in the app and deleted the app afterward.
  • Day 1: Installed the app again after viewing an ad. Completed an order in the app.
In this case, the User Count and Paying Users on Day 0 and Day 1 will show as follows.
  • Total Users, Paying Users: 1
  • User Count and Paying Users on Day 0: 1 each
  • User Count and Paying Users on Day 1: 1 each
The Revenue report and the Actuals report aggregate revenue from different sets of users, so their totals don’t match. The Revenue report aggregates revenue only from users who generated a Start Event, while the Actuals report aggregates revenue from all users. The factors below can widen the difference even further:
  • Difference in how ad performance is measured
  • Event duplication
  • Difference in how negative values are counted
  • Difference in update frequency
Difference in how ad performance is measured
  • The Actuals report counts revenue-related events that occur within the attribution window as ad performance. Events outside the attribution window aren’t included in the metrics.
  • The Revenue report counts each revenue event as ad performance of the most recent Start Event. The attribution window does not apply.
Event duplication
When a user performs multiple Start Events in a day, the Revenue Event may be duplicated in the Revenue report.Let’s say a user interacted with your app as described below.
  1. 2 PM, Day 0: Installed app after viewing a video ad
  2. 7 PM, Day 0: Opened the app via a deep link after viewing a search ad
  3. 11 AM, Day 1: Completed an order in the app
The Revenue report will report as the following:
  • Number of Revenue Events attributed to the video ad on Day 1: 1
  • Number of Revenue Events attributed to the search ad on Day 1: 1
Difference in how negative values are counted
The Revenue report counts negative values as 0. The Actuals report counts negative values as they are.
Difference in update frequency
The Actuals report updates in real time, while the Revenue report updates once an hour.
Yes, all settings are saved when you save the Revenue Report, so you can reuse them whenever you like.Note, however, that for reports saved before June 27, 2024, the ranges for aggregating the Return Events are set to a maximum of Day 30, Week 4, or Month 3, depending on the chosen granularity. The range settings saved in the Revenue Reports can be modified.
The Revenue Report aggregates data collected in the past. If the date range is too recent, some ranges may not be provided because the data hasn’t been collected yet. Refer to the following example.Let’s say the Revenue Report has been configured as follows.
  • Date Range: January 1, 2024 - January 3, 2024
  • Cycle: Daily
  • Revenue Event view ranges: Day 0-30
If today is January 15, 2024, the revenue data will be provided in 15 ranges from Day 0 to Day 14. This is because Airbridge has only data collected until today, which is January 15, and therefore cannot display the retention data from Day 15 to Day 30 even though “Day 0-30” has been chosen as the Revenue Event view ranges.
The Revenue Report aggregates data collected in the past. If the date range is too recent, some ranges may not be provided because the data hasn’t been collected yet. Refer to the following example.Let’s say the Revenue Report has been configured as follows.
  • Date Range: January 1, 2024 - January 3, 2024
  • Cycle: Daily
  • Revenue Event view ranges: Day 0-30
If today is February 1, 2024, the revenue data will be provided in 31 ranges from Day 0 to Day 30. The sub-rows for January 1 and January 2 will show data points in 31 ranges, as January has 31 days.However, the sub-row for January 3 will show data points in 30 ranges from Day 0 to Day 29, and the data point for Day 30 will be missing. This is because Airbridge has data collected until today, which is February 1 and Day 29, considering January 3 as Day 0, and there is simply no data collected yet for February 2, Day 30.