1. View the mediation (Waterfall) report data
Adjusting Waterfall needs to be done in combination with the actual data performance of each layer of ad sources. The TopOn mediation page directly provides two sets of data: TopOn SDK statistics and network report API data. There is no need to switch to the full report page to view and then switch back to make adjustments, which maximizes your convenience and saves time.
1.1 Report Time Zone
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 aggregated according to the selected time zone (Facebook, Mintegral, Applovin, UnityAds, Tapjoy), 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
1.2 Data update time
The update time of different data metrics will be different, as follows:
(1) eCPM: eCPM is calculated by splitting the API revenue according to the impression ratio. Yesterday's data will be updated at 11:00 and 17:30 every day;
(2) Other TopOn SDK statistics except eCPM: updated every 30 minutes;
(3) Report API data of ad platforms (we will pull network data of the previous day in multiple time periods), please refer to the update instructions of each network in the full report for details
(4) Latency Percentiles data updated the next day:
① UTC+8 China Standard Time: Updated daily at 6:00
② UTC+0 Greenwich Mean Time: Updated daily at 11:00
③ UTC-8 Pacific Standard Time: Updated daily at 20:00
1.3 Report Metrics
Custom metrics support checking the required data dimension content to impression in the aggregate management report.
Description of each indicator of the mediation report:
Report indicator | Description |
---|---|
Priority | The order in which TopOn initiates requests to each ad source. Request in ascending order of Arabic numerals and descending order of priority. Note: When the numbers are the same, the priority is the same. Each time a request is made, the priority of the ad source with the same number will be randomly requested. S2S and C2S icons are Impressioned for bidding ad sources |
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 mediation. >>More |
Status | Turn on or off the ad source. Blue is on, gray is off. |
Operation | Edit or delete the ad source. |
Price | Sorting price. This price is only used for priority sorting when requesting ads: for example, if ABCDE 5 layers of ad sources are added, these 5 layers of ad sources need to be sorted. This sorting will be sorted from high to low according to the filled-in price, and will not affect ad filling. Note: ① If the sorting prices of multiple ad sources are the same, the priority is the same, and each request is made with a random priority; ② It is recommended that the price be as consistent as possible with the actual eCPM (i.e. eCPM API) value of the ad source, which can be used to estimate the real-time revenue and LTV of the day. |
eCPM | eCPM (effective cost per mile) refers to the ad revenue that can be obtained for every thousand impressions; if there are multiple traffic groups, it is the eCPM converted after the revenue and impression of the traffic group are split. Calculation formula: (revenue/impression)×1000. Note: Assuming that there are 3 traffic groups A, B, and C in this placement, the revenue of traffic group A = TopOn statistical impression of traffic group A/Total impression of TopOn statistics× revenue; eCPM of traffic group A = revenue of traffic group A/TopOn statistical impression of traffic group A×1000. |
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; ② Header bidding ad source: real-time ad impression price. >>Header bidding instructions |
Request | The summary row represents the traffic request, that is, the number of requests (Load) initiated by the application (client) to the TopOn SDK; The remaining rows represent the ad source request, that is, the number of requests initiated by TopOn to each ad source according to the waterfall ad source ranking of the aggregate management. Note: One traffic request may correspond to multiple ad source requests. When the application (client) initiates a request to TopOn, TopOn initiates requests to each ad source in sequence according to the waterfall ad source order. 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. |
Fill rate | Summary row indicates the traffic fill rate, that is, the percentage of ads returned successfully after the application (client) initiates a request (Load) to the TopOn SDK; The remaining rows indicate the ad fill rate, that is, the percentage of ads returned successfully after TopOn initiates a request to each ad source. Calculation formula: Traffic fill rate = number of traffic requests returned successfully (number of traffic fills) / traffic requests ×100%; Ad source fill rate = number of ad source requests returned successfully (number of ad fills) / ad source requests ×100%. |
Latency (sec.) | The average time from initiating a request to successfully returning an ad. Note: ① Due to the self-filling behavior of UnityAds, the Latency cannot be accurately counted, and the Latency data of the UnityAds ad source is not Impressioned for the time being. ② Statistical data will be available starting from December 16, 2020. |
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). |
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/impression*100%. |
Impression Rate | The ratio of the number of ad impressions counted by TopOn to the number of successful traffic requests returned (traffic filling number). Calculation formula: impression/traffic filling number*100%. |
Impression Gap | The difference between the number of ad impressions counted by TopOn and the number of ad impressions counted by the network. Calculation formula: (Impression-Impression API)/Impression API. Note: Due to different statistical calibers, there may be some differences between the impression statistics of TopOn and the impression statistics of the network (Impression API). When the Impression gap exceeds 15%, you can contact TopOn's AM to investigate the cause. |
eCPM API | The eCPM (effective cost per mile) that TopOn pulls from the network through the report API. Calculation formula: (Revenue/Impression API) ×1000. Note: If there are multiple groups (traffic groups or AB tests), the eCPM API in each group is the total eCPM of the ad ID pulled from the network, and is not split according to the group. If you want to view the actual eCPM of the group, please check the eCPM indicator, which is the estimated eCPM data after splitting; or use an independent set of ad source IDs for each group to accurately distinguish. |
Revenue API | The actual revenue that TopOn pulls from the network through the report API. Note: If there are multiple groups (traffic groups or AB tests), the revenue in each group is the total revenue of the ad ID pulled from the network, and is not split according to the group. If you want to view the actual revenue of the group, please check the estimated revenue indicator, which is the estimated revenue data after splitting; or use an independent set of ad source IDs for accurate distinction for each group. |
Request API | The number of ad requests that TopOn pulls from the network through the reporting API. Note: Some ad platforms do not provide this data. If there are multiple groups (traffic groups or AB tests), the requests in each group are the total requests for the ad ID pulled from the network, and are not split according to the group. If you want to view the actual requests for the group, please check the Request indicator, which is the request data counted by TopOn; or use an independent set of ad source IDs for each group to accurately distinguish. |
Attempts Rate API | The ad fill rate that TopOn pulls from the network through the report API. Note: Some ad platforms do not provide this data. If there are multiple groups (traffic groups or AB tests), the requests in each group are the total fill rate of the ad ID pulled from the network, and are not split according to the group. If you want to view the actual fill rate of the group, please check the Attempts Rate indicator, which is the fill rate data counted by TopOn; or use an independent set of ad source IDs for each group to accurately distinguish. |
Impression API | The number of ad impressions that TopOn pulls from the network through the report API. Due to different statistical calibers, there may be some differences between the impression statistics of TopOn and the impression statistics of the network (Impression API). Note: If there are multiple groups (traffic groups or AB tests), the requests in each group are the total impression of the ad ID pulled from the network, and are not split according to the group. If you want to view the actual impression of the group, please check the impression indicator, which is the impression data counted by TopOn; or use an independent set of ad source IDs for each group for precise distinction. |
Chicks API | The number of ad clicks that TopOn pulls from the network through the report API. Note: If there are multiple groups (traffic groups or AB tests), the requests in each group are the total clicks of the ad ID pulled from the network, and are not split according to the group. If you want to view the actual clicks of the group, please check the Click indicator, which is the click data counted by TopOn; or use an independent set of ad source IDs for each group to accurately distinguish. |
CTR API | The click-through rate of ads that TopOn pulls from the network through the report API. Calculation formula: Chicks API/Impression API×100%. Note: If there are multiple groups (traffic groups or AB tests), the requests in each group are the total click-through rate of the ad ID pulled from the network, and are not split according to the group. If you want to view the actual click-through rate of the group, please check the CTR indicator, which is the click-through rate data counted by TopOn; or use an independent set of ad source IDs for each group to accurately distinguish. |
1.4 FAQ
(1) What is the function of latency?
Latency refers to the average time from initiating an ad request to the ad returning successfully. It can be used to view the loading time of each ad layer, and optimize the waterfall flow in time by combining the ad layer fill rate and ecpm.
Note:
① Long latency does not necessarily mean that the ad effect is poor, and it needs to be evaluated in combination with other data.
②Generally, video ads with a loading time of less than 10 seconds are not considered slow.