S2S impression revenue API
© 2025 AppLovin. All rights reserved.
Impression-level revenue data helps you better understand your users, calculate ROI precisely, and build accurate LTV models. For supported networks, MAX gives you data about each impression: information about revenue, the demand source, and the creative.
You can process this data directly yourself. You can also have the data analyzed by any of AppLovin’s supported analytics providers (you can find a list of these providers in the “MMP integration: MAX to MMP” section of this page).
There are three ways you can get user-level revenue data:
MAX has analytics partners who can help you access your data in a single dashboard. You can work with any of AppLovin’s supported partners to access impression-level ad revenue or aggregated ad revenue data. These supported partners include Adjust, GameAnalytics, AppsFlyer, and Singular. Refer to the documentation pages maintained by those partners for more information about their capabilities.
Contact your account team or the support team to enable this feature.
AppLovin’s servers can send postbacks to an external endpoint whenever they record a MAX impression.
You define which endpoint receives these requests.
The postbacks are in the form of HTTP or HTTPS GET requests.
AppLovin makes these postbacks soon after the impression, but they may be delayed by a few minutes.
You can use an impression timestamp macro to reconcile any delay between the impression and the postback times.
The postback request times-out if five seconds pass without a response from your endpoint. There are no retries for postback requests.
You can incorporate any of the macros in the following table into your postback URL.
The example URL above incorporates the {IDFA}, {USER_ID}, {EVENT_ID}, and {EVENT_TOKEN} macros.
AppLovin’s servers replace these macro names with accurate values when the servers make the request to your endpoint.
| Name | Description |
|---|---|
{AD_UNIT_ID} | MAX ad unit ID (16 hex characters) Example: 9ad0816ac071552a |
{AD_UNIT_NAME} | Ad unit name (URL-encoded) Example: My%20App%20Banners |
{AD_UNIT_TEST_NAME} | Name of the ad unit test, URL-encoded Example: Control |
{ALL_REVENUE} | Estimated revenue, including FB Bidding estimates Examples: 0.0121, 5.74466e-05 |
{CC} | Two-letter country code of the user Example: gb |
{CUSTOM_DATA} | Custom data passed in from the integration (URL-encoded). AppLovin recommends that you keep the size of the string under 8192 characters. You must not include ampersand (&) characters in the custom data if you include this macro.Example: my%20custom%20data |
{DEVICE_TYPE} | User’s device type. Example: Tablet |
{EVENT_ID} | Unique event ID, 40 hex characters |
[COMPONENT: SetPlacement]
[COMPONENT: SetUserId]
[COMPONENT: CustomData]
The following code snippets show you how to add custom String data to postbacks.
This String data replaces the {CUSTOM_DATA} macro in these postbacks.
AppLovin recommends that your string contain fewer than 8192 characters.
The following code snippets show you how you can add a placement name to an ad unit.
The value of the placement name replaces the {PLACEMENT} macro in postback requests:
The following code snippets show how to tag users with your own internal User ID. The maximum size of the User ID string is 8192 characters.
8dc948013d71f04264b8e5c1c61933154b226e08{EVENT_TOKEN} | sha1( «event-ID» + «your-event-key» )Example: e000949f6d851c1f34adae08e6ef1076ba43cf31 |
{EVENT_TOKEN_ALL} | sha256( «All macros alphabetically as-is, not URL-decoded» + «your-event-key» )Note: If EVENT_TOKEN is one of your macros, omit it from the “All macros alphabetically” string.Example: eba615583ed59bc679a495…ff6be5f218702a97a |
{FORMAT} | Ad Unit format Examples: reward, banner, inter |
{IDFA} | iOS IDFA or Google Advertising ID Example: 860635ea-65bc-eaed-d355-1b5283b30b94 |
{IDFV} | Identifier for Vendor Example: 4CD1C3C4-3FD7-00F5-1635-7BC6D9387E60 |
{IP} | User’s IP address. (IPv6 values are URL-encoded) Examples: 162.1.1.1, fe80%3A%3A1ff%3Afe23%3A4567%3A890a%0A |
{NETWORK} | Name of the ad network that served the impression. Names should match the names used in the Management API. Example: APPLOVIN_NETWORK |
{NETWORK_PLACEMENT} | Placement name of the external ad network Example: ca-app-pub-12345678%2F0987654321 |
{PACKAGE_NAME} | App Package Name (Android) or Bundle ID (iOS). URL-encoded. Example: com.test.app |
{PLACEMENT} | Publisher-defined MAX ad placement name (URL-encoded) Example: Launch%20Screen |
{PLATFORM} | Platform Examples: android, ios |
{PRECISION} | Information on how precise the revenue value is. Options are:
Example: exact |
{REVENUE} | Estimated revenue. Set to 0 when FB Bidding.Examples: 0.0121, 5.74466e-05 |
{TS} | Timestamp of impression (integer, seconds since epoch) Example: 1546300800 |
{USER_ID} | Publisher-defined, URL-encoded, user ID; maximum length is 8192 characters Example: 7634657898 |
{WATERFALL_NAME} | The name of the Ad Unit waterfall Example: LAT |
You must set custom data before you load a banner ad or MREC ad. Otherwise that data will not appear in the postbacks associated with the ad.
[COMPONENT: NativeAdView]
[COMPONENT: AdView]
[COMPONENT: AdView]
[COMPONENT: NativeAdView]