Skip to content

MobileFuse: Pass imp.ext through to the MobileFuse endpoint - #4691

Open
dtbarne wants to merge 1 commit into
prebid:masterfrom
dtbarne:mobilefuse-pass-imp-ext
Open

dtbarne wants to merge 1 commit into
prebid:masterfrom
dtbarne:mobilefuse-pass-imp-ext

Conversation

@dtbarne

@dtbarne dtbarne commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

🔧 Type of changes

  • bid adapter update

✨ What's the context?

The MobileFuse bidder rebuilt imp.ext with only skadn, so imp.ext.gpid, imp.ext.data and every other imp-level extension publishers send never reached MobileFuse. A publisher reported that GPID was missing from requests arriving at our endpoint. The matching PBS-Go change is prebid/prebid-server#5061.

🧠 Rationale behind the change

Passing imp.ext through untouched is the simplest change, and it carries over any future imp-level signals without more adapter work. The MobileFuse endpoint ignores fields it doesn't use, including bidder.

🧪 Test plan

  • MobilefuseBidderTest: the skadn test now checks that imp.ext (bidder, skadn and gpid) passes through unchanged, and the tagid test no longer expects ext to be stripped.
  • MobilefuseTest (integration): the expected outgoing request now includes imp.ext with tid and bidder.

🏎 Quality check

  • Are your changes following our code style guidelines?
  • Are there any breaking changes in your code?
  • Does your test coverage exceed 90%?
  • Are there any erroneous console logs, debuggers or leftover code in your changes?

🤖 Generated with Claude Code

https://claude.ai/code/session_018nDAKza5SSDcVBDLyWfAoL

The bidder rebuilt imp.ext with only skadn, dropping gpid, data and
every other field publishers send. Leave imp.ext as-is so GPID and
first-party data reach MobileFuse.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant