Discrepancy Between AdMob API Data and Dashboard – Anyone Else Facing This?

7 views
Skip to first unread message

jignesh boricha

unread,
Oct 2, 2025, 7:37:13 PMOct 2
to AdMob API Developer Forum
Hey devs 👋

I'm working on a portal that integrates with the Google AdMob API to display reporting metrics like earnings, ad requests, impressions, etc.

For a comparison between the API and the AdMob dashboard (13–14 July), I noticed some unexpected differences. Here's a quick comparison:

| Metric | Portal (Dashboard) | API Response | | ------------------ | ------------------ | ------------ | | Estimated Earnings | $X.85 | $X.9112 | | Total Ad Requests | XX,691 | XX,253 | | Matched Requests | XX,163 | XX,559 | | Impressions | XX,403 | XX,726 | | Clicks | X,560 | X,593 | | Match Rate | XX.59% | XX.65% | | Show Rate | XX.62% | XX.23% | | Impression CTR | X.67% | X.36% |


Most values are fairly close, which is fine. But the Show Rate (a difference of 2.69 percentage points) and Impression CTR (a difference of 21.39 percentage points) are off by quite a bit. I'm wondering if others have faced similar discrepancies?

My thoughts so far:

Could it be timezone misalignment?

Is there data sampling on either end?

Maybe some metrics are calculated differently by the dashboard?

I would love to hear if anyone has dealt with this issue or found a workaround/explanation. 🙏

Thanks in advance!

AdMob API Developer Forum

unread,
Oct 2, 2025, 7:51:47 PMOct 2
to AdMob API Developer Forum
Hello,

We have checked our systems and haven't found a general discrepancy between AdMob API and AdMob UI reporting data.

When users report a mismatch, it's usually due to one of the following two reasons. Please check these first:
  • Currency Mismatch: The most common issue is incorrectly comparing data in different currencies (e.g., Euro vs. USD). Please ensure the currency setting is identical in both the API request and the UI report.
  • Timezone Mismatch: Since metrics like Show Rate are also mismatched, the issue may be the timezone. The API defaults to account's timezone, but the timezone can be explicitly set to "Americas/Los_Angeles", more details are here.

If these checks do not resolve the issue, please share the exact API request you are running so we can troubleshoot it directly.

Thanks,
Reply all
Reply to author
Forward
0 new messages