Revenue

Note

The report was updated on September 19, 2022. What's new:

  • Added new dimensions.
  • Added new metrics for advertising revenue and event parameters.
  • Changed Validated Revenue tracking: with validation enabled, all In-App Revenue metrics are counted based on validated purchases and purchases passed without parameters for validation. For invalid purchases, Invalid revenue and Users with invalid revenue metrics are counted.

The Revenue report displays the main metrics that are related to your app's revenue from in-app purchases or advertising monetization.

To collect statistics on revenue, configure sending in the app. For more information, see Sending information about a purchase (Android | iOS).

The report will help you:

  • Evaluate the success of new app features using the ARPU metric.
  • Evaluate the user reaction to price changes using the ARPPU metric.
  • Evaluate popular products in the app.
  • Evaluate the geography of purchases using a dimension with data grouped by city.
  • Evaluate the profitability of individual advertising networks and blocks.

Working with the report

General settings

  1. Choose the time period and audience segment. By default, the report shows data for the week grouped by days.

    The time in the report is the beginning of the session on the user's device in the time zone specified in the app settings.

    Note

    To set a custom reporting period, use the element . The selected time interval can be grouped by hours, days, weeks, or months.

  2. You can select specific users for the report using segmentation.

  3. You can set up dimensions and metrics in the report.

Configuring a chart with a choice of metrics

The report contains a visual chart with a choice of metrics. You can select no more than three metrics at a time. The selected metrics must have the same units. If a metric is not available in the list (its name is written in gray), it means that it has a different unit.

Selecting dimensions and metrics

The report contains metrics grouped into dimensions.

To set up dimensions and metrics:

  1. Click the buttons one by one.

  2. In each window, add dimensions and metrics you want to use to build the report.

  3. Configure the order of metrics and dimensions.

    The order of metrics determines the order of columns, the order of dimensions determines the nesting of rows in the table.

Dimensions

Audience
  • Operating system.
  • OS version.
  • Gender. Determined heuristically using Crypta technology. If the prediction accuracy is insufficient , it takes the Undefined value.
  • Age. Determined heuristically using Crypta technology. Possible values: <18 | 18-24 | 25-34 | 35-44 | 45-54 | ≥55. If the prediction accuracy is insufficient, it is Undefined.
Geography
  • Continent.
  • Country.
  • District.
  • Region.
  • City.
  • City size.
Event parameters
  • All parameters, nesting levels 1-5 Outputs all passed event parameters corresponding to the nesting levels.
  • Parameter. Lets you select a specific parameter. You can select a dimension several times with different parameters.
Application
  • Version.
  • Build number.
Total Revenue
  • Revenue Type. Possible values: Purchases: In-app purchases. Ad Revenue: Revenue from advertising monetization.
In-App Revenue
  • Product. In-app product ID.
  • Currency. The currency in which the purchase was made.
  • Order ID.
Ad Revenue
  • Ad Type.
  • Ad Network.
  • Ad Unit id.
  • Ad Unit name.
  • Ad Placement id.
  • Ad Placement name.
  • Ad Precision.

You can drill down the data if you select the following dimensions: region, country, or payload. Use the button to enable the drilldown mode.

Metrics

Total Revenue metrics

  • Total Revenue. Total revenue from advertising monetization, in-app purchases, and in-app subscriptions for the reporting period. Learn more about currency conversions.

  • Total ARPU. The ratio of the total app revenue from advertising monetization, in-app purchases, and subscriptions for the reporting period to the number of app users for the same period. Learn more about currency conversions.

In-App Revenue metrics

  • Purchases. The number of in-app purchases and subscription events with positive revenue.

  • In-App Revenue. Total revenue from in-app purchases and in-app subscriptions. Learn more about currency conversions.

  • Average order. The ratio of revenue from all in-app purchases and subscriptions to their number. Learn more about currency conversions.

  • Paying users. The number of users who made at least one in-app purchase or subscription during the selected period.

  • Purchases per user. The ratio of the number of in-app purchases and subscriptions to the number of paying users for the selected period.

  • In-App ARPU. Average revenue per user. Calculated as the ratio of the total revenue from in-app purchases and subscriptions to the total number of app users for the selected period. Learn more about currency conversions.

  • In-App ARPPU. The ratio of total revenue from in-app purchases to the number of paying users for the selected period. Learn more about currency conversions.

  • % of paying users. The ratio of the number of users making in-app purchases or subscribing to all users for the selected period.

  • Invalid revenue. Total revenue from invalid in-app purchases and subscriptions for the selected period. Invalid in-app purchases aren't counted in other Revenue metrics.

  • Users with invalid revenue. The number of users with invalid in-app purchases and subscriptions over the selected period. Invalid in-app purchases aren't counted in other Revenue metrics.

Ad Revenue metrics

  • Ad Revenue events. The number of events with advertising revenue (Ad Revenue) for the selected period.

  • Ad Revenue. Total revenue from advertising monetization for the selected period.

  • Ad ARPU. The ratio of app revenue from advertising monetization for the selected period to the number of app users for the same period. Learn more about currency conversions.

  • eCPM. The ratio of the total revenue from advertising monetization to the number of events with Ad Revenue for the selected period multiplied by 1000.

  • Users with Ad Revenue. The number of users with advertising revenue (Ad Revenue) events for the selected period.

  • Ad Revenue events per user. The ratio of the number of events with advertising revenue (Ad Revenue) to the number of users for the selected period.

  • Sessions with Ad Revenue. The number of sessions during which events with advertising revenue (Ad Revenue) were committed for the selected period.

  • Ad Revenue events per session. The ratio of the number of events with advertising revenue (Ad Revenue) to the total number of sessions for the selected period.

  • % of users with Ad Revenue. The ratio of the number of users with advertising revenue (Ad Revenue) events to all users for the selected period.

Metrics by event parameters

  • Unique parameter values. The ratio of the number of unique values of the selected parameter of the Revenue event to the number of users with the event. A missing value or parameter in the event during the calculation is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

  • Sum of parameter values. The sum of values of the selected parameter of the Revenue event. A missing value or parameter in the event during the calculation is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

  • Average parameter value. The sum of values of the selected parameter of the Revenue event divided by the number of events. A missing value or parameter is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

  • Median parameter value. The median value of the selected event parameter. A missing value or parameter in the event during the calculation is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

  • Unique parameter values per user. The ratio of the number of unique values of the selected parameter of the Revenue event to the number of users with the event. A missing value or parameter in the event during the calculation is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

  • Sum of parameter values per user. The ratio of the sum of values of the selected parameter of the Revenue event to the number of users with the event. A missing value or parameter in the event during the calculation is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

  • Unique parameter values per session. The ratio of the number of unique values of the selected parameter of the Revenue event to the number of sessions with the event. A missing value or parameter in the event during the calculation is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

  • Sum of parameter values per session. The ratio of the sum of values of the selected parameter of the Revenue event to the number of sessions with events. A missing value or parameter in the event during the calculation is interpreted as 0. Parameters are passed in the payload object of the Revenue event.

The report interface also displays the following:

  • The color key of metrics on the chart. Use it to show or hide a metric on the chart.

    Note

    This item is not displayed when the data is grouped by date.

  • Table structure selector

Data export

You can export data from a report. To do that, click → Export in the upper-right corner. The data is exported based on the selected report settings: segmentation, dimension, and time period.

The dropdown list contains the following elements:

  • Export full report in CSV to export data from the table in CSV format.

  • Chart→ CSV to export data from the chart in CSV format.

  • Chart→ PNG to export chart images in PNG format.

  • Copy table API request — Displays the query text for exporting data from the table using the Reporting API. You can use this query to build your own dashboard or create automated data export scripts.

    Note

    If you are getting the text of the query for the first time, make sure that the browser doesn't block the pop-up authorization window. In the authorization window, allow AppMetrica to access the data.

  • Copy chart API request — Displays the query text for exporting data from the chart using the Reporting API. You can use this query to build your own dashboard or create automated data export scripts.

    Note

    If you are getting the text of the query for the first time, make sure that the browser doesn't block the pop-up authorization window. In the authorization window, allow AppMetrica to access the data.

If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible.

Contact support
Previous
Profile list
Next
Purchase analysis