Developer
User guidesDeveloper websiteHelp centerLog in
  • Welcome!
  • Organisations structure
    • Datamart
    • Users and roles
  • User points
    • User identifiers
      • Networks IDs
        • Device-based Network IDs
          • Custom Device ID integration
          • ID5
          • First ID
        • User-based Network IDs
          • Custom User ID integration
          • UTIQ martechpass
      • Accounts
      • Emails
      • Device identifiers
    • User activities and events
    • Compartments
    • User profiles
    • User segments
    • Hyper point & Quarantine
  • Data model
    • Defining your schema
    • Computed fields
      • Concepts
      • Setup
      • Development
      • Examples
  • Data ingestion
    • Real time user tracking
      • Website tracking
      • Mobile apps tracking
      • Ads exposure tracking
      • AMP tracking
      • Conversions tracking
      • Email views and clicks
      • Tracking API
      • Event rules
      • Activity analyzers
    • Bulk processing
      • Imports
        • User activities import
        • User profiles import
        • User choices import
        • Segments import
      • Deletions
        • User identifiers deletion
        • Device points deletion
        • User points deletion
      • User identifiers association
      • Integration batch
    • Activities analytics
    • Data warehouse
      • Preliminary setup
        • BigQuery
      • Create data warehouse
  • Querying your data
    • OTQL queries
    • OTQL examples
    • GraphQL queries
    • UserPoint API
    • User activities
    • Activities analytics queries
      • API Quickstart
      • Dimensions and metrics
      • Use cases
    • Funnel API
  • Alerting
    • Alert configurations
  • Data visualisation
    • Quickstart
    • Dashboards
    • Sections and cards
    • Charts
    • Datasets and data sources
      • Using a data file data source
    • Transformations
    • Filters
    • Cookbook
    • Reference
  • Advanced usages
    • Audience segmentation
      • Audience features
      • Segment builders
      • Audience segment metrics
      • Audience segment feed
        • Building new feeds
        • Monitoring a feed
        • Curated Audiences (SDA)
      • Edge segments
      • Cohort-based Lookalike
    • Contextual targeting
      • Setup
      • Activation
        • Google Ad Manager
        • Xandr (through prebid.js)
      • API documentation
    • Exporting your data
      • Query Exports
      • Datamart replication
    • Data privacy compliance
      • User choices
      • Cleaning rules
      • Exercise of user rights
      • Cookies
    • Campaigns
    • Automations
      • Email routers
      • Email renderers
      • Opt-in provider
      • Custom action plugins
      • Usage limits for automations
    • Plugins
      • Concepts
      • Creation & Deployment
      • Coding your plugin
      • Manage existing plugins
      • Layouts
      • Presets
      • Monitoring
      • Throttling
      • Batching (for external feeds)
    • Platform monitoring
      • Resources usage
        • Dimensions and metrics
      • Collection volumes
        • Dimensions and metrics
      • Events ingestion monitoring
        • Dimensions and metrics
    • Data Clean Room
      • Bunker
      • Clean room
  • Resources
    • Tutorial: Data Ingestion
      • Your first events
        • Add the mediarithmics tag
          • Getting the tag
          • Adding the tag
        • Send events using the tag
          • Adding event properties
          • Finding the UserEvent type in your schema
          • Matching your schema
          • Standard events
      • Your first bulk imports
        • API basics
          • Authentication
          • Your first API call
        • Send documents using the API
          • Requirements
          • Sending documents
    • Using our API
      • Authentication
    • Tools & libraries
      • mics CLI
      • JS Tag
      • Plugin SDK
    • Data cubes
      • Creating a report
      • Reference
Powered by GitBook
On this page
  • Introduction
  • How to retrieve segment mapping
  • How to use Curated Audiences mapping in bid request
  • Handling Multiple Providers and Taxonomies

Was this helpful?

Export as PDF
  1. Advanced usages
  2. Audience segmentation
  3. Audience segment feed

Curated Audiences (SDA)

PreviousMonitoring a feedNextEdge segments

Last updated 21 days ago

Was this helpful?

Introduction

To learn more about the Curated Audiences feed capability and the steps for configuring this feature, please refer to the .

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

// 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 matched segment_ids will be added in the segment array for the respective provider_name and taxonomy_id

  • For different provider_name or taxonomy_id combinations: Each unique combination will generate a separate data object.

For instance, if a user matches:

  • Segments 12 & 34 with Provider_name = mics.io and Taxonomy = 3

  • Segments 56 & 78 with Provider_name = mics.io and Taxonomy = 4

  • Segment 90 with Provider_name = mics.com and Taxonomy = 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" }
        ]
    }]
}

In that section, we will provide an example for using your Curated Audiences mapping in bid request using :

user guide
prebid.js