Ad Revenue

One of the types of mobile app monetization is in-app ad impressions (Ad Revenue). You can transmit Ad Revenue info to AppMetrica.

After you set up sending Ad Revenue data, you'll be able to:

  • Evaluate your app's overall profitability — from in-app purchases to ad monetization.
  • Identify best-performing ad units, formats, and screens.
  • Build funnels to assess conversion to ad views.
  • Measure the user acquisition metric to identify partners who bring you the most revenue, and evaluate the effectiveness of their traffic.
  • Identify the most profitable user segments and use cohort analysis to track your user revenue over time.
  • Optimize user scenarios and increase ad monetization.

Ad Revenue events aren't included in paid limits. Sending these events doesn't affect your plan cost.

How Ad Revenue is calculated

Data is transmitted from the SDK for each ad impression that generates ad revenue (impression-level revenue data).

All Ad Revenue events in AppMetrica are linked to users, and the Ad Revenue metrics are calculated based on this data:

Metric Description
Ad Revenue events The number of Ad Revenue events.
Ad Revenue Total revenue from ad monetization.
Ad ARPU The ratio of app revenue from ad monetization to the number of app users. Learn more about converting currencies.
eCPM The ratio of the total revenue from ad monetization to the number of Ad Revenue events, multiplied by 1000.
Users with Ad Revenue The number of users with Ad Revenue events.
Ad Revenue events per user The ratio of the number of Ad Revenue events to the number of users.
Sessions with Ad Revenue The number of sessions during which Ad Revenue events occurred.
Ad Revenue events per session The ratio of the number of Ad Revenue events to the total number of sessions.
% of users with Ad Revenue The ratio of the number of users with Ad Revenue events to all users.

Based on the Ad Revenue data, total revenue metrics are calculated:

Metric Description
Total Revenue Total revenue from ad monetization, in-app purchases, and in-app subscriptions. Learn more about converting currencies.
Total ARPU The ratio of the total app revenue from ad monetization, in-app purchases, and subscriptions to the number of app users. Learn more about converting currencies.

Set up sending Ad Revenue events

There are two ways to set up sending Ad Revenue events: using the SDK (the main method) or the Post API.

Set up sending events via the SDK

Step 1. Activate the SDK

Make sure that the AppMetrica SDK is activated in your app:

Step 2. Set up sending Ad Revenue data via the SDK

Select a platform and integration method and set up the appropriate SDK methods.

AppMetrica supports the following methods of integration with ad monetization and mediation services:

Debugging

In AppMetrica, it's not possible to segment events into test and non-test ones. If you use the main API key for debugging the collection of data on advertising monetization, the test events are included in general statistics. For this reason, to debug, use a reporter to send data to an additional API key.

Learn more about reporters

Set up sending events via the Post API

Here are the cases when using the Post API might be a good idea:

  • Import of historical data — upload events for a period when the SDK wasn't yet installed (over the past 14 days maximum).
  • Server validation — transmit data from your backend after additional processing or validation.
  • Data aggregation — group data from multiple sources before sending it to AppMetrica.
  • Offline scenarios — send data collected while a device was offline.
  • Integration with third-party systems — get data from ad networks via their APIs and send it to AppMetrica.
  • Advanced logic — apply business logic on the server before sending analytics.

Take into account the specific features and limitations of the Post API.

Step 1. Get a Post API key

Go to Settings → Main and get the Post API key for request authorization.

Debugging

To make sure that test events aren't included in general statistics while debugging data collection, use different Post API keys for the testing and production environments.

Step 2. Prepare the data to send

Review the documentation on uploading Ad Revenue events via the Post API: Uploading Ad Revenue events.

Collect the necessary parameters for an Ad Revenue event.

Step 3. Send an HTTP request

The Post API supports two data transfer methods:

  • Sending data in the request body (CSV format). Works well for bulk data uploading.

    Use the following endpoint: /logs/v1/import/adrevenue.csv.

    Pass the data in the request body in CSV format.

  • Sending data in request parameters. Works well for standalone events.

    Use the following endpoint: /logs/v1/import/adrevenue.

    Pass the data as URL parameters.

Step 4. Handle the response

The API returns the following response codes:

  • 200: Data uploaded successfully.
  • 403: Authorization error.
  • 400: Missing required parameters.

Check data in reports

After you set up sending Ad Revenue events via the SDK or using the Post API, make sure that the event data flows into the system and the number of events matches the number of ad views.

The Ad Revenue metrics are available in the following reports:

In-app and Ad Revenue
Use the In-app and Ad Revenue report to estimate the app's total revenue, revenue from different types of monetization (ad and in-app monetization), and revenue from different ad networks and different types of ads.
User Acquisition and Remarketing
Use these reports to evaluate the effectiveness of sources for user acquisition and remarketing in terms of ARPU and other advertising and in-app monetization metrics. Please note that the metrics in the report are summed up over the user's entire lifetime.
Cohort analysis
Using the cohort analysis report, you can estimate how much revenue you receive from users over time and what your ARPU is on a certain day.
Funnels
With the Funnels report, you can estimate the share of users who end up viewing ads in general or a certain type of ads (for example, rewarded ads).
Segmentation
To build each report, you can select only those users who, for example, interacted with ads from a certain advertising network or of a certain advertising format.

Currency conversion

You can send Ad Revenue data in different currencies. For a list of all supported currencies, see Supported currencies.

Ad Revenue is converted into any currency the report supports: USD, EUR, or RUB. AppMetrica uses an exchange rate that is provided from more than 15 sources, including the European Central Bank.

AppMetrica converts the currency using the previous day rate. For example, if the Ad Revenue event occurred on day N, the revenue is converted at the exchange rate of day N − 1. Conversion takes place into EUR and RUB against USD.

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 Suggest an improvement for documentation
Previous
Supported currencies
Next
Crashes/Errors reports