This Real-Time Data (RTD) submodule reads Agentic Audiences embedding data from browser storage (localStorage or cookies) and merges it into the outbound bid request as OpenRTB user.data entries. It follows the community extension Agentic Audiences in OpenRTB (see IAB Tech Lab — Agentic Audiences and the reference repository).
You can configure multiple providers under a single module: each key in params.providers becomes the name on one Data object in user.data, with segments built from that provider’s stored payload. No separate Prebid module is required per vendor—only this submodule plus the correct storageKey for wherever each partner’s script writes data.
Build the module into your Prebid.js bundle. The parent rtdModule is required. You may list both explicitly, or rely on agenticAudienceAdapter being registered as an RTD submodule so builds that include only agenticAudienceAdapter still pull in rtdModule:
gulp build --modules=rtdModule,agenticAudienceAdapter,...
Register the data provider with pbjs.setConfig({ realTimeData: ... }) as shown below.
pbjs.setConfig({
realTimeData: {
auctionDelay: 300,
dataProviders: [{
name: 'agenticAudience',
waitForIt: true,
params: {
providers: {
partner_a: { storageKey: '_example_agentic_audiences_a_' },
partner_b: { storageKey: '_example_agentic_audiences_b_' }
}
}
}]
}
});
The realTimeData.dataProviders[] entry for this submodule uses name: 'agenticAudience' (the RTD submodule name). Other fields such as auctionDelay and waitForIt are generic RTD behavior; see Publisher Real-Time Data Configuration.
params| Parameter | Type | Description |
|---|---|---|
providers |
object | Required for initialization. Map from a provider label (string) to per-provider settings. The object key becomes user.data[].name in the bid request. If providers is missing, not a plain object, or has no enumerable keys, the submodule does not inject data. |
providers.<label>.storageKey |
string | Key used for localStorage; if absent there, the cookie API is tried. If missing or falsy for a given label, that provider is skipped (no user.data row for it). |
Provider labels are chosen by the publisher (or by convention with a data partner). The module does not whitelist names.
The value at each storageKey is expected to be Base64-encoded JSON (as produced by the Agentic Audiences client storage format). After atob and JSON.parse, the payload should include an entries array. Each entry is mapped to one OpenRTB Segment with standard id and name where present, and Agentic Audiences fields placed under segment.ext (ver, vector, dimension, model, type) as defined in the OpenRTB extension. The module does not validate or re-encode vectors; consumers should follow the extension for decoding (Float32 little-endian per value, Base64).
For each configured provider that yields at least one mappable segment, the submodule appends one element to user.data, in the order of Object.keys(params.providers) (typical object insertion order). Structure matches the extension’s single- and multi-provider examples: one Data object per provider with name and segment[], and embedding metadata in each segment’s ext.
The submodule reads first-party storage. It is registered with Prebid’s vendorless GVL handling so that, when TCF control is used, enforcement aligns with other publisher-scoped storage modules (publisher purpose consent rather than a specific advertising vendor). See the FAQ on vendorless GVL for context.
From the Prebid.js repository:
npm test -- --file test/spec/modules/agenticAudienceAdapter_spec.js
| [Agentic Audiences | IAB Tech Lab](https://iabtechlab.com/standards/agentic-audiences/) |