1. Functional Overview
Data reports provide a rich data dimension of ad monetization to fully understand the monetization effect of your ad business. Data reports include full reports, cohorts report, user engagement, hourly reports, cross-promotion reports, ROI reports and other multi-dimensional visualization content.
Notes
To prevent TopOn server failures caused by crawlers grabbing data, developers are requested not to use crawlers to grab TopOn data reports. If you have the above behavior, please stop immediately, otherwise TopOn will suspend your service! Please comply with this, partners.
2. Operation Guide
Data View By: Date, App, Placement, Segment, Channel, Area, Network, Ad Source, Scenario, Ad Format, SDK Version, App Version
Data Indicators:DAU, ARPDAU, New Users, New Users/DAU, Day2 Retention, DEU, Engaged Rate, Impression/DAU, Impression/DEU, Bid Request, Bid Request Rate, Estimate Revenue, Estimate eCPM, Request, Request Fill Rate, Impression, Impression Rate, eCPM, Click, CTR, Attempts, Attempts Fill Rate, Impression Gap, Click Gap, Revenue, Impression API,eCPM API, Clicks API, CTR API, Attempts API, Attempts Fill Rate API, Cross Promotion Statistics.
3.
The data report supports modifying the report time zone. Currently, it supports UTC+8 China Standard Time, UTC+0 Greenwich Standard Time, and UTC-8 Pacific Standard Time. The default is UTC+8 time. TopOn SDK statistics and the following network data have been summarized according to the selected time zone (Mintegral, Applovin, UnityAds, Tapjoy, Bigo), and the remaining network data are based on the time zone returned by the API.
Report time zone modification path: TopOn Developer Backstage→[My Account]→[Account information]→[base information]→Report Time Zone
4. Data Update Time
The update time of different date mertrics will vary, as follows:
(1) DAU, New Users and Retention Rate: updated every 2 hours
(2) Other TopOn SDK statistics except DAU, New Users, Retention Rate: updated every 5 minutes;
(3) Network report API data (we will pull the network data of the previous day in 5 time periods): 3:30, 10:50, 14:30, 16:30, 21:00
5. Related data description
5.1 Data Filters
Custom filter items support checking the required filter item content to display in the full report.
Filter Items | Description |
---|---|
App | App created in TopOn. >>More |
Placement | Placement created in TopOn. >>More |
Ad Format | Ad Formats for Ad Placements Created in TopOn: Rewarded Video, Interstitial, Native, Splash, Banner |
Segment | TopOn provides multiple dimensions to group users. Different traffic groups can be configured with different Waterfalls to achieve refined traffic monetization. Currently, the traffic grouping dimensions supported by TopOn are as follows: Area, Ad format, App, Placement, Day, Hour, Network Type, App Version, SDK version, OS Version , Device ID ,Device Type, Device Brand, Installation Time, Channel, Sub-channel and Custom. >>More |
Channel | Developers can pass the channel field to TopOn to distinguish user data from different source channels. >>How to pass channel fields through custom rules? |
Network | Access to multiple network SDKs supported by TopOn. >>Networks supported by TopOn |
Ad source | The ad slot ID parameter of each network corresponds to a unique TopOn ad source, which can be used for waterfall ad layering in mediation. >>More |
Area | User's country/region |
SDK version | TopOn's SDK version. >>SDK download address |
App version | Developer customized app version. |
Platform | Android/IOS |
Usage type | Regular ad source/Header Bidding ad source. >>Header Bidding Instructions |
Scenario | Scenario is to create multiple scenario s under one ad position, which can effectively distinguish the display and click data under different scenarios. It is suitable for products that have multiple scenarios in the app and need to distinguish the display data. >>More |
5.2 Data Metrics
Custom indicators support checking the required data dimension content to display in the full report.
Date mertrics | Description |
---|---|
Date | The time period when the data was generated. |
DAU | Daily Active User, that is, the number of device users who initialized TopOn SDK. Note: According to the GDPR agreement, the EU region needs user consent before statistics are collected. >>What is GDPR? |
ARPDAU | Average Revenue Per User (ARPU). Calculation formula: Revenue/DAU |
New Users | Number of device users who initialized TopOn SDK for the first time in the past 60 days. |
New Users/DAU | Ratio of device users who initialized TopOn SDK for the first time in the past 60 days to daily active users. Calculation formula: new users/DAU |
Day2 Retention | Ratio of users who still generate network requests 2 days after acquiring new users. |
DEU | The number of device users who have displayed (exposed) ads every day. Note: DEU supports data in the app and ad slot dimensions. |
Engaged Rate | The ratio of device users who have displayed (exposed) ads every day to daily active users. Calculation formula: DEU/DAU*100% |
Impression/DAU | The average number of impressions per daily active user. |
Impression/DEU | The average number of impressions per device user who has displayed (exposed) an ad. |
Bid Request | Number of inquiries initiated by Header Bidding ad sources. >>Header Bidding Description |
Bid Request Rate | Header Bidding ad source inquiry response rate. Calculation formula: Number of corresponding inquiries/number of inquiries*100%. >>Header bidding description |
Bid Request eCPM | The average eCPM returned by the network when the header bidding ad source responds to the inquiry. >>Header bidding instructions |
Estimate Revenue | Estimated revenue based on the number of impressions and eCPM prices counted by TopOn SDK. Calculation formula: ① Conventional ad source: manually filled in eCPM price * TopOn statistics / 1000; ② Header bidding ad source: real-time ad display price. >>Header bidding instructions |
Est. ARPDAU | Calculation formula: estimated revenue/DAU |
Estimate eCPM | Calculate the estimated eCPM based on the estimated revenue and the display of TopOn statistics. The calculation formula is: (estimated revenue/display of TopOn statistics)*1000. Note: 1. Estimated eCPM is provided on the same day; 2. Conventional ad sources are calculated based on manually entered eCPM prices, and bidding ad sources are calculated based on real-time bidding prices. |
Request | Number of requests (Load) initiated by the app (client) to TopOn SDK. |
Request Fill Rate | The percentage of successful ads returned after the app (client) initiates a request (Load) to TopOn SDK. Calculation formula: Number of traffic requests returned successfully (number of traffic fills)/traffic requests*100%. |
Impression | From 0:00 on March 7, 2023 (UTC+8), the statistical caliber will be adjusted from "the number of times TopOn calls the network SDK to start displaying" to "the number of callbacks TopOn receives from the network SDK for successful displaying". Due to different statistical calibers, there may be some differences between the display counted by TopOn and the display counted by the network (display API). |
Impression Rate | The ratio of the number of ad exposures counted by TopOn to the number of successful traffic requests returned (traffic filling number). Calculation formula: display/traffic filling number*100%. |
eCPM | TopOn calculates eCPM by using the actual revenue obtained from the network through the report API and the display counted by TopOn. The calculation formula is: (revenue/display counted by TopOn)*1000. Note: eCPM is provided with a delay of 1 day. |
Click | Number of ad clicks counted by TopOn. Some platforms do not provide click callbacks (such as Admob's rewarded videos), resulting in TopOn being unable to count user clicks. |
CTR | The ratio of ad clicks counted by TopOn to ad exposures counted by TopOn. Calculation formula: click/display*100%. |
Attempts | The number of requests TopOn makes to each network (ad source) according to the waterfall flow ad source ranking of aggregate management. Note: One traffic request may correspond to multiple ad source requests. When the app (client) makes a request to TopOn, TopOn makes requests to each ad source in turn according to the waterfall flow ad source ranking. When the high-priority ad source is not filled or no ad is returned within the short timeout (8s), it will request the lower-priority ad source. At this time, one traffic request will correspond to multiple ad source requests. |
Attempts Fill Rate, | The percentage of successful ads returned after TopOn initiates a request to each network (ad source). Calculation formula: number of successful ad source request returns (number of ad source fills)/ad source request*100%. |
Impression Gap | The difference between the number of ad exposures counted by TopOn and the number of ad exposures counted by the network. Calculation formula: (Impression - Impression API)/Impression API. Note: Due to different statistical calibers, there may be some differences between the display statistics of TopOn and the display statistics of the network (display API). When the display gap exceeds 15%, you can contact TopOn's AM to investigate the cause. |
Click Gap | The difference between the number of ad clicks counted by TopOn and the number of ad clicks counted by the network. Calculation formula: (click-click API)/click API. |
isReady | The number of times the TopOn isReady interface is called. Note: The isAdReady interface determines whether there are currently ads that can be displayed. (Android native and banner ads do not support isReady judgment; dual-end TopOn 5.7.6 version starts to support isReady judgment of open screen) |
isReady rate | The ratio of the number of times the TopOn isReady interface returns true to the number of times the TopOn isReady interface is called. Calculation formula: the number of times the TopOn isReady interface returns true/the number of times the TopOn isReady interface is called*100%. |
Reach Scenario | The number of times a user reaches the scenario . App needs to call the entryAdScenario method to count. |
Scenario Ready Rate | The percentage of ads that are ready when users reach the scenario |
API data | The following indicators are API data, i.e.: data that TopOn pulls from the network through the report API |
Revenue | The actual revenue that TopOn obtains from the network through the reporting API. |
Impression API | The number of ad impressions that TopOn obtains from the network through the reporting API. Due to different statistical calibers, there may be some differences between the impressions counted by TopOn and the impressions counted by the network (display API). |
eCPM API | TopOn calculates the eCPM API using the actual revenue and display API pulled from the network through the reporting API. The calculation formula is: (revenue/display API)*1000. Note: eCPM API is provided with a delay of 1 day. |
Click API | The number of ad clicks pulled from the network by TopOn through the reporting API. |
CTR API | The click-through rate of ads that TopOn pulls from the network through the reporting API. Calculation formula: Click API/Impression API*100%. |
Attempts API | The number of ad source requests that TopOn pulls from the network through the reporting API. Note: Some networks do not provide this data. |
Attempts Fill Rate API | The fill rate of ads that TopOn pulls from the network through the reporting API. Note: Some networks do not provide this data. |
Cross Promotion Statistics | Estimated revenue and ad statistics for cross-promotion. >>What is cross-promotion? |
6. Offline Report Center
Export report supports exporting up to 5,000 rows of data. If you need to export more than 5,000 rows of data, please use Export Offline Report (offline report supports exporting up to 50,000 rows of data):
(1) Search data according to your needs
(2) Click [Export Report] to submit the task of generating offline report (it is recommended to set different report names for different query results)
(3) Jump to [Report] > [Offline Report] to view the generation results of offline report (offline report generation time is generally 5 to 15 minutes)
7. FAQ
(1) What is the difference between request and ad request?
After the app initiates a request to TopOn, TopOn initiates ad request to each network in sequence according to the waterfall flow.
(2) How does TopOn determine which country the user is from?
When a user initiates an ad request from the client, TopOn will make a judgment based on the user's IP information.