React Native Google Mobile Ads enables you to monetize your app with AdMob.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 56%
Response Time: -
First Timer Success: 100%
invertase/react-native-google-mobile-ads has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in invertase/react-native-google-mobile-ads respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 61.5 places invertase/react-native-google-mobile-ads in the A tier.
The external contributor pull request merge rate for invertase/react-native-google-mobile-ads is 55.6%, based on public PR activity from non-core contributors.
invertase/react-native-google-mobile-ads currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
React Native Google Mobile Ads enables you to monetize your app with AdMob.
Highly welcoming maintainers in invertase/react-native-google-mobile-ads. Prompt code reviews with positive guidance for new contributors.
Discussions in invertase/react-native-google-mobile-ads focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/invertase/react-native-google-mobile-ads?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (74% approval). Large PRs (>500 lines) take ~75 hours (26% approval). Keep your diff compact for rapid review.
What happened? On a physical iPhone development build, RewardedAdEventType.EARNED_REWARD and AdEventType.CLOSED are never delivered to JavaScript for a rewarded ad, even though Google's own native test-mode UI visually confirms the reward was granted ("Reward granted" banner), and even in a controlled reproduction where the app never leaves the foreground and never backgrounds. AdEventType.LOADED, RewardedAdEventType.LOADED, and all interstitial ad events (loaded, shown, dismissed) work correctly on the same build/device using the same wrapper library, so the native↔JS ad-event bridge is not broken in general — the failure appears specific to the rewarded ad's post-load event delivery. Reproduction (foreground-only, no backgrounding) Load and show a rewarded test ad (ca-app-pub-3940256099942544/1712485313, Google's official iOS rewarded test unit) via RewardedAd.createForAdRequest + addAdEventListener. Watch the ad play. Google's native test-mode UI shows the "Reward granted" conf
What happened? Summary NativeAd.addAdEventListener(NativeAdEventType.PAID, ...) exposes a payload type with currencyCode, but both native implementations emit the JavaScript payload key as currency. TypeScript accepts payload.currencyCode, but that property is undefined at runtime. The actual value is available at payload.currency. Evidence The NativeAd TypeScript payload declares currencyCode: export type NativeAdPaidEventPayload = { value: number; precision: number; currencyCode: string; }; https://discord.com/channels/295953187817521152/1059856784308850709/1539547481434492958 Platforms Android, but have not tested behavior on iOS React Native Info System: OS: Windows 11 10.0.26200 CPU: "(12) x64 AMD Ryzen 5 5600H with Radeon Graphics " Memory: 1.60 GB / 15.35 GB Binaries: Node: version: 24.15.0 path: C:\Program Files\nodejs\node.EXE Yarn: version: 4.10.3 path: C:\Users\Sanjay Sargam\AppData\Roaming\npm\yarn.CMD npm: version: 11.8.0 p
What happened? I want to use react-native-firebase and react-native-google-mobile-ads. However, Firebase has announced that future iOS support will be provided through Swift Package Manager (SPM) only, and CocoaPods support will be discontinued. Since react-native-firebase currently relies on use_frameworks! :linkage => :static, it is difficult to migrate to an SPM-based setup while using both libraries together. Would it be possible to support this use case? This also seems to be related to the discussion in react-native-firebase issue #9140: invertase/react-native-firebase#9140 Platforms Only on iOS React Native Info System: OS: macOS 26.6 CPU: (8) x64 Apple M1 Pro Memory: 30.30 MB / 16.00 GB Shell: version: "5.9" path: /bin/zsh Binaries: Node: version: 24.15.0 path: ~/.nvm/versions/node/v24.15.0/bin/node Yarn: version: 1.22.22 path: /opt/homebrew/bin/yarn npm: version: 11.12.1 path: ~/.nvm/versions/node/v24.15.0/bin/npm Watchman: v
What happened? Google just released swipeable interstial. Platforms Android, but have not tested behavior on iOS React Native Info . Are your using Typescript? My project is using Typescript package.json . app.json . ios/Podfile android/build.gradle android/app/build.gradle android/settings.gradle AndroidManifest.xml
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to invertase/react-native-google-mobile-ads, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of invertase/react-native-google-mobile-ads acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 55.6% were successfully merged into the primary branch.
invertase/react-native-google-mobile-ads has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 61.5 places invertase/react-native-google-mobile-ads in the Welcoming tier.
The external pull request merge rate is 55.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, invertase/react-native-google-mobile-ads currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for invertase/react-native-google-mobile-ads are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.