Knowledge Base

Magnite SSP Connector — Attributes & How-To

Supported identifiers

The connector accepts the following identifiers in audience membership files:

  • mobile_id_unique_identifier
  • android_advertising_id
  • apple_idfa
  • ip_address
  • narrative_id with context of:
    • mobile_id_unique_identifier
    • adid
    • idfa
    • ip_address

Normalization and hashing are handled upstream via Rosetta Stone.

Audience identifier TTL

  • Membership TTL is applied according to Magnite’s audience expectations and the connector’s delivery cadence.
  • Practically, your dataset refresh schedule governs how often updates are published; ensure it reflects how long memberships should remain active.

Connection behavior

  • Delivery aligns to your materialized view refresh cadence.
  • “Deliver all data” (historical backfill) vs “new rows only” is controlled via the historical_data_enabled quick‑setting.
  • The connector creates or updates a taxonomy element at connect time and updates it on subsequent runs.

Best practices

  • Keep your audience materialized view focused on the identifiers you intend to deliver.
  • Choose clear audience names; use descriptions to document purpose and targeting context.

Magnite — Introduction

Business value and when to use the Magnite connector.

Read the intro
< Back
Rosetta

Hi! I’m Rosetta, your big data assistant. Ask me anything! If you want to talk to one of our wonderful human team members, let me know! I can schedule a call for you.