Skip to main content
Connectors enable you to deliver data from Narrative to external platforms. Each connector is a pre-built integration that handles authentication, data formatting, and delivery to a specific destination.

​
Available connectors

​
Advertising platforms

The Trade Desk

Deliver audiences to TTD’s first-party or third-party marketplace with automatic UID2 generation

Meta Custom Audiences

Push custom audiences to Facebook and Instagram advertising

Meta Conversions API

Send conversion events for ad attribution and campaign optimization

Google Ads

Deliver Customer Match audiences to Google Ads

Google DV360

Activate audiences in Google Display & Video 360

TikTok

Deliver custom audiences to TikTok Ads Manager

Snapchat

Deliver custom audiences to Snapchat Ads Manager

Yahoo DSP

Activate audiences in Yahoo’s demand-side platform

Pinterest

Deliver custom audiences to Pinterest for ad targeting

Magnite

Deliver audience segments to Magnite’s SSP

PubMatic

Deliver audience segments to PubMatic for programmatic advertising

​
AI/ML

Hugging Face

Export trained AI models to Hugging Face Hub

​
Cloud storage

Amazon S3

Deliver data files to your Amazon S3 bucket

​
Connector interfaces

A connector is installed as an app (identified by an app_id). Each app exposes one or more interfaces (each identified by an interface_id); a dataset connects to a specific (app_id, interface_id) pair, not to the connector as a whole. Some connectors appear more than once in Available connectors above because a single app exposes several interfaces — Meta Custom Audiences and Meta Conversions API are two interfaces of one installed Meta app, each with its own collaboration policy. Each interface defines: Before creating a connection, check which interfaces accept a dataset’s schema; an accepted (app_id, interface_id) pair is one a connection will succeed against. See Connector Interfaces for the concept and the connection creation flow for the API calls.

​
Connector requirements

Most connectors match users on identifiers, enforced by the interface’s collaboration policy. The requirements are listed on each connector’s own page under Supported identifiers — open a connector from Available connectors above for its exact table. Three connectors work differently:
For identifier formatting requirements, see Hashing PII for Upload.
Connectors cannot be attached to view datasets. If you need to deliver query results to an external platform, use a materialized view instead.

​
Common workflows

​
Delivering first-party data

Push your own customer data to platforms for targeting:
  1. Prepare your data with hashed identifiers
  2. Upload to a dataset
  3. Map to Rosetta Stone attributes
  4. Configure and deliver through the connector

​
Delivering acquired data

Activate third-party data purchased through Narrative:
  1. Query data from data collaborators using NQL
  2. Materialize results into a dataset
  3. Deliver through the appropriate connector

​
Related content

Data Activation Overview

Understand how connectors fit into the activation workflow

Structuring Audiences

Organize your data for efficient delivery

Rosetta Stone Mapping

Map your schema for connector compatibility

Schema Incompatibility Errors

Resolve HTTP 400 errors when a dataset schema doesn’t match a connector