invertase/react-native-google-mobile-ads

[Feature Request] Add registerWebView() support for WebView API for Ads

Open

#855 opened on May 23, 2026

View on GitHub
 (2 comments) (2 reactions) (0 assignees)TypeScript (213 forks)github user discovery
help wantedstale

Repository metrics

Stars
 (1,010 stars)
PR merge metrics
 (PR metrics pending)

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:

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

Contributor guide

Research direction
Implement a new method `mobileAds().registerWebView(viewTag)` that bridges to the native `MobileAds.registerWebView()` on Android and `GADMobileAds.sharedInstance.registerWebView()` on iOS. Ensure compatibility with both Old and New Architecture (Bridgeless mode) by using the proper native module registration (e.g., TurboModules or Fabric components). Reference the existing Flutter plugin implementation for guidance.
Tech stack
typescriptjavascriptreact nativeandroidios
Domain
mobile
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
React NativeAndroid SDKiOS SDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40