Yahoo Ads: Migrate to OpenRTB 2.6

[MananRPatel]

🔧 Type of changes

• new bid adapter
• bid adapter update
• new feature
• new analytics adapter
• new module
• module update
• bugfix
• documentation
• configuration
• dependency update
• tech debt (test coverage, refactorings, etc.)

Migrates the Yahoo Ads bidder (and its yahoossp / yahooAdvertising aliases)
from OpenRTB 2.5 to OpenRTB 2.6 on the wire. Three changes, all in the bidder:

1. HTTP header x-openrtb-version: 2.5 → 2.6 in
   src/main/java/org/prebid/server/bidder/yahooads/YahooAdsBidder.java.
2. Remove the in-bidder down-conversion. The bidder explicitly converted the
   request back to 2.5 before serializing it
   (conversionManager.convertFromAuctionSupportedVersion(bidRequest, OrtbVersion.ORTB_2_5)).
   That call is removed, along with the now-unused
   BidRequestOrtbVersionConversionManager dependency in the bidder and its
   YahooAdsConfiguration.
3. Legacy ext→top promotion for regs.{gpp, gpp_sid, coppa}. The old
   modifyRegs / resolveExtRegs block re-buried these (and gdpr/us_privacy)
   into regs.ext. It is replaced with a modifyRegs that, when a publisher
   sends the legacy 2.5-ext shape (regs.ext.gpp / regs.ext.gpp_sid /
   regs.ext.coppa) and the 2.6 top-level field is empty, copies the value to
   its 2.6 top-level slot and removes it from regs.ext. Typed ext-only fields
   (gpc, dsa), unknown regs.ext properties, and any of the three that
   could not be promoted (e.g. a malformed, non-textual gpp) are left in
   regs.ext untouched, so no value is silently dropped.

No publisher-facing config change is required bidder params (dcn, pos) are
unchanged, and bidder-config/yahooAds.yaml already declared ortb-version: "2.6".

Why

PBS-Java core up-converts every incoming request to its canonical 2.6 form
(BidRequestOrtb25To26Converter) before bidders run. The Yahoo bidder then
explicitly down-converted that back to 2.5 and re-buried
gpp / gpp_sid / coppa into regs.ext, and sent x-openrtb-version: 2.5.
Net effect: even fully 2.6-aware publishers had privacy/addressability fields
buried in .ext on the wire.

Removing the in-bidder down-conversion lets core's existing promotion reach the
wire. The new modifyRegs additionally promotes the three regulatory fields
that neither converter handles.

Field(s)	Legacy (2.5-ext) location	2.6 location	Promoted by
regs.gdpr, regs.us_privacy	regs.ext.*	top-level on Regs	core up-converter
user.consent, user.eids	user.ext.*	top-level on User	core up-converter
source.schain	source.ext.schain	top-level on Source	core up-converter
imp.rwdd	imp.ext.prebid.is_rewarded_inventory	top-level on Imp	core up-converter
regs.gpp, regs.gpp_sid	regs.ext.*	top-level on Regs	this PR (bidder)
regs.coppa	top-level (since 2.0) or regs.ext.coppa (legacy)	top-level on Regs	this PR (bidder)

What this means for publishers

Publisher integration shape	Before	After
2.6-shape (e.g. regs.gpp top-level)	bidder re-buried fields into .ext; header was 2.5	top-level fields stay top-level; header 2.6
Legacy 2.5-ext shape	values stayed in .ext on the wire	core promotes gdpr, us_privacy, consent, eids, schain, rwdd; the bidder additionally promotes gpp, gpp_sid, coppa; everything else passes through in .ext

Non-regulatory 2.6 fields the bidder does not transform (e.g. device.sua,
user.kwarray, site/app.inventorypartnerdomain, content.network,
content.channel) pass through in whatever shape the publisher sent.

What changed

File	Insertions	Deletions
src/main/java/org/prebid/server/bidder/yahooads/YahooAdsBidder.java	88	50
src/main/java/org/prebid/server/spring/config/bidder/YahooAdsConfiguration.java	2	4
src/test/java/org/prebid/server/bidder/yahooads/YahooAdsBidderTest.java	152	34
src/test/resources/org/prebid/server/it/openrtb2/yahooads/test-yahooads-bid-request.json	3	5
Total (4 files)	245	93

YahooAdsBidder.java bumps the header literal, removes the down-converter call
and dependency, and replaces the regs re-bury logic with modifyRegs +
resolveGpp / resolveGppSid / resolveCoppa helpers. The helpers operate on
a toBuilder() copy of Regs (the bidder already rebuilds the request
per-impression), so they cannot affect the request other bidders see.

Test plan

Automated

• mvn test -Dtest=YahooAdsBidderTest 27 unit tests pass. New cases cover:
  ext→top promotion, mixed publisher shapes (some fields top-level, some in
  ext), wrong-typed regs.ext values (no promotion), a malformed value left in
  ext while a sibling field promotes, and the no-ext short-circuit.
• mvn test -Dtest=YahooAdsTest integration test passes against the
  updated 2.6 wire fixture.

End-to-end against the Yahoo Ads SSP

A build of this branch was run as a local PBS-Java process (not Docker) and
pointed at the Yahoo Ads SSP endpoint. For each scenario a request was POSTed to
/openrtb2/auction with ext.prebid.debug: 1, and the exact bytes the bidder
put on the wire were read back from ext.debug.httpcalls.yahooAds[*] (request
body + headers). Every outbound carried x-openrtb-version: 2.6 and the SSP
returned HTTP 200. Bid presence varies with demand and is not asserted here.

Scenario	What it confirms (wire shape)
Site banner, 2.6-native	top-level privacy/addressability fields forwarded unchanged (no re-bury)
Site banner, legacy 2.5-ext	regs.gpp / regs.gpp_sid / regs.coppa promoted to top-level and removed from regs.ext; core-promoted fields (gdpr, us_privacy) at top-level; unrelated regs.ext keys (gpc, dsa) left in regs.ext
Video, plcmt=2 and plcmt=4	video request serialized with the 2.6 header
Video ad pod, 3 slots	per-impression split produces one outbound per slot with pod fields (podid, podseq, slotinpod, maxseq, poddur, mincpmpersec, rqddurs) intact
App banner / video / ad pod	app.id override applied (same mechanism as site.id); 2.6 wire
Multi-bidder (yahooAds + 2 other SSPs in one imp)	the yahooAds outbound is byte-identical to the standalone case adding other bidders does not change what PBS sends to Yahoo

How to verify locally

mvn package -DskipTests
java -jar target/prebid-server.jar \
  --spring.config.additional-location=<your-config>.yaml

curl -s -X POST http://localhost:8080/openrtb2/auction \
  -H 'Content-Type: application/json' \
  -d @your-yahooAds-request.json \
  | jq '.ext.debug.httpcalls.yahooAds[0].requestheaders["x-openrtb-version"]'
# → ["2.6"]

Test fixture changes

• test-yahooads-bid-request.json (integration): expected outbound now carries
  regs.gpp / regs.gpp_sid / regs.gdpr at top-level (previously under
  regs.ext).
• YahooAdsBidderTest.java: header assertion 2.5 → 2.6; the
  "remove/overwrite regs ext" tests are replaced with promotion + passthrough
  tests described above.

Backward compatibility

No breaking changes.

• Bidder-param schema (dcn, pos) unchanged.
• Bid-response handling (makeBids) unchanged.
• 2.6-shape requests are forwarded without re-burying.
• Legacy 2.5-ext requests get the core-promoted fields plus gpp / gpp_sid /
  coppa at top-level; all other fields pass through unchanged in .ext.

Aliases

yssp, yahoossp and yahooAdvertising are declared as aliases of yahooAds
in bidder-config/yahooAds.yaml and share the same YahooAdsBidder instance,
so all alias codes send the 2.6 wire after this PR.

---

For contact: prebid-tech-team@yahooinc.com

🤖 Drafted with assistance from Claude Code.