> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/curated-audiences-sda.md).

# Curated Audiences (SDA)

Expose standardised taxonomy segment IDs in the browser, for any bidding partner on your site to read.

The Curated Audiences (SDA) connector lets publishers define and share audience segments built on first-party data, contextual signals or other transparent sources. It uses standardised taxonomies, so the segments are consistent and interoperable across the partners integrated on your site.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Client-side (local storage)</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/data-sharing-and-export.md">Data sharing &#x26; export</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>None - taxonomy segment IDs only, kept in the browser</td></tr><tr><td><strong>Authentication</strong></td><td>None</td></tr></tbody></table>

## Description

### What this connector does

It writes segment IDs that **you** define into the visitor's browser local storage, under the fixed key `mics_sda`, in a structure any partner integrated on your website can read. The segment IDs are expressed against a standardised taxonomy rather than as free text.

### What you can do with this connector

* Share audience signals with bidding partners without sharing any personal identifier.
* Express your audiences against a taxonomy your partners already understand, such as the IAB Tech Lab Audience Taxonomy.
* Serve every partner on the page from a single local storage key.

### Which identifiers are sent

**No personal identifiers are shared.** The connector provides the **Segment IDs** you define, stored in the browser's local storage and readable by any partner integrated on your website.

## Connector setup

### Prerequisites

* The mediarithmics tag installed on the site, calling `syncFeeds` - the call that enables client-side feeds. See the **Setup & Monitor** section, under *Collect & manage your data › Collect data in real time › Web tracking*.
* A taxonomy chosen, and the segment IDs within it that describe your audience. The standardised taxonomies are maintained in the [IAB Tech Lab community extension repository](https://github.com/InteractiveAdvertisingBureau/openrtb/blob/main/extensions/community_extensions/segtax.md) - taxonomy ID `4`, for instance, is the [IAB Tech Lab Audience Taxonomy 1.1](https://iabtechlab.com/standards/audience-taxonomy/).

### Setup steps

{% stepper %}
{% step %}
**Create the Curated Audiences (SDA) feed on a segment.**
{% endstep %}

{% step %}
**Fill in the configuration.**

All four fields are mandatory.

<table data-search="false"><thead><tr><th width="220">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>A name for the feed, shown on the segment dashboard page.</td></tr><tr><td><strong>Provider Name</strong></td><td>The unique domain of the entity determining the attribute or cohort - your website's domain, or your parent group's.</td></tr><tr><td><strong>Taxonomy ID</strong></td><td>The identifier of the taxonomy range the segment IDs belong to.</td></tr><tr><td><strong>Segment IDs</strong></td><td>The IDs representing your internal segmentation. If your audience maps to several taxonomy entries, list them comma-separated, for example <code>123,456</code>.</td></tr></tbody></table>
{% endstep %}

{% step %}
**Activate the feed.**
{% endstep %}

{% step %}
**Read the mapping from local storage and pass it to your activation platform.**

See [Retrieve the segment mapping](#retrieve-the-segment-mapping) and [Use the mapping with Prebid](#use-the-mapping-with-prebid).
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## Retrieve the segment mapping

Once the feed is configured and activated, the mapping for matched segments is available in the browser's local storage under the `mics_sda` key, with this structure:

```javascript
{
    "last_modified_ts": <LAST_MODIFIED_TS>,
    "data": [{
        "name": "<PROVIDER_NAME>",
        "ext": {
            "segtax": <TAXONOMY_ID>
        },
        "segment": [
            { "id": "<SEGMENT_ID_1>" },
            { "id": "<SEGMENT_ID_2>" }
        ]
    }]
}
```

### Use the mapping with Prebid

An example of putting the mapping into a bid request with [Prebid.js](https://docs.prebid.org/prebid/prebidjs.html):

```javascript
// 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
      }
   }
})
```

## Good to know

### Several providers and taxonomies at once

If a user matches segments across several Curated Audiences feeds:

* **Same `provider_name` and `taxonomy_id`** - all matched segment IDs are added to the `segment` array of that one entry.
* **Different `provider_name` or `taxonomy_id`** - each unique combination produces its own `data` object.

For a user matching segments 12 and 34 with provider `mics.io` and taxonomy `3`, segments 56 and 78 with provider `mics.io` and taxonomy `4`, and segment 90 with provider `mics.com` and taxonomy `3`, `mics_sda` holds:

```json
{
    "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" }
        ]
    }]
}
```

## FAQ

#### Does this connector share personal data?

No. It shares only the segment IDs you define, and they stay in the visitor's browser until a partner on your page reads them.

#### Which key holds the mapping?

`mics_sda`. Unlike the [Browser Local Storage](/connectors/destinations/browser-local-storage.md) connector, the key is not configurable.

#### Where do the taxonomy IDs come from?

From the IAB Tech Lab community extension repository. They are not mediarithmics values.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Browser Local Storage</strong></td><td>The other local-storage connector, with a configurable key and free-text segment names.</td><td><a href="/connectors/destinations/browser-local-storage.md">Browser Local Storage</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/connectors/destinations/curated-audiences-sda.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.