1. Function Overview
(1) Supports up to 5 independent date comparisons.
(2) Supports checking the required ietrics and viewing the visual charts.
(3) The charts can be exported.
2. Related data description
2.1 Data Filter
Filter Items | Description |
---|---|
Date | The time period when the data was generated. Note: You can select a date of up to 7 days each time. |
App | App created in TopOn. >>More |
Placement | Placements created in TopOn. >>More |
Scenario | Scenario is to create multiple scenarios under one ad position, which can effectively distinguish the impression and click data under different scenarios. It is suitable for products that have multiple scenarios in the app and need to distinguish the impression data. >>More |
Ad Format | Ad Formats corresponding to the 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, TopOn supports the following segment dimensions: area, ad Format, app, placement, date, hour, network type, app version, SDK version, device type, device brand, installation time, channel, sub-channel and custom rules. >>More |
Channel | Developers can pass the channel field to TopOn to distinguish the data from different source channels of users. >>How to pass channel fields through custom rules? |
Network | Access to multiple network SDKs supported by TopOn. >>Networks supported by TopOn |
Ad source | The placement ID parameter of each network corresponds to a unique TopOn ad source, which can be used for waterfall ad layering in aggregation management. >>More |
Area | User's country/area |
SDK version | TopOn's SDK version. >>SDK download address |
App version | Developer-defined app version. |
Platform | Android/IOS |
Device type | iPhone/iPad. |
2.2 Data Ietrics
Data ietrics supported by hourly reports.
Data ietrics | Description |
---|---|
Date | The time period when the data was generated. |
Hours | Hours of the day. |
Estimated 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; ② Head bidding ad source: real-time ad impression price. >>Header bidding instructions |
Estimated eCPM | Estimated eCPM is calculated based on the estimated revenue and the impression of TopOn statistics. The calculation formula is: (estimated revenue/impression 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 successfully returned (number of request filled) / traffic request * 100%. |
Attempts | The number of requests TopOn makes to each network (ad source) according to the waterfall flow ad source ranking managed by aggregation. 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. |
Attempt 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 fills) / ad source request * 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 impressioning" to "the number of callbacks TopOn receives from the network SDK for successful impressioning". Due to different statistical calibers, there may be some differences between the impression counted by TopOn and the impression counted by the network (impression API). |
Impression rate | The ratio of the number of ad exposures counted by TopOn to the number of successful traffic requests returned (request filling number). Calculation formula: impression/traffic filling number*100%. |
eCPM | TopOn calculates eCPM by using the actual revenue obtained from the network through the report API and the impression counted by TopOn. The calculation formula is: (revenue/impression 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. |
Click-through rate | The ratio of ad clicks counted by TopOn to ad exposures counted by TopOn. Calculation formula: click/impression*100%. |
3. FAQ
(1) Hourly report app scenarios
① Observe data changes after strategy/settings are adjusted.
② Observe data performance in different time periods.
③ Real-time estimate of revenue performance for the day to provide support for buying volume.
(2) How the data of hourly reports are counted
① Revenue-related data ietrics, such as estimated revenue and estimated eCPM, are estimated based on the eCPM ranking price filled in by the developer. Therefore, the closer the filled price is to the actual eCPM, the more accurate the estimated data is.
② Except for the data ietrics related to revenue, all data are statistical data of TopOn SDK.