Ad monetization reporting is available to Analytics Enterprise, Attribution Premium, and Attribution Enterprise customers. For more information, see Singular's customer plans guide or reach out to your Customer Success Manager.
Singular's ad monetization reporting lets you track all your aggregated ad revenue from different networks and mediation platforms in one page.
Use ad mon reports to answer questions such as:
- How much did I earn through each of the ad networks I work with?
- What was my revenue from different apps in different countries and platforms?
- What was my revenue by ad type, ad instance, and/or ad placement?
- What was my fill rate for ad requests?
Ad monetization reporting is available in Singular the web app at Analytics > Ad Monetization, and in the Singular API through the Ad Monetization Reporting API endpoint.
Use the metrics Ad Requests, Filled Ad Requests, and Fill Rate to see if your app is actually displaying all the ads it can display. If your ad requests are not getting filled for certain apps or in certain countries, you may need to start using additional networks.
Singular pulls ad monetization revenue data from the ad networks you work with. This provides you with the most reliable information straight from the source, as opposed to getting revenue stats from mediation platforms.
The data Singular pulls from networks for ad monetization analytics isn't associated with specific users or devices. Therefore, Singular can't analyze it by cohorts to measure ad revenue LTV and ROI.
Singular does offer several ways to add user-level ad revenue to your reporting. To learn more see Setting Up User-Level Revenue Reporting. If you set up user-level ad revenue, you'll see the Ad Revenue metric added to your options in the main Reports page (not in the Ad Monetization page).
User Activity Metrics (DAU and ARPDAU)
The DAU metric stands for Daily Active Users, or how many unique users had at least one session in your app on a particular day. This stat is pulled from your attribution tracker (MMP).
ARPDAU is the average revenue per daily active user (from ad monetization). Singular calculates this metric for you by dividing the total daily revenue from ad monetization by the number of daily active users. Use ARPDAU to check if you are realizing the monetization potential of your app.
Singular pulls DAU data from your attribution tracker, unlike other ad monetization metrics, which are pulled from your ad networks. This is why when you run a report with DAU and/or ARPDAU, you can only break the data down by app, OS, and/or country. Other breakdowns (dimensions) are not available for this data.
If you've selected other dimensions, deselect them to be able to run the DAU/ARPDAU report.
Setting Up Ad Monetization Analytics
To get started, make sure you have added the relevant apps and data connectors:
Go to Settings > Apps and make sure all the apps that you are monetizing are in the list. If you've already set up all your apps for campaign performance reports, you do not need to add anything specifically for ad monetization. But if you are monetizing different apps than the ones you are marketing, you need to add them here.
See Setting Up Your Apps for Analytics for help with the page.
Go to Settings > Data Connectors and add an ad monetization data connector for each ad network through which you are monetizing apps. Ad monetization connectors have "Ad Monetization" in the name. For example, if you are working with Unity, select the data connector "Unity (Ad Monetization)".
See the Data Connectors FAQ for help with the page.
- After setting up the data connector, allow 24 hours before you can see your data live in Singular.
Note on mediation platforms: Even if you are working with a group of ad networks through a mediation platform, you need to set up a separate data connector for each of the networks. Setting up a data connector for the mediation platform will only pull data for the platform's ad network.
For example, if your networks are IronSource and Facebook Audience Network, and they are both managed through IronSource as a mediation platform, you still need to set up two data connectors - for IronSource and for Facebook Audience Network.
You can set up custom dimensions for ad monetization the same as you would for your campaign performance reports. See Setting Up Custom Dimensions for help with the page.
You can build dimensions to fit your company's analytical needs. For example:
- A dimension to track who is the monetization manager per network.
- If you have set up different ad placements to track the first impression vs. the second and the third, you can set up a custom dimension based on ad placement name.
- You can normalize your ad type activity: to measure video ads vs. non-video, set up a custom dimension that maps out the different ad types from different networks.
Note: When you have ad monetization activated, the Custom Dimensions page has a separate tab for ad monetization. Dimensions that you create for campaign data will not be available for ad monetization, and vice versa.
Data connectors for ad monetization have "Ad Monetization" in the name.
For example, if you are running ads on Unity's ad network, you would add the data connector called "Unity Ads" to pull campaign data. If you are monetizing apps through Unity, you would add the data connector called "Unity (Ad Monetization)" to pull ad monetization data.
If you are working with a mediation platform, note that setting up a data connector for your mediation platform will only pull data for the platform's ad network. You need to set up a separate data connector for each of your networks.
For example, if your networks are IronSource and Facebook Audience Network, but it's all managed through IronSource as a mediation platform, you still need to set up two data connectors - for IronSource and for Facebook Audience Network.