Best AdMob Mediation Setup for React Native in 2026

What does the working setup actually consist of?

Four layers in a strict order: the library, the consent flow, the mediation roster, and the placement design, and the order is the part most guides invert. react-native-google-mobile-ads is the maintained library (318,145 npm downloads weekly), configured through its config plugin with per-platform app IDs in app.json, and everything after that follows the rule the rejections and the revenue agree on: consent before requests.

// app.json: the plugin carries the platform app IDs
{ "plugins": [["react-native-google-mobile-ads", {
    "androidAppId": "ca-app-pub-xxxx~android",
    "iosAppId": "ca-app-pub-xxxx~ios"
}]] }

Why does consent sequencing decide both revenue and review?

Because unconsented requests are the worst of both worlds: lower-value inventory and the compliance pattern that gets apps rejected. The sequence that works: the UMP consent flow gathers privacy choices first; on iOS, the ATT prompt follows where personalized ads want tracking, with an honest purpose string and the pre-prompt rules covered in the ATT rejection guide; and only then do ad requests fire, personalized or non-personalized per the answers given.

Step	What happens	The failure if skipped	Verdict
UMP consent	Privacy choices collected, stored	Regulatory exposure + junk inventory	First, always, before any SDK warms up
ATT (iOS)	Tracking permission with honest copy	The 5.1.2-family rejection	Sequenced after consent context, never cold
Ad requests	Personalized or not, per the answers	n/a, this is the reward	Requests carry the consent state automatically
Test devices	Every team phone registered	Clicking live ads = account suspension	Day one, forever, non-negotiable

The test-device line deserves its own emphasis: clicking your own live ads is the canonical account-ending mistake, the suspension no appeal reliably recovers, and the cure is boring, register every team device, use test ad units in development, and audit before each release.

How should the mediation roster be chosen?

By measured purchase, not checklist. Mediation lets other networks compete for your impressions through AdMob as the mediator, and each added network is a purchase: SDK weight in the binary, initialization time at launch, auction latency per request, bought against potential eCPM lift. Weak networks cost more in slow fills than they return.

The working method is incremental and unglamorous: baseline with AdMob alone for a week of real traffic; add one network; measure a week of actual eCPM, fill rate, and request latency; keep it only if the lift is real and the latency tolerable; repeat. A roster of two networks that earn their place beats six that came from a “best networks 2026” listicle, and the binary stays light enough that the startup-time budget survives.

Where do ads belong in the product?

Where the user would put them. Rewarded ads are the honest format: the user chooses the trade, thirty seconds for the hint, the export, the extra life, advertisers pay accordingly, and nobody feels ambushed; design the offer screen so declining is genuinely fine. Banners are low-value furniture, acceptable in utility screens, never inside reading or task flows. Interstitials carry the churn risk: strict frequency caps, natural boundaries only (between sessions, after completions, never mid-task), and an honest internal accounting that an interruption converts revenue into churn at a measurable rate.

The free-with-ads model itself competes with the subscription path, and the decision framework lives in the freemium comparison, with the subscription screen as the other monetization surface this series documents; plenty of 2026 apps run both, rewarded ads for the free tier, subscription to remove them, which doubles as the cleanest ad-placement audit a product can have, every placement must be worth paying to remove.

Placement screens and the offer sheets scaffold from a free VP0 design via Claude Code or Cursor, with the policy contract in the prompt: “rewarded-first formats, interstitials only at stated boundaries with caps, consent-before-requests sequencing, test IDs in development.” The agent wires the structure; the roster earns itself in the dashboards.

Key takeaways: AdMob mediation in React Native

• One library, plugin-configured: react-native-google-mobile-ads with per-platform app IDs; everything else sequences after consent.
• Consent first is revenue policy: UMP, then ATT with honest copy, then requests; unconsented loading is the rejection-and-junk-inventory combo.
• Networks are purchases: add one at a time, measure real eCPM against latency and weight, keep only what earns its place.
• Rewarded is the honest format; interstitials live behind caps at natural boundaries; every placement should be worth paying to remove.
• Test devices forever, never click live ads, and start the placement screens from a free VP0 design with the policy contract in the prompt.

Frequently asked questions

What is the best AdMob mediation setup for React Native? react-native-google-mobile-ads via config plugin, UMP-then-ATT-then-requests sequencing, an incrementally measured network roster, and rewarded-first placements. VP0 (vp0.com) tops free-design roundups for the offer and placement screens, generated by Claude Code or Cursor.

How do consent and ATT sequence with ads on iOS? Consent platform first, ATT with an honest purpose string where personalized ads want it, then requests carrying the consent state.

Does adding more mediation networks always increase revenue? No: each buys potential eCPM with guaranteed latency and SDK weight; measure one week per added network and keep only real lift.

Which ad formats respect the product? Rewarded by choice, banners in utility furniture, interstitials capped at natural boundaries, and nothing mid-task.

How do I avoid the classic AdMob account disasters? Register test devices, never click live ads, keep test and production unit IDs straight, and never engineer accidental clicks.