Ad Serving Limited Despite ~8% Average CTR — Request for Clarification and Review

2 views
Skip to first unread message

exciting

unread,
3:35 AM (5 hours ago) 3:35 AM
to Google Mobile Ads SDK Developers
ctr.png

My AdMob account recently received an “Ad serving limited” restriction. I reviewed the Policy Center, but there are no specific violations or actionable details shown—only general guidance about invalid traffic.

I want to highlight one key point: on the day the limitation occurred, my overall CTR was around ~8% on average, based on clicks ÷ impressions. From my perspective, this does not appear extreme enough to justify a full ad-serving limitation across my apps, especially since:

  • I do not click my own ads, and my/team devices are blocked from generating ad traffic.

  • My apps primarily show banner ads, and only show one interstitial/open-type ad at startup (not repeated).

  • I do not design UI flows that encourage clicking ads.

Because this restriction impacts my livelihood as an indie developer, I need a clearer explanation of what triggered the limitation. Could you please confirm:

  1. Which app(s) or ad unit(s) were primarily responsible for the invalid traffic signals?

  2. Whether the issue was tied to specific countries/regions, traffic sources (e.g., Google Ads campaigns), or time windows?

  3. Whether the invalid traffic concern is related to accidental clicks, bot/automated behavior, or low-quality paid acquisition, and how you determined that?

  4. What exact remediation steps you expect me to take beyond the generic invalid-click documentation, so I can prevent recurrence.

If you need logs or additional data (app list, date ranges, traffic breakdown by country/ad unit, mediation setup), I can provide them. I am requesting a manual review and concrete guidance so I can resolve this properly.

Reply all
Reply to author
Forward
0 new messages