Keep connection settings together.
Exchange connection/openrtb2/{exchange}/bid
- Seat
- Identify the buyer on this connection
- Versions
- Accept configured OpenRTB versions
- Rate
- Apply the configured QPS limit
- Billing
- Choose the notice convention
Configure the connection.
Give each exchange its own route, seat, request-rate limit, accepted versions and billing convention.
Normalize the request.
Lift supported OpenRTB 2.5 extension fields into the internal model, including consent and SupplyChain information.
Use the shared pipeline.
Apply targeting, privacy, supply and budget controls, then send the bid and tracking URLs back to the exchange.
Normalize the supported version differences.
OpenRTB 2.5 extensions
regs.ext.gdpr
user.ext.consent
source.ext.schainNormalized fields
regs.gdpr
user.consent
source.schainExercise the route through Prebid Server.
The integration harness points the existing adprime adapter at pico DSP. It covers a CTV auction, VAST, notices, player events and no-bid cases, rather than claiming a dedicated upstream pico DSP adapter.
Is there a dedicated pico DSP adapter in Prebid Server?
The integration harness uses an existing adapter with a configured endpoint. It exercises the OpenRTB compatibility path; it does not claim an upstream pico DSP adapter or exchange certification.