AdMob's brand-safety classifier circumvented by a coordinated casino-ad scheme. Google Play suspended our app for what AdMob shipped.

On April 20, Google Play suspended dataDex (com.talzz.datadex) — a 10-year-old app with ~5M downloads, 600k+ monthly active users, part of the Google Play Pass program since program inception — over an in-app interstitial creative. The creative turned out to be one of at least 11 documented variants of a coordinated casino-ad scheme served by Google's own ad network, AdMob. Every variant came through the same demand source under fake game-themed shell-app names. These were all classified under general categories, such as "Games" or "Toys and Games". The app's AdMob configuration already had sensitive categories like "Gambling & Betting (18+)" and "Social Casino Games" blocked at the time these creatives were served. The block had no effect, because AdMob's classifier never categorized the creatives as gambling. Google Play suspended our app for what AdMob shipped.

The systems failure

The cited creative was a casino interstitial — PROMO_GRAPHIC-6445.png, "Tower Rush" / "PREMIO 1500 EUR + 250 FREE SPINS GIOCARE" — an online-casino promotion. It was not uploaded by us, not selected by us, and not present in the Play Console assets, the Play Store listing, or the linked Google Ads account. It was programmatic demand served through the app's single AdMob interstitial unit.

When this creative served — and the ten other variants like it — the Gambling & Betting (18+) and Social Casino Games categories were already blocked in the app's AdMob configuration. Publisher-side category controls depend on AdMob's classifier. When the classifier is circumvented, the controls have no opportunity to act.

The scheme is coordinated. AdMob's classifier was circumvented.

The actual served count is almost certainly higher than 11; "at least 11 documented" is the floor verifiable from our AdMob review records, not the ceiling.

The 11 documented variants

All eleven were served through AdMob via the same demand source, under fake game-themed shell-app names. Per-variant screenshot evidence is available in the public bundle.

Our app

dataDex (com.talzz.datadex). Live on Google Play since 2016. ~5M cumulative downloads. 4.5+ average rating. 600k+ monthly active users. Part of the Google Play Pass program since program inception (2019). Clean policy record across the entire decade.

Publisher-side controls

Post-suspension, we tightened controls:

• All sensitive AdMob categories disabled. (Screenshot in bundle.)
• Maximum AdMob ad content rating set to "T" (Teen), which excludes adult and casino creatives at AdMob's classification layer. (Screenshot in bundle.)
• The AdMob ad unit fully disabled — the app currently serves zero ads of any kind.
• All linked Google Ads campaigns disabled.

These additional steps make recurrence impossible from the publisher side. They do not address the underlying classifier failure that allowed the eleven variants through in the first place.

The internal-redress record

Standard Google Play appeal — case 2-1866000040535, agent Ronan. Stuck in a template-reply loop. Four verbatim copies of the App Promotion policy template, instructing the publisher to "remove your ad campaign or promotion" or "upload a new app under a new package name." The detailed remediation evidence and the systems-failure analysis are unaddressed across all four rounds.

Parallel Google Play Developer Support ticket — case 9-9277000041337, agent Joseph. Engaged on the merits, acknowledged the remediation in writing, confirmed in writing that the standard appeal channel was cycling automated templates, re-flagged the case internally for human review, then closed his desk per scope.

AdMob support — case 4-3221000040899, agent Qian. Three brush-offs across two days, none engaging with the classifier-failure evidence. The first reply opens with an apology that AdMob does not support Hebrew — our submission was in English; only the locale-driven auto-acknowledgement was in Hebrew — suggesting our submission material was not actually read. Subsequent replies redirect to the Play Console team for "cross-product transfers" the publisher never requested.

Public escalation — two community threads, both stalled. When official channels stalled, we posted on Google's public Help Communities for escalation by a Product Expert:

• On April 22 we posted on the Google Play Developer Community. A Product Expert escalated the case the same day. The Product Expert's last reply, on April 26, was "I will let you know, if I get an update from the team." As of May 5, the team has not followed up.
• On April 29 we posted on the AdMob Help Community. A Product Expert engaged within 48 hours and stated they would escalate the case from the AdMob side. As of May 5, no further follow-up.

Both threads remain open. Both escalations are pending team responses that have not arrived. Public escalation paths are now stalled in the same shape as the official channels.

What this case actually needs

• A human reviewer at Google Play with the appeal record and the documented evidence in front of them.
• A confirmation from AdMob that the eleven variants violated AdMob policy and were misclassified by AdMob's classifier.
• Investigation into the broader casino-ad scheme that bypassed AdMob's classifier, as this issue has the potential to affect many other publishers.
• Internal coordination between AdMob and Google Play on the matter.

Public evidence bundle (PDF report, 11 creative screenshots, AdMob configuration, full appeal threads): https://drive.google.com/drive/folders/1d6SdbJrHdGSe4IJHnEPesKDt_PcdWQDB