Impression Loss Due to Navigation Gestures/Backpress During Ad Display

82 views
Skip to first unread message

Sumitra

unread,
Jun 30, 2025, 6:50:10 PM6/30/25
to Google Mobile Ads SDK Developers
Issue Description:
In recent Android versions (especially Android 10+ with gesture navigation), users are able to swipe back or use the system back gesture right after an interstitial ad is triggered via ad.show(),
but before the admob close button visible back callback is fired.

My app uses user-friendly and responsible ad practices, showing AdMob full-screen interstitial ads only after user interaction, delay, and consent-related checks.
However, due to Android's gesture-based navigation or back button, users can dismiss the ad — typically within 400–700ms — leading to significant impression loss and zero revenue, even though the ad was triggered correctly.
This happens before AdMob's close button is visible, and before onAdImpression() fires, which is beyond developer control.
here i just try to show whats happening:
Frame 1.png

From the user’s perspective, the back gesture is convenient — but from the developer’s standpoint, this interrupts a legitimate monetization flow, since no proper visible = no revenue.

I understand the importance of user control and policy compliance — I'm not looking to block the close button permanently. However, this issue is currently leading to significant impression loss, especially from users with fast swipe-back actions.

I look forward to your technical guidance. This issue significantly impacts developer revenue while maintaining positive UX.

Please Confirm if there's official solution to prevent back-gesture during initial ad display

Sincerely,
Sumitra

Mobile Ads SDK Forum Advisor

unread,
Jul 1, 2025, 1:25:10 AM7/1/25
to sumitra...@gmail.com, google-adm...@googlegroups.com

Hi,

Thank you for contacting the Mobile Ads SDK Support team. 

This is a known issue and our team is actively working on a resolution. Once we receive any updates, we will intimate you. 

Meanwhile you may consider setting `android:enableOnBackInvokedCallback="false"` or removing `android:enableOnBackInvokedCallback` from the Manifest file. This will prevent back press/gesture functionality until the user selects the advertisement's close button.


Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5
[2025-07-01 05:23:45Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rgo6R:ref" (ADR-00316561)



Serkan Sekman

unread,
Jul 4, 2025, 4:21:59 AM7/4/25
to Google Mobile Ads SDK Developers

Hi there,
I'm experiencing a similar issue. However, instead of using Google Ads directly, I'm showing Interstitial ads through the Max-Applovin SDK.

Just like mentioned above, I added:

<activity
            android:name="com.google.android.gms.ads.AdActivity"
            android:enableOnBackInvokedCallback="false"
            android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"
            />

to the manifest, but when I see the ad and press the device back button before the ad completes its display time, the ad gets dismissed.

I wasn't able to get the suggested solution working properly.
I'm currently using play-services-ads:20.4.0

Do you have any other suggestions?

Thanks in advance!

1 Temmuz 2025 Salı tarihinde saat 08:25:10 UTC+3 itibarıyla Mobile Ads SDK Forum Advisor şunları yazdı:

Mobile Ads SDK Forum Advisor

unread,
Jul 4, 2025, 9:39:23 AM7/4/25
to serkan...@gmail.com, google-adm...@googlegroups.com

Hi,

It is always recommended to use the latest versions of the SDK. As of today, the latest version of the Google Mobile Ads Android is 24.4.0 please check in this and confirm.

Currently we don’t have any updates. We will inform you once we receive any updates. Meanwhile, your patience is important. 

Thanks,
 
Google Logo Mobile Ads SDK Team

Feedback
How was our support today?

rating1    rating2    rating3    rating4    rating5

[2025-07-04 13:38:14Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rgo6R:ref" (ADR-00316561)



Reply all
Reply to author
Forward
0 new messages