Ad revenue reporting
With Adjust’s ad revenue reporting, you can see insights on your user lifetime value (LTV) in one place. This helps you understand the performance of your campaigns and optimize them.
Aggregated vs ad impression-level reporting
Aggregated ad revenue data is aggregated at the device level. This means that in your reporting you see the total ad revenue earned from each device. Ad impression-level revenue reporting lets you see the revenue from each ad that is served.
You can view aggregated ad revenue data and cohorts in the Monetization dashboard in Datascape, and access ad revenue data through the Report Service API. Ad impression-level reporting is only available using an SDK or S2S connection.
With API connections, the mediation platform sends us ad revenue requests that include device IDs. However, when the platform sends ad revenue data from a device we haven't recorded an install from, we cannot match that data to a device ID. This can happen if you switch to Adjust from another MMP, without first importing devices. In these cases, ad revenue data is displayed against a link called Unknown Devices.
Available metrics
When you have RevWorks activated on your plan, the following ad revenue metrics are available:
- Ad impressions
- Ad revenue
- Ad revenue per mille impressions (Ad RPM)
You can also see the following Ad Revenue Cohort metrics in your cohorts:
- Ad Revenue
- Ad Revenue Total
- Ad RPM
- All Revenue (in-app + ad revenue)
- All Revenue Total
- All Revenue per User
If you are using the Network revenue API connections solution, then the following metrics are available for you:
- Impressions (AAR)
- Clicks (AAR)
- Requests (AAR)
- Revenue (AAR)
Filter ad revenue data by source
Ad revenue forwarding lets you select which ad revenue source data you want to send to networks. You can choose the ad revenue data sources to share data with networks, while setting up the data sharing options for a network.
Filter your ad revenue by source clearly defines which revenue partner’s data you want in your dataset. You can filter by more than one ad_revenue_source. This also provides greater flexibility in your ad revenue data analysis.
To avoid duplicates and refine your dataset to just what you need, you can use the Ad Revenue Sources filter. This can be applied in Datascape reports, partner data sharing settings, or in your Conversion Hub mapping settings.
The available ad revenue sources to filter by are as follows:
| Ad revenue source | Description |
|---|---|
all | Ad Revenue for all sources, including unknown sources. |
unknown | Ad revenue from unknown sources. |
admob | Ad revenue from AdMob API integration. |
admost | Ad revenue from AdMost API integration. |
admost_sdk | AdMost SDK ad revenue. |
applovin_max | Ad revenue from AppLovin MAX API integration. |
applovin_max_fb_only | AppLovin MAX ad revenue with only Facebook bidding data. |
applovin_max_sdk | AppLovin MAX SDK ad revenue. |
facebook | Facebook ad revenue. Note: Facebook is unavailable as an ad revenue source in the new Adjust suite. |
helium_by_chartboost_sdk | Helium by Chartboost SDK ad revenue. |
ironsource | Ad revenue from Unity LevelPlay (formerly ironSource) API integration. |
ironsource_sdk | Ad revenue from the ironSource SDK integration. |
mopub | Only available for historical MoPub ad revenue data. |
tapjoy | Tapjoy ad revenue. |
topon | TopOn ad revenue |
s2s | Server-to-server reported Ad Revenue. |
Raw data reporting
You can only view aggregated data in reports and dashboards in Datascape. To get ad revenue data sent directly to your servers, use one of the following data export methods:
The following table provides information about the callback frequency for each ad revenue solution:
| Solution | Granularity | Frequency | Callback detail |
|---|---|---|---|
| Mediation platform SDK connections | Impression-level | In real-time | 1 ad impression = 1 callback |
| Mediation platform revenue API connections | Network revenue API connections | Device-level | Once per day | Each callback can have a high ad_impression_count |
| Network revenue S2S connections | Request-level | In real-time | 1 ad impression = 1 callback |
To export user-level ad revenue data, append placeholders to your callback strings or include them in your CSV definition:
| Adjust placeholder | Value delivered |
|---|---|
{revenue_float} | Revenue in whole currency units E.g., 4.99 = €4.99 |
{revenue} | Revenue in cents E.g., 34.5 = €0.345 |
{currency} | Original ISO 4217 currency code E.g., EUR |
{revenue_usd} | Revenue, in US dollars E.g., 4.99 = $4.99 |
{revenue_usd_cents} | Revenue, in US cents E.g., 4.99 = 499 |
{reporting_revenue} | Revenue, as reported in Adjust, in whole currency units E.g., 4.99 |
{reporting_currency} | ISO 4217 currency code E.g., USD |
{ad_impressions_count} | Number of mobile ads served to end users |
{ad_revenue_network} | Ad network that displayed the ad
|
{ad_revenue_unit} | Ad unit that generated the revenue |
{ad_revenue_placement} | User placement as defined on the platform |
{ad_revenue_payload} | Impression-level revenue data as a JSON |
{ad_mediation_platform} | Mediation platform name (monetized by any number of ad networks) from which Adjust fetches ad revenue data. Available values:
|
Ad revenue reporting for users that opt out
A partner's ability to ingest and use ad revenue data may depend on the device IDs that Adjust passes to the partner. Adjust retrieves the device IDs available from the Adjust SDK, ad revenue API integration, or S2S ad revenue request. In order for Adjust to pass ad revenue data with a particular device ID, it has to be present as a parameter in the partner's callback template. Learn more about accepted advertising and device identifiers here.
Ad revenue reporting for users who opt-out of third-party tracking varies by implementation. Expand a section below to view more details.