Connectors

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

​

AI/ML

​

Cloud storage

---

​

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. A few connectors work differently:

---

​

Audience membership duration

Membership duration is how long a delivered identifier remains active in the destination audience before the destination platform expires it. It is distinct from the dataset’s retention policy (which governs data stored in Narrative) and the interface’s refresh window (which governs how stale the source dataset may get). Each audience destination handles membership duration differently. Per audience means the duration is set once when the audience is created and never updated afterward; per record means the duration is sent with every delivered identifier, so each delivery renews the clock. See each connector’s Audience membership duration section for details. Conversions API interfaces deliver events rather than audience memberships, so membership duration doesn’t apply to them; see each Conversions API page for its event age limits. Amazon S3 and Hugging Face deliver files and models, so nothing expires.

---

​

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