feat: add neighboringContentUrls request option - #875
Merged
mikehardy merged 4 commits intoAug 18, 2026
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #875 +/- ##
==========================================
- Coverage 43.72% 40.88% -2.83%
==========================================
Files 30 36 +6
Lines 549 685 +136
Branches 151 175 +24
==========================================
+ Hits 240 280 +40
- Misses 309 405 +96 🚀 New features to boost your workflow:
|
philipheinser
force-pushed
the
feat/neighboring-content-urls
branch
from
August 17, 2026 08:25
535c376 to
3922173
Compare
Expose Google Mobile Ads brand-safety neighboring content URLs on RequestOptions for iOS and Android.
setNeighboringContentUrls expects a List, not a HashSet.
Mirror contentUrl e2e/jest coverage for URL length and add e2e tests for the neighboringContentUrls request option.
mikehardy
force-pushed
the
feat/neighboring-content-urls
branch
from
August 18, 2026 01:38
3922173 to
543edab
Compare
mikehardy
approved these changes
Aug 18, 2026
Collaborator
|
🎉 This PR is included in version 16.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Google Mobile Ads supports neighboring content URLs for brand safety on both platforms (
GADRequest.neighboringContentURLStringson iOS,AdRequest.Builder.setNeighboringContentUrlson Android). This library already exposescontentUrl, but not the neighboring URLs used when an ad sits next to other web content (for example articles in a feed).This adds
neighboringContentUrlstoRequestOptions:Validation matches
contentUrl: HTTP(S) only, max 512 characters per URL, and a maximum of 4 URLs as documented by Google.Related issues
None.
Release Summary
feat: add neighboringContentUrls request option for brand-safety targeting
Checklist
and followed the process outlined there for submitting PRs.
AndroidiOSe2etests added or updated in__tests__e2e__jesttests added or updated in__tests__Test Plan
__tests__/requestOptions.test.tsxfor type, URL, length, and max-count validation.neighboringContentURLStrings) and AndroidsetNeighboringContentUrls.🔥