User-Level Ad Revenue with ironSource

User-Level Ad Revenue has been unlocked, thanks to a new partnership with mediation platform ironSource. Now marketers have access to granular data, providing them with a greater understanding of in-app ad interactions and the revenue generated from them.

As we’ve explained the benefits already on our blog, we’re going to cover how it works in more detail here, with steps on how to set it up. So, first, let’s take at the fundamentals of User-Level Ad Revenue tracking.

A look under the hood of Adjust’s User-Level Ad Revenue

For User-Level Ad Revenue, we collect data (a device’s generated advertising revenue) from ironSource via an API. After the request is made to ironSource, the aggregated revenue (per app) is represented in the dashboard. For each device, we deliver the following data:

• Daily number of impressions a user has viewed
• The revenue amount generate (and currency)

With User-Level Ad Revenue enabled, clients will see three new deliverables columns in the dashboard: Ad Revenue, Ad Impressions, Ad RPM (Revenue Per Mille). You can look at these to see the aggregated revenue for each network, or check it against any campaign level you wish.

Getting set up with User-Level Ad Revenue

Before we get started, please note that User-Level Ad Revenue is an additional feature available as a separate package. So, if you haven’t already, please reach out to Adjust’s sales team if you’d like to get started.

When Ad Revenue on, you’ll need to link your ironSource account to receive ironSource’s data. To do so, go to Menu > Partner Ad Accounts.

With this, you are able to view and click on ironSource’s menu to configure partner setup. You’ll find it here:

In this menu, you’re able to configure settings, such as:

• Enter one secret key and one refresh key

Once configured, Ad Revenue data appears as three KPIs in Adjust’s Dashboard. These are:

• Ad Impressions
• Ad Revenue
• Ad RPM (Ad Revenue per Mille Impressions)

The KPIs will be displayed in ‘Deliverables’ for all apps with ironSource under your account.

The logic behind these new KPIs is simple: the users you have acquired see ads in your app (Ad Impressions) and in doing so they generate Ad Revenue. Important to note: these KPIs are tied to the attribution source of the user.

If you wish to get device-level revenue data in your BI system, you can use our raw data options. In either scenario, you can simply use the {currency} and {revenue} placeholders. To get raw data of the number of ad impressions that contributed to revenue, you can use the new placeholder {ad_impressions_count}.

Where do clients put these placeholders?

• For real-time callbacks, clients will have a new trigger: Ad Revenue. Our backend will collect this data once per day and send it to the client-specified URL. Clients will use the {currency} and {revenue} placeholders in the ad revenue trigger. This will specifically pass the ad revenue. In addition to revenue, clients need the number of impressions, which they can get by using the {ad_impressions_count} placeholder.
• For CSV options, clients can add the Ad Revenue event to export, and use the same placeholders mentioned above: {revenue}, {currency},

For any more questions about setup, or the feature, please contact our support team.