[Feature Request] Add registerWebView() support for WebView API for Ads
#855 ouverte le 23 mai 2026
Métriques du dépôt
- Stars
- (1 010 stars)
- Métriques de merge PR
- (Métriques PR en attente)
Description
Documentation Feedback
Feature Request
Problem
Google officially requires registerWebView() to be called on each WebView instance
to classify traffic as in-app (instead of web browser traffic), which affects:
- CPM (advertisers pay more for in-app traffic)
- Ad targeting via Ad Manager
- Policy compliance for WebView monetization
See official Google docs:
- https://developers.google.com/admob/android/browser/webview/api-for-ads
- https://developers.google.com/ad-manager/mobile-ads-sdk/android/browser/webview/api-for-ads
Current Situation
No maintained React Native package implements this today:
react-native-google-ads-webview(Wix) → abandoned since 2022- Manual native bridge → crashes on New Architecture (UIManagerModule is null in Bridgeless mode)
Expected Solution
Add a method like:
mobileAds().registerWebView(viewTag)
that handles the native bridge correctly for both Old and New Architecture,
similar to how the Flutter plugin implements it:
MobileAds.instance.registerWebView(controller)
See Flutter reference: https://developers.google.com/ad-manager/mobile-ads-sdk/flutter/webview
Why this belongs here
This package already wraps the Google Mobile Ads SDK on both Android and iOS.
registerWebView() is a method on MobileAds (Android) and
GADMobileAds.sharedInstance (iOS) — both already initialized by this package.
Platform
- Android
- iOS
- Both