Urgent Help Needed: Sudden Spike in Ad Requests from an Older App Version Threatening My AdMob Account

122 views
Skip to first unread message

Vishrut Mavani

unread,
Apr 11, 2024, 11:45:34 PM4/11/24
to Google Mobile Ads SDK Developers
Hello everyone,

I'm facing a critical issue with my Android app and urgently need your insights or suggestions to navigate this situation.

My app is currently live with version 67, which typically sees an average of around 15,000 ad requests. However, in the past two days, there's been an unprecedented spike in ad requests, soaring to over 300,000. After digging into the Ads Activity Report, I was stunned to find that these requests are all coming from version 39 of the app.

Here's the catch: version 39 doesn't have a feature to force updates on the users. This has put me in a tricky position, as I can't directly compel the users of version 39 to update to the latest version, which adheres to the best practices for ad requests and user engagement.

This surge in ad requests is putting my AdMob account at high risk. I'm concerned about the potential repercussions and am eager to find a solution that can mitigate this risk as soon as possible.

Thank you in advance for your help and support.


Mobile Ads SDK Forum Advisor

unread,
Apr 12, 2024, 7:49:42 AM4/12/24
to vishrut.o...@gmail.com, google-adm...@googlegroups.com

Hi,

I don't think AdMob has app version blocking functionality. As you've mentioned, version 39 doesn’t have a feature to force updates on the user. But facing issues with AdMob requests on that. At this time I think you cannot do anything with the old version application. 

I can see only one solution here to create new ad units and implement a new version application which is having force update functionality. This will stop all your previous ads immediately. And from the fresh app new ad units ads will start serving.

 
This message is in relation to case "ref:!00D1U01174p.!5004Q02tP3UR:ref" (ADR-00230893)

Thanks,
 
Google Logo Mobile Ads SDK Team


Reply all
Reply to author
Forward
0 new messages