RTD Modules and ortb2 5 Browser Enrichment Browser Prebid.js RTD Modules Data Providers Demand Partners 1 Init 2 HTTP calls 3 Segments 4 Enrich ortb2 5 Bid requests 6 Bids P_
RTD Modules and ortb2 Browser Enrichment 5 RTD modules 1 call data providers 2 for audience and content segments 3 , then merge results into ortb2 4 — site.content.data, user.data. Each HTTP call adds latency the browser pays, gated by auctionDelay. waitForIt per module forces the auction to block on that provider. Unlike 11 , enrichment costs the user's page-load time. FIELD NOTES → auctionDelay always waits the full timer even if data arrives early → device.sua — Chrome only → 75+ RTD modules exist but >3 stacks latency past auctionDelay P_ atd.postindustria.com/5

How It Works

RTD modules [1] call data providers [2] for audience and content segments [3], then merge results into `ortb2` [4] — `site.content.data`, `user.data`. Each HTTP call adds latency the browser pays, gated by `auctionDelay`. `waitForIt` per module forces the auction to block on that provider. Unlike {11}, enrichment costs the user's page-load time.

Field Notes

  • `auctionDelay` always waits the full timer even if data arrives early
  • `device.sua` -- Chrome only
  • 75+ RTD modules exist but >3 stacks latency past `auctionDelay`

Questions about RTD Modules and ortb2?

Get expert guidance from our team. We'll help you implement it.