Prebid.js RTD Provider module
The Prebid.js RTD Provider is a ready-made integration that connects StackUp enrichment data to your ad stack. It enriches Prebid.js bid requests with StackUp Content Taxonomy, IAB Audience Taxonomy, and legacy StackUp audience signals, derived from the current page before the auction fires, so every bidder sees the segments without any per-bidder work.
What the module does
Instead of calling the Curation API yourself and wiring the response into Prebid, the RTD module does the whole loop on-page: it identifies the current article, fetches its enrichment, and injects the segments into the bid request. You will find it in the console under Modules, with tabs for Overview, Install, Configure, and Test mode, plus full docs.
Module at a glance
| Property | Value |
|---|---|
| Version | v1.0, stable. |
| Module type | Real-Time Data (RTD). |
| Auction impact | Pre-bid: enrichment is attached before bids are requested. |
| Data sent to API | URL path and domain only. |
| Default timeout | 300 ms, configurable. |
| Cache | sessionStorage, 1 hour TTL. |
| Taxonomies injected | StackUp content (segtax 502), IAB Audience (segtax 4), legacy StackUp audience (segtax 501). |
How it works
Resolve and fetch. On page load, init() resolves the article ID from the page URL path (or an explicit CMS slug) and kicks off a background fetch to GET /v1/enrich-ortb-rtd.
Cache. The response is cached in sessionStorage, so subsequent auctions within the same session cost roughly 0 ms.
Merge. When getBidRequestData() fires, the enrichment is merged non-destructively into ortb2Fragments.global. Every bidder in the auction receives the segments, and nothing already in your ortb2 setup is overwritten.
Fail open. If the API has not responded within params.timeout ms, the auction is released clean. The module never blocks the auction indefinitely.
Privacy by design
Getting started
Open Modules › Prebid.js RTD in the console and follow the Install and Configure tabs for your Prebid build. Use Test mode to validate the integration before going live: it lets you confirm segments are resolving and merging for your pages without affecting production auctions. You will need scanned content from Prism for enrichment to resolve.