Report
1. Data Explanation
1.1 Data Types and Definitions
| Data Types | Definition Explanation |
|---|---|
| ToBid Statistical Metrics | Data collected and reported through the ToBid SDK can be presented in real-time through real-time data computation. |
| API Metrics | Data returned to ToBid by each AD Network through the Report API |
| Data GAP | ( ToBid Statistical Data - API Data) / API Data Note: The reasonable indicator of data GAP rate is within 5%. If it exceeds 10%, please contact business or technical support colleagues for timely verification. |
| User Behavior Metrics | User level data counted by ToBid SDK |
1.2 API data metrics supported by each AD Network
Some AD Networks do not currently support API postback for all data metrics. The following table shows the postback metrics currently supported by various AD Networks
| AD Network | Revenue | Ad Request | Ad Response | Ad Fill Rate | Impression | eCPM | Click | CTR |
|---|---|---|---|---|---|---|---|---|
| Sigmob | - | - | - | - | √ | √ | √ | √ |
| AdMob | √ | √ | √ | √ | √ | √ | √ | √ |
| AppLovin | √ | - | - | - | √ | √ | √ | √ |
| Baidu | √ | √ | √ | √ | √ | √ | √ | √ |
| CSJ | √ | √ | √ | √ | √ | √ | √ | √ |
| ironSource | √ | √ | √ | √ | √ | √ | √ | √ |
| Kusishou | √ | - | - | - | √ | √ | √ | √ |
| Mintegral | √ | √ | √ | √ | √ | √ | √ | √ |
| Tencent | √ | √ | √ | √ | √ | √ | √ | √ |
| Unity Ads | √ | - | - | - | √ | √ | √ | √ |
| Vungle | √ | - | √ | √ | √ | √ | √ | √ |
2. Overview
Click "Reports" - "Overview" to view the report API postback data through the third-party AD Network.
| Table Capability Description | Description |
|---|---|
| Disclosure of Data Types | API metrics only |
| Data Update Time | T+1，Pull data from various AD Networks at multiple times per day for updates to ensure data integrity |
| Supported Data Dimensions | Time, OS, APP, AD Type, ToBid Placement, AD Network |
| Disclosed Data Metrics | Revenue API、Impression API、Click API、CTR API、eCPM API |
3. Daily Report
Click on "Reports" - "Daily Report" to view the data of the monetization application under the account.
| Table Capability Description | Description |
|---|---|
| Disclosure of Data Types | ToBid Statistical Metrics + API Metrics |
| Data Update Time | Updated every hour |
| Supported Data Dimensions | Time, OS, APP, AD Type, ToBid Placement, AD Network, Segment, IDFA , ad source type, ad source, ToBid SDK version, APP version |
| Disclosed Data Metrics | - ToBid Statistical Metrics：Est. revenue、Request、Response、Fill Rate、Impression、Impression Rate、Ad Request、Ad Response、Ad Fill Rate、Ad Impression Rate、Click、CTR、eCPM - API Metrics：Revenue API、Ad Request API、Ad Response API、Ad Fill Rate API、Impression API、Click API、CTR API、eCPM API |
3.1 Metrics Description
| Property | Property Value | Description |
|---|---|---|
| ToBid Statistical Metrics | Est. Revenue | Estimated revenue for non-bidding ad sources = SUM(expected eCPM set in the waterfall * displays counted by ToBid / 1000). Estimated revenue for in-app bidding ad sources = SUM(real-time price of each display) |
| Request | The number of requests sent from the app to ToBid. One traffic request may trigger multiple ad requests. | |
| Response | The number of successful responses after the app sends requests to ToBid | |
| Fill Rate | The proportion of successful responses to requests sent from the app to ToBid, calculated as: Response / Request | |
| Impression | The number of ad impressions counted by ToBid based on ad display callbacks. Due to differences in counting criteria and network packet loss, the number of impressions counted by ToBid may differ from those counted by ad networks. | |
| Impression Rate | Calculated as: Impressions / Responses | |
| Ad Request | For ordinary ad sources, indicates Ad Request, which is the number of requests sent from ToBid to the ad network. One traffic request may trigger multiple ad requests; for in-app bidding ad sources, indicates Bid Request, which is the number of bids sent from in-app bidding ad sources to third-party ad networks. | |
| Ad Response | For ordinary ad sources, indicates Ad Response, which is the number of successful responses after ToBid sends requests to the ad network; for in-app bidding ad sources, indicates Bid Response, which is the number of successful bid responses from third-party ad networks. | |
| Ad Fill Rate | For ordinary ad sources, indicates Ad Fill Rate, which is the proportion of successful responses to requests sent from ToBid to the ad network; for in-app bidding ad sources, indicates Bid Response Rate, which is the Bid Response / Bid Request | |
| Ad Impression Rate | Calculated as: Impressions / Ad Response | |
| Click | The number of ad clicks counted by ToBid based on ad click callbacks. Due to some ad networks not providing click callbacks, the number of clicks counted by ToBid may differ from those counted by ad networks. | |
| CTR | Calculated as: Click / Impression | |
| eCPM | Estimated revenue per thousand impressions within the selected time range. Calculated as the weighted average eCPM for the selected time range. For example: eCPM for the past 7 days = (Income_Day1 + Income_Day2 + ... + Income_Day7) / (Impressions_Day1 + Impressions_Day2 + ... + Impressions_Day7) * 1000 | |
| API Metrics | Revenue API | Revenue pulled via Reporting API, converted to account currency using real-time exchange rates |
| Ad Request API | The number of ad requests pulled via Reporting API. Some ad networks may not return this field. | |
| Ad Response API | The number of ad responses pulled via Reporting API. Some ad networks may not return this field. | |
| Ad Fill Rate API | Calculated as: Ad Response API / Ad Request API | |
| Impression API | The number of ad impressions pulled via Reporting API | |
| Click API | The number of ad clicks pulled via Reporting API. Some ad networks may not return this field. | |
| CTR API | Calculated as: Click API / Impression API | |
| eCPM API | Calculated as: Revenue API / Impression API * 1000 | |
| GAP | Ad Request GAP Rate | The difference between the number of ad requests counted by ToBid and those counted by ad networks, calculated as: (Ad Request - Ad Request API) / Ad Request API |
| Ad Response GAP Rate | The difference between the number of ad responses counted by ToBid and those counted by ad networks, calculated as: (Ad Response - Ad Response API) / Ad Response API | |
| Impression GAP Rate | The difference between the number of ad impressions counted by ToBid and those counted by ad networks, calculated as: (Impression - Impression API) / Impression API | |
| Click GAP Rate | The difference between the number of ad clicks counted by ToBid and those counted by ad networks, calculated as: (Click - Click API) / Click API | |
| eCPM GAP Rate | The difference between eCPM calculated by ToBid and eCPM calculated based on data returned by ad networks, calculated as: (eCPM - eCPM API) / eCPM API |
3.2 Points to Note
- The finest granularity of traffic level data metrics is traffic grouping. Therefore, when selecting [Ad Network/Ad Source Type/Ad Source] dimensions, the data report will automatically hide relevant indicators of traffic level data.
- When selecting [ToBid SDK Version/App Version] dimensions, the data report will automatically hide API-related data indicators and GAP rate data indicators.
- When selecting any combination of [Ad Network/Ad Source Type/Ad Source] and [ToBid SDK Version/App Version], the system will automatically hide all data related to traffic level data, API-related data, and GAP rate.
- Traffic level data metrics include: traffic requests, traffic returns, traffic fill rates, and traffic display rates.
4. Hourly Report
Click "Reports" - "Hourly Report" to view the hourly data
| Table Capability Description | Description |
|---|---|
| Disclosure of Data Types | ToBid Statistical Metrics |
| Data Update Time | Updated every 2-3 minutes |
| Supported Data Dimensions | Time, OS, APP, AD Type, ToBid Placement, AD Network, Segment, IDFA , ad source type, ad source, ToBid SDK version, APP version |
| Disclosed Data Metrics | ToBid Statistical Metrics：Est. revenue、Request、Response、Fill Rate、Impression、Impression Rate、Ad Request、Ad Response、Ad Fill Rate、Ad Impression Rate、Click、CTR、eCPM |
4.1 Points to Note:
- The finest granularity of traffic level data indicators is traffic grouping. Therefore, when selecting any dimension in [Ad Network/Ad Source Type/Ad Source], the data report will automatically hide the relevant indicators of traffic level data.
- Hourly reports can only query data within the last 90 days, with a time span of 3 days.
5. In-App Bidding Report
点击【漏斗分析】-【应用内竞价分析】竞价漏斗分析页面，可查看广告在头部竞价广告请求链路产生的数据。
| Table Capability Description | Description |
|---|---|
| Disclosure of Data Types | ToBid Statistical Metrics + API Metrics |
| Data Update Time | Updated every hour |
| Supported Data Dimensions | Time, OS, APP, AD Type, ToBid Placement, AD Network, Segment, IDFA , ad source type, ad source, ToBid SDK version, APP version |
| Disclosed Data Metrics | - ToBid Statistical Metrics：Est. revenue、Bid Request、Bid Response、Bid Win、Bid Response Rate、Bid Win Rate 、Ad Material Request、Ad Material Response、 Ad Material Fill Rate、Bid Latency(sec.)、Average Bid Response Price 、Ad Material Impression、Ad Material Click、Ad Material CTR、eCPM |
5.1 Special Metrics Description
| Metrics | Description |
|---|---|
| Bid Request | The number of bid requests sent from in-app bidding ad sources to third-party ad networks |
| Bid Response | The number of successful bid responses from third-party ad networks for in-app bidding ad sources |
| Bid Win | The number of winning bids in the overall waterfall ranking from the bid responses of in-app bidding ad sources |
| Bid Response Rate | Calculation formula: Bid Response / Bid Request |
| Bid Win Rate | Calculation formula: Bid Win / Bid response |
| Ad Material Request | The ad request sent to the third-party ad network to load ad materials after winning the bid in in-app bidding |
| Ad Material Response | The number of successful responses to the material request sent to the third-party ad network after winning the bid in in-app bidding |
| Ad Material Fill Rate | Calculation formula: Ad Material Response / Ad Material Request |
| Bid Latency(sec.) | The average response time from initiating a bid request to receiving a bid response in in-app bidding |
| Average Bid Response Price | The average bid price in the bid responses of in-app bidding |
6. User Behavior
Click "Reports" - "User Behavior" to view the user behavior data
| Table Capability Description | Description |
|---|---|
| Disclosure of Data Types | ToBid Statistical Metrics + API Metrics |
| Data Update Time | Updated every hour |
| Supported Data Dimensions | Time, OS, APP, ToBid Placement,Segment, IDFA , ToBid SDK version, APP version |
| Disclosed Data Metrics | - ToBid Statistical Metrics：DAU、DEU、Engaged Rate、Impression、Imp./DAU、Est. Revenue、Imp./DEU、ARPDAU、eCPM - API Metrics：Impression API、Imp.API/DAU、Imp.API/DEU、Revenue API、ARPDAU API、eCPM API |
6.1 Points to Note
- When disclosing DAU metrics at the summary row, the calculation method for the metric is the multi-day average.
- When selecting dimensions such as "Segment" ,"Ad Placement Type" ,"ToBid Placement" etc., the DAU at the summary row holds no practical significance, and the system will automatically hide the summary row data.
7. Waterfall
Clicking on "Mediation Management" - "Waterfall Management" allows access to the waterfall management page. Here, you can set traffic grouping and advertising source for the selected APP-aggregated ad placement, and view detailed data under the waterfall. 
| Table Capability Description | Description |
|---|---|
| Disclosure of Data Types | ToBid Statistical Metrics + API Metrics |
| Data Update Time | Updated every hour |
| Supported Data Dimensions | APP , ToBid Placement ,Segment |
7.1 Special Metrics Description
| Metrics | Description |
|---|---|
| Request | The summary row indicates Request, which is the number of requests sent from the app to ToBid; for other rows, non-bidding ad sources indicate Ad Request, which is the number of requests sent from ToBid to the ad network; in-app bidding ad sources indicate Bid Request, which is the number of bids sent from in-app bidding ad sources to third-party ad networks. |
| Response | The summary row indicates Response, which is the number of successful responses after the app sends requests to ToBid; for other rows, non-bidding ad sources indicate Ad Response, which is the number of successful responses after ToBid sends requests to the ad network; in-app bidding ad sources indicate Bid Response, which is the number of successful bid responses from third-party ad networks. |
| Fill Rate | The summary row indicates Fill Rate, which is the proportion of successful responses to requests sent from the app to ToBid; for other rows, non-bidding ad sources indicate Ad Fill Rate, which is the proportion of successful responses to requests sent from ToBid to the ad network; in-app bidding ad sources indicate Bid Response Rate, which is the Bid Responses / Bid Requests. |
| Impression Rate | The summary row indicates Impression Rate, calculated as: Impression / Responses; for other rows, non-bidding ad sources indicate Ad Impression Rate, calculated as: Impressions / Ad Responses; in-app bidding ad sources indicate Ad Material Impression Rate, which is Material Impressions / Ad Material Responses. |
| Latency(sec.) | The summary row indicates Latency, which is the time taken from the app sending an ad request to ToBid to receiving the ad fill; other rows indicate Ad Latency, which is the time taken from ToBid sending a request to the ad network to receiving the ad fill. Due to Unity's self-filling behavior, the fill time for Unity ad sources is not displayed. |
7.2 Points to Note
After activating A/B Test in the waterfall, the system will automatically generate a new experiment ID to record the data results of each A/B Test. Therefore, after activating/closing the current A/B Test, the waterfall will no longer retain the data before this A/B Test, and will only disclose the data after the current A/B Test is activated. Historical detailed data can be viewed in the "Comprehensive Report" section.
8. Data Discrepancies and Common Issues
8.1 The significant gap between ToBid estimated data and API data can stem from various reasons, including:
ToBid SDK relies on callback interfaces provided by various ad network SDKs to track SDK data such as impressions, returns, clicks, etc. Due to differences in statistical criteria, network packet loss, deduplication, and other factors, there may be discrepancies between the metrics tracked by ToBid and those tracked by third-party ad networks.
The data in the backend of ad networks only includes what they consider valid data. Invalid traffic such as frequent requests, cheating, network issues, etc., are filtered out in the data tracked by third-party ad networks. However, this portion of data is already included in ToBid's estimated data.
Typically, a reasonable GAP rate for data is within 5%. If it exceeds 10%, please contact your business or technical support colleagues for timely verification.
8.2 Why is it that sometimes some AD Network API data hasn't been updated by 10 am?
- The time for each AD Network to generate data is unstable. The aggregation platform will pull data and retry every hour through the Report API interface of the third-party AD Network. If the API dimension data has not been viewed on the report after 12 noon every day, you can contact the business colleague for help and check the reason.
8.3 If the ad placement or ad source is deleted from the platform, will the data still be displayed in the report?
- Yes, all ad placement or ad sources created on the platform will permanently retain data. Deleted ad placement or ad sources, although deleted on the platform, are actually logically deleted. If the corresponding data dimension is selected on the data report, the word "deleted" will be displayed.
When an ad placement or ad source is deleted, it can result in difficulties navigating to the corresponding ID for page redirection due to the removal of the root node in the operation path. To address this issue:
8.4 What is the relationship between estimated earnings and earnings API?
| Metrics | Description |
|---|---|
| Est. Revenue | - Estimated revenue for regular advertising sources = SUM (expected eCPM set in waterfall x ToBid impressions /1000) - Est. revenue from in-app bidding AD source =SUM(real-time price per display) |
| Revenue API | Revenue pulled via Reporting API, converted to account currency using real-time exchange rates |
When there is minimal or no discrepancy between the impression count statistics in ToBid and those in third-party ad networks, the sorting eCPM price filled in for ad sources in the waterfall becomes the key metric for estimating revenue.
Definition of Sorting Price: This price is solely used for prioritizing ad requests and estimating revenue in ToBid statistics. If an eCPM floor price is set in the ad network, it is recommended to align the price entered here with the set floor price.
In practical operation, the sorting price in the waterfall will serve as the sole sorting criterion for ad requests and ad displays.
