Onboarding Guide for Ad Revenue Attribution

Learn about the different implementations of Ad Revenue Attribution, which one is right for you, and how to set it up.

Prerequisites You've completed basic onboarding and use Singular's reports.

Understand Singular's Ad Revenue Attribution

1

Understand Ad Revenue Attribution

With complete visibility into accurate ROI, channel and campaign performance can look completely different. You need to factor ad revenue into the ROI calculation.

Without ad revenue, UA managers are not getting the full picture. For instance, they may be missing the “ad whales” that are highly engaged with in-app ads and subsequently drive higher ad revenues.

There are three ways to set up Ad Revenue attribution that balance additional integration against the amount of data available.

Note: This feature is different from Ad Monetization Analytics, which is where you get ad revenue as reported directly from your ad monetization sources.

2

The three ways to set up Ad Revenue Attribution

You can get your ad revenue attribution data:

  1. Through SDK events from your mediation platforms.
  2. Through User-level API integrations of your mediation platforms.
  3. Through Singular’s estimation

Important: Ad Revenue Attribution is not enabled by default. No matter which method you use, you will need to contact us to enable the feature for your account. The instructions below include this reminder.

3

Which metrics will you need in your reports?

Singular offers a number of different metrics to help you understand your data. Learn the difference between them:

  • Revenue: Your revenue from in-app purchases.
  • Ad Revenue: Your revenue from ad monetization.
  • Total Revenue: The sum of the two revenue values.
  • ROI: Your revenue from your in-app purchases divided by cost.
  • Ad ROI: Your revenue from ad monetization divided by cost.
  • Total ROI: Your total revenue divided by cost.
  • Average Revenue Per User (ARPU): Your revenue from in-app purchases divided by the number of users. 
  • Ad ARPU: Your revenue from ad monetization divided by the number of users.
  • Total ARPU: Your total revenue divided by the number of users.
  • Average Revenue Per Daily Active Users (ARPDAU): Your revenue from in-app purchases divided by the number of daily active users.
  • Ad ARPDAU: Your revenue from ad monetization divided by the number of daily active users.
  • Total ARPDAU: Your total revenue divided by the number of daily active users.

Note: These metrics are available in the Singular App. Ratio metrics such as ROI, ARPU, and ARPDAU are not available via the API. This is because your ratio, say ROI, will not be accurate if you pull the ROI metric and add the individual values together. To get accurate values for your ratio metrics, you must aggregate non-ratio metrics such as revenue and use them to calculate your ratios.

Set up using SDK Events

1

Setup instructions

Singular can receive SDK events from mediators like IronSource, AppLovin MAX, MoPub, and AdMob.

  1. Contact Singular to enable ad revenue attribution for your account.
  2. Update to the latest version of the Singular SDK.
  3. Add the appropriate code snippet to your Singular SDK integration, based on the mediation platform you use for your ad revenue data.
  • Use the “Adding Ad Revenue Attribution Support” section in our Android, iOS, or Unity guides.
  • Before going live, validate your setup in the SDK Console.
  • In Settings > SDK Console, run an SDK audit or manually test your setup. Step-by-step guide.
  • Confirm the “ad_currency” field matches your preferred currency.
  • Confirm the “is_revenue_event” is set to “true”.
  • Confirm the value of the event is correct.
  • After you have tested and validated your setup, you can take the app live. You can see aggregated data in Analytics > Reports and user-level data in Attribution > Export Logs.

Important:

  • If you use AdMob, you will also need to contact them to enable this feature.
  • If you use IronSource, you will need to enable the ARM SDK Postbacks Flag in IronSource.
2

What to expect from your reports

  • The data is updated hourly.
  • In Analytics > Reports, you will see the ad revenue data combined with UA cost and attribution data.
  • Reports will only show you Android and opted-in IDFA users. Revenue for iOS users who have not opted in to share their IDFA is treated as organic.
  • You can set up SKAdNetwork revenue models with ad revenue data.
  • In Attribution > Export Logs, the revenue event is called "_Admon_user_level_revenue_". The "_revenue_" event includes both ad monetization revenue and in-app purchases.
  • You can set up BI postbacks or user-level data destinations. You can also postback ad revenue events to UA sources.

Set up using User-level APIs

1

Setup instructions

Singular is integrated with AppLovin MAX and IronSource through their APIs. This method does not require you to update your Singular SDK integration.

  1. Contact your Singular representative to enable ad revenue attribution for your account.
  2. In Singular, go to Settings > Data Connectors and add the “AppLovin MAX User Level” or “IronSource User Level Publisher” connector.
    • Note: If you use both, inform Singular about which mediator you use for which app.
  3. After Singular pulls all the data successfully, view aggregated data in Analytics > Reports.
2

What to expect from your reports

  • Data is available for up to 2 days prior.
  • You cannot set up SKAdNetwork revenue models.
  • In Analytics > Reports, you will see the ad revenue data combined with UA cost and attribution data. You can break down ad ROI to any granularity.
  • Reports will only show you Android and opted-in IDFA users. Revenue for iOS users who have not opted in to share their IDFA is treated as organic.
  • You can receive user-level data for this integration type via data destinations.
  • If you use multiple mediators i.e. multiple user-level data connectors, you can do a breakdown of each mediation source.
    • Singular App: Run a report using the Ad Revenue metric and hover over a cell to see the source breakdown.
    • API: Run a query with the "admon_data_source" dimension. The data will not be combined and revenue will appear as a separate row from tracker/network data.

Set up using Estimation 

1

Setup instructions

You can use your existing Singular SDK integration to calculate the average revenue per event for your defined user events.

  1. Contact us to enable ad revenue attribution for your account.
  2. Decide which event to use to calculate the ad revenue per user. We recommend an event that is related to when an ad was served i.e. "ad_impression". However, you can always default to "session" if you don't have any custom ad impression event.
  3. In Singular, go to Settings > Data Connectors and add the relevant AdMon data connectors for all your ad networks. These will have “(Ad Monetization)” in their name, e.g. “AdWords (Ad Monetization)”.
  4. After Singular pulls all the data successfully, view the data in Analytics > Reports by selecting your relevant metrics.
2

What to expect from your reports

  • Data is available for up to 2 days prior.
  • You cannot set up SKAdNetwork revenue models.
  • You cannot get user-level data through this method.
  • In Analytics > Reports, you will see the ad revenue data combined with UA cost and attribution data. You can break down ad ROI to any granularity.
  • You can get a breakdown of your data via the API.

 

Was this article helpful?