1. Troubleshooting Instructions
(1) TopOn’s data indicators come from two sources: network APIs and TopOn statistics
Type | Sources |
---|---|
Network API |
The data indicators come from the third-party network API. Prerequisite: You need to enable the reporting API authorization of the corresponding network in the TopOn background [Network] module to see the data. TopOn background revenue and data indicators with API suffix are all network API data. Notice!: 1. You need to open the report API authorization so that TopOn can pull API data. Third-party networks use this to settle accounts with developers. All data with API are settlement data of the platform. 2. Regardless of whether API authorization is enabled or not, all settlement data is subject to the backend of the third-party platform. The statistics of TopOn backend are for reference only. |
TopOn Statistics |
The data indicators come from TopOn tracking points. Prerequisite: You can see the data only after you connect to TopOn SDK. Except for revenue, all data indicators without API suffix in the TopOn backend belong to TopOn statistical data. Note: All indicators without API are from TopOn statistics. They are for reference only and have nothing to do with the actual settlement amount of the platform. |
(2) Update time of each data in TopOn report
The update time of different data indicators will vary, as follows:
● Performance , Full report , Hourly Report , Mediation , traffic management , network :
① DAU, new users, and retention rate: updated every 2-3 hours.
② Other TopOn SDK statistics except DAU, new users and retention rate: updated every 5 minutes.
③ Reporting API data of the network (we will pull the network data of the previous day in 5 time periods): 3:30, 10:50, 14:30, 16:30, 21:00.
● User Engagement:
① LTV: Yesterday’s data was updated around 13:00 today.
② Estimated LTV: The data for the day is updated at around 9:00 am on the same day, and then updated every 4 hours.
③ Retention: Yesterday’s data was updated around 8:00 this morning.
2. Troubleshooting gaps between network and API data
Items | Steps |
---|---|
Data Delay | TopOn will pull the network data of the previous day in the following 5 time periods: 3:30, 10:50, 14:30, 16:30, 21:00 |
Time zone | Confirm whether the time zone of the network is consistent with the time zone of TopOn. The default time zone of TopOn is East 8. • If the problem cannot be solved after checking the above factors, please contact the TopOn contact person for assistance. |
3. Check for gaps between TopOn data and API data
3.1 Meaning of data indicators
More data indicator interpretation >> View
name | Interpretation |
---|---|
eCPM | TopOn calculates eCPM based on the actual revenue obtained from the network through the reporting API and the impression statistics of TopOn. |
eCPM API | TopOn calculates the actual revenue obtained from the network through the reporting API and the impression API. |
Estimated eCPM | The estimated eCPM is calculated based on the estimated revenue and the impressions counted by TopOn. Note: ①Estimated eCPM is provided on the same day; ② Conventional ad sources are calculated based on manually entered eCPM prices, and bidding ad sources are calculated based on real-time bidding prices; ③Meta bidding ad sources are estimated based on historical eCPM API. |
impression | The number of callbacks TopOn receives when the network SDK displays successfully. |
Impression API | TopOn pulls the number of ad exposures from the network through the reporting API. Tips: Due to different statistical calibers, there may be certain differences between the impression statistics of TopOn and the impression statistics of the network (impression API). |
Revenue | The revenue that Topon obtains from the network through the API. |
Estimated revenue | ① Bidding ad source: estimated revenue is obtained by summarizing the real-time advertising display prices; ② Non-bidding ad source: manually filled eCPM price * TopOn statistics display summary to get estimated revenue; ③Meta estimated revenue is based on Meta’s historical eCPM API* TopOn statistics. |
3.2 Checking the gap between revenue and estimated revenue
Tips: Generally speaking, if the GAP between revenue and estimated revenue is within 15%, we consider it acceptable. This is because both eCPM and display may have GAP.
name | Interpretation |
---|---|
revenue | The revenue that Topon obtains from the network through the API |
Estimated revenue | ① Bidding ad source: estimated revenue is obtained by summarizing the real-time advertising display prices; ② Non-bidding ad source: manually filled eCPM price * TopOn statistics display summary to get estimated revenue; ③Meta estimated revenue is based on Meta’s historical eCPM API* TopOn statistics. |
● The premise that the income is equal to or close to the estimated income
(1) Revenue calculation formula: revenue = number of impressions *eCPM/1000
(2) If you want the estimated revenue from TopOn statistics to be close to the actual revenue from third-party platforms, both the number of impressions and the number of eCPMs must be close.
(3) If there is a gap in the display, please refer to step 2.3.2 for display-related issues.
(4) If there is a gap in eCPM, please refer to step 2.3.3.
(5) If the display and eCPM gaps are resolved, there will basically be no gap.
● Troubleshooting steps
1 | Confirm the comparison data. The time zone in the three-party backend and TopOn backend is consistent. If the time zone is inconsistent, there will definitely be a GAP. |
2 | First confirm the network with the big gap, which network it is, and which time range. It is recommended to first check the data of various networks yesterday. After determining the network with the largest gap, you can then check the gap in finer dimensions: revenue gap in app, placement, and ad source dimensions. View path: TopOn backend → Report → Full report |
● Example
How to use full reports to identify profit gaps?
(1) Issue: Admob had a discrepancy between estimated revenue and actual revenue on March 30
(2) Determine the gap in the application dimension: TopOn Backstage → Report → Full Report, set up according to the following steps (refer to Figure 1 below) to determine the applications with the largest actual gap.
① Dimension selection: date, network
② Filter: Date is yesterday (or other dates with a large difference)
③ Metrics (part of selecting a pen): Select Estimate Revenue, Revenue API
- If the difference between individual apps is huge, continue to investigate the placement dimensions and ad source dimensions (similarly, in the dimension part, add filtering of placements and ad sources).
- There is a big difference between two or more apps: Differentiate between apps and check the placement and ad source dimensions separately.
- There is a big gap between all applications and the displayed API is blank: it can be basically determined that the revenue has not been pulled back for the time being, that is, the data update time may not have arrived yet. You can wait until later in the day to check the revenue.
If the historical revenue data is not pulled back, it is recommended to first confirm that the report API has been bound, then contact TopOn operations, provide the network and time range of the missing data, and re-pull the historical data.
(Report API addition path: TopOn backend → [Network]→[Monetization] → Edit → Report API has been activated, refer to Figure 2 below)
3.3 Troubleshooting gaps between Impression and Impression API
name | Interpretation |
---|---|
Impression | The number of callbacks TopOn receives when the network SDK displays successfully. |
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(Impression API) counted by TopOn and those counted by the network. |
Impression Gap | The difference between the number of callbacks received from the network SDK for successful display counted by TopOn and the number of ad exposures counted by the network. [Calculation formula: (Impression - Impression API) / Impression API.] |
When the Impression gap exceeds 15%, you can follow the steps below to find out the cause. If you still cannot locate the cause, you can contact TopOn's operations team to troubleshoot together.
● If the impression API > impression
Check whether the advertising ID of the third-party network is old and whether there is any individual traffic that does not request ads through TopOn; for example, whether there is an old version that does not use the TopOn SDK.
● If the impression API < impression
(1) First confirm the ad format and the network
(2) Distinguish the data of each ad source and find out which ad source has the most obvious difference.
For example:
① The ad source B on platform A has an impression API of 700 and an impression of 1000 on March 7, 2023. The impression GAP here is relatively large.
The impression API here is the actual display data pulled by TopOn from the platform, and the display is the display callback sent back by the platform counted by TopOnSDK, which means there is a loss of 300 displays. Although these 300 displays have been called back to TopOn, the platform has deducted them from the settlement data. It is recommended that developers contact network A for further confirmation.
② The impression API of ad source C on platform A on March 7, 2023 is 930, and the display is 1000. The display GAP here is small, which is due to statistical caliber and network reasons, and is acceptable.
● Optimize effective advertising impression
① Do not block, distort or blur advertising images and content.
② The display time of native and banner ads exceeds 1 second, and the display area exceeds 50%.
③ The display area of the splash screen ad must exceed 75% of the screen, and it must play for 5 seconds or until the skip button is clicked. For example, some developers need to add their own app logo at the bottom of the page when designing the splash screen. This area cannot be too large, and the ad display area must exceed 75% of the phone screen.
Notice:
① The duration and area requirements may vary from platform to platform, but generally speaking, there are requirements for these two indicators. The display duration here refers to the time that users stay on the ad page for more than 1 second after the ad content is displayed. For example, if a user quickly brushes away some information flow ads while scrolling through the information flow, this may not be counted as an effective display.
② Display area. Please note that even if the user has seen the entire ad, it does not mean that the display area is greater than 50%, because there may be a transparent mask covering the ad during integration. Although it cannot be seen by the naked eye, the network will also consider that the display area does not meet the requirements.
3.4 Troubleshooting gaps between eCPM and eCPM API
name | Interpretation |
---|---|
eCPM | TopOn calculates eCPM based on the actual revenue obtained from the network through the reporting API and the display statistics of TopOn. |
eCPM API | TopOn calculates the actual revenue obtained from the network through the reporting API and the impression API. |
If there is a discrepancy between eCPM and eCPM API, it is mainly due to the discrepancy between the display statistics of TopOn and the impression API. Please follow the troubleshooting steps in 2.2.
3.5 Estimated eCPM and eCPM API
name | Interpretation |
---|---|
eCPM API | TopOn calculates the actual revenue obtained from the network through the reporting API and the impression API. |
Estimated eCPM | Calculate the estimated eCPM based on the estimated revenue and the display statistics of TopOn (which can be understood as the average of the manually filled eCPM of the regular ad source and the eCPM calculated based on the real-time bidding price of the bidding ad source) Note: ① Estimated eCPM is provided on the same day; ② Regular ad sources are calculated based on manually entered eCPM prices, and bidding ad sources are calculated based on real-time bidding prices; ③ Meta bidding ad sources are estimated based on historical eCPM API |
● The premise of eCPM estimation and eCPM API consistency
The sorting price and the eCPM API price need to be modified to be consistent, and the impression and impression API data need to be close.
Modification path: Mediation-Select all placements under the application
① For ad sources with a reserve price: Check whether the sorting price is consistent with the eCPM API price. Adjust the sorting price in the TopOn backend to the corresponding eCPM API price. You can select the pen symbol to modify it manually.
② Advertising sources without reserve price:
- If you have Report API permissions, it is recommended that you configure the Report API and turn on automatic pricing to automatically adjust the sorting price to be consistent with the eCPM API.
- If you do not have the reporting API permission, it is recommended to upload data from a third-party platform. After the server completes the processing, compare the eCPM API and the sorting price, and manually fill in the price to be consistent with the actual price. >> How to upload data from a third-party platform
● Troubleshooting steps
(1) Use the full report to identify the network with the largest gap → the problematic placement → the problematic ad source, and determine the date range with the problem. It is recommended to first check the data of each network yesterday.
Viewing path: TopOn background - report - full report, or TopOn background - Mediation.
① Dimension selection: date, app, network, placement, ad source
② Filter: Date is yesterday (or other dates with large gaps), application or ad space to be checked, ad platform (ad platform to be checked)
Tips: For dimensions and filters, developers can customize their selections based on their troubleshooting needs.
③ metrics (part of the pen selection): You need to check eCPM and eCPM API, and the rest can be based on your own needs
④ Observe and compare the networks and ad sources with large gaps, and determine the networks/ad sources/placements with large gaps
(2) Compare data GAP and solve the problem accordingly
If the sorting price is incorrectly filled in --> modify the sorting price to be consistent with the actual eCPM API of the platform.
Modification path: Developer backend-Mediation
Reason: The calculation formula of TopOn backend estimated revenue is as follows. The accuracy of estimated revenue is affected by the accuracy of ranking eCPM.
If the eCPM is inconsistent and the GAP is large (generally, an eCPM GAP within 5% is acceptable) after the changes are consistent [at least one week], please contact the third-party platform or TopOn operation team for assistance in resolving the issue.
4. FAQ
(1) Why are the sorting prices and eCPM API inconsistent?
① Check whether the code position display volume is too small. This situation is easy to occur when there are only a few displays. It is recommended to evaluate after the cumulative display volume is greater than 1,000.
② Check whether the sorting price of the code position is consistent with the sorting price filled in the [Third-party Backstage].
③ Make sure that ① and ② have been completed, that is, make sure that the cumulative display volume of the code position is greater than 1000, and the sorting price of the code position is consistent with the sorting price filled in the [third-party backend], and then it is recommended to observe for at least [1 to 3 days]. If the sorting price of the code position is still [for at least 1-3 days] and the difference between the sorting price and the eCPM API price is large (GAP is greater than or equal to 15%), it is recommended to consult the TopOn operation team.