Google Play ad Fraud policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps that display ads or send ad impressions, clicks, or attribution events.
Ad fraud means presenting activity to an ad network as genuine user interest when it isn’t. It can come from hidden ads, fabricated clicks, false attribution, or dishonest inventory information.
What to check
Inspect ad visibility, click handlers, attribution SDKs, and the package and platform identifiers sent to networks. Check for ads rendered behind other views or triggered outside the app.
Look at dependency behavior even if you didn’t build a custom advertising system. A mediation component can generate invalid activity on your behalf.
How to address the rejection
Remove artificial interactions and correct inventory data. Ensure impressions and clicks reflect the user’s actual experience, and remove providers that generate fraudulent traffic.
Use test ads when checking placements. Trace the event sequence for a displayed ad and a real user interaction, then verify there are no background clicks or hidden placements. Provide the affected SDK version and the implemented fix. Better disclosure doesn’t make fabricated ad traffic acceptable.
Messages this guide can help with
Ad Fraud; Ad Fraud policy violation; Ad Fraud rejection; Ad Fraud denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Ad Fraud Checked 22 September 2026