Skip to main content

Data discrepancy troubleshooting ideas

Why is fill less than fill API?​

  • Fills: the number of ad fills returned by the TradPlus SDK after it sends a request to an ad network
  • Fill API: the number of fills that TradPlus pulls through the ad network's reporting API (some ad networks do not return fills)

Check the ratio of three-way timeouts; TP fill data does not contain timeout data, while three-way fill contains some timeout data

Why are there more impressions than valid impression APIs (or display APIs)?​

  • Impression: the number of showcases recorded by TradPlus.
  • Impressions API: the number of impressions that TradPlus pulls in through the ad network's reporting API.
  • Valid display API: TradPlus SDK receives display callbacks from three-party ad SDKs (some three-party ad SDKs do not return Banner or Native display callbacks)

Troubleshooting call problems: the same ad repeatedly calls TradPlus impression, TradPlus will record the impression multiple times, while the three parties will record only one effective impression (common in Banner or Native)

Why are there fewer impressions than valid display APIs (or display APIs)?​

It may be caused by the developer's repeated use of the ad view, developers need to combine with the app's usage scenarios, and independently check the invocation logic.

Why is there impression in the background data but no display API (meaning there is no display data in the three-party background)?​

a. Check whether test mode is enabled in the three-party background.

The test mode needs to be turned off.

b. Check if test mode is added in the access code.

Remove the test mode from the code.

c. Examine whether the test id is used.

The official id needs to be used.

d. Check if the necessary elements of the advertisement type are complete.

If the necessary elements of the ad type are not complete, the tripartite will not consider it a valid impression. We need to check the access to the sdk and complete the necessary elements of the ad type.