A mobile app can earn revenue from ad impressions (Ad Revenue) and in-app purchases (IAP Revenue).

AppMetrica allows you to collect information about purchases in the app and track statistics in the Revenue report. For more information, see Sending Revenue on Android and on iOS.

  1. Tracking metrics
  2. Currency conversion
  3. Validating purchases
  4. Grouping purchases
  5. Debugging Revenue sending
  6. Paid subscriptions in the App Store

Tracking metrics

You can use the Revenue report data to evaluate:
  • The success of new app features using the ARPU metric.
  • User reaction to price changes using the ARPPU metric.
  • Popular products in the app.
  • Geography of purchases by grouping the city.

Currency conversion

In-app purchases can be made in different currencies. For a list of all supported currencies, see Supported currencies.

AppMetrica converts the purchase price to all report currencies: USD, EUR, 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 purchase was made on day N, the purchase price is converted at the exchange rate of day N − 1. Conversion takes place into EUR and RUB against USD.

Attention. The AppMetrica conversion rate may not coincide with Google Play Console and iTunes Connect rates.

Validating purchases

AppMetrica supports the revenue validation for purchases made through the App Store or Google Play. Purchases on iOS are validated using the iTunes API and on Android through local validation using a public key.

To validate purchases, you need to add keys in the AppMetrica settings and configure sending additional information along with Revenue. For more information, see Sending Revenue on Android and iOS.

If validation is enabled, the report displays purchases that were validated or sent without any information for validation.

Grouping purchases

In-app purchases are grouped by OrderID.

For purchases with validation enabled, the following is used as an identifier:

You can set OrderID manually for purchases without validation. It should be passed in the payload field. For more information, see Sending Revenue on Android and iOS.

If you don't pass OrderID , the AppMetrica SDK generates the ID automatically.

Debugging Revenue sending

AppMetrica doesn't let you create segments for “test” and “not test” Revenue. If you use the main API key for debugging purchases, the test purchases are included in general statistics. Therefore, to debug Revenue sending, use a reporter to send statistics to the additional API key. For more information, see Sending Revenue on Android and iOS.

Paid subscriptions in the App Store

In the AppMetrica SDK, you can track new paid subscriptions in the App Store. They are processed as regular purchases.
Attention. To track subscription renewals, configure revenue sending for each renewal.