Impression-Level User Revenue API for MMPs
© 2025 AppLovin. All rights reserved.
This API uses a publisher-subscriber architecture.
The MAX SDK broadcasts MAX ad revenue events and MMPs subscribe to the max_revenue_events topic.
AppLovin recommends that you subscribe to that topic immediately after your app launches.
This way, you will not miss events.
Each broadcast event includes the following parameters:
| Name | Description | Example |
|---|---|---|
ad_format | The ad format of the ad. | BANNER, MREC, INTER, REWARDED |
country_code | The revenue’s country code. | US (for the United States) |
id | Unique internal ID for the serve. | 19017d954ffcded6c42772b09ec36699efe0bfc2 |
max_ad_unit_id | The MAX Ad Unit ID. | 65d8d0195e50bda6 |
network_name | Display name of the network that showed the ad. | AppLovin |
revenue | A double that represents the revenue amount. | 0.002067201 |
third_party_ad_placement_id | The ad’s placement ID, if any (bidding may not have one). | inter_regular |
user_segment | The user segment of the user who was shown the ad. | experiment5 |
The following example shows how you subscribe to and process the events that the SDK broadcasts.
MMPs are responsible for setting the values of these parameters. If you do not get data for one or more of these parameters, or if that data is not reliable, work with your MMP to ensure that they support all relevant parameters.
If "revenue" is -1, this indicates an error.
