Curated Audiences (SDA)
Introduction
To learn more about the Curated Audiences feed capability and the steps for configuring this feature, please refer to the user guide.
How to retrieve segment mapping
Once you have configured and activated the segment mapping in Navigator, mapping for matched segments will be available in the browser's local storage under the mics_sda key.
The mics_sda key will have the following structure:
{
"last_modified_ts": <LAST_MODIFIED_TS>,
"data": [{
"name": "<PROVIDER_NAME>",
"ext": {
"segtax": <TAXONOMY_ID>
},
"segment": [
{ "id": "<SEGMENT_ID_1>" },
{ "id": "<SEGMENT_ID_2>" }
]
}]
}How to use Curated Audiences mapping in bid request
In that section, we will provide an example for using your Curated Audiences mapping in bid request using prebid.js:
// Retrieve Curated Audiences mapping
mics_sda_data = JSON.parse(localStorage.getItem("mics_sda"))['data'];
// Use this mapping in the bid request
pbjs.mergeConfig({
ortb2: {
user: {
data: mics_sda_data
}
}
})Handling Multiple Providers and Taxonomies
If a user matches multiple segments across various Curated Audiences feeds:
For identical
provider_name&taxonomy_id: all matchedsegment_idswill be added in thesegmentarray for the respectiveprovider_nameandtaxonomy_idFor different
provider_nameortaxonomy_idcombinations: Each unique combination will generate a separatedataobject.
For instance, if a user matches:
Segments 12 & 34 with
Provider_name = mics.ioandTaxonomy = 3Segments 56 & 78 with
Provider_name = mics.ioandTaxonomy = 4Segment 90 with
Provider_name = mics.comandTaxonomy = 3
The content of mics_sda would be:
{
"last_modified_ts": 1737147480000,
"data": [{
"name": "mics.io",
"ext": { "segtax": 3 },
"segment": [
{ "id": "12" },
{ "id": "34" }
]
},
{
"name": "mics.io",
"ext": { "segtax": 4 },
"segment": [
{ "id": "56" },
{ "id": "78" }
]
},
{
"name": "mics.com",
"ext": { "segtax": 3 },
"segment": [
{ "id": "90" }
]
}]
}Last updated
Was this helpful?