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