Pinterest Connector

The Pinterest Connector delivers audience data to Pinterest, enabling you to create custom audiences for advertising campaigns on the Pinterest platform.

Overview

The connector pushes your audience data to Pinterest, where it becomes available as a Custom Audience for targeting in your Pinterest ad campaigns. You can connect multiple Pinterest profiles, manage ad accounts, and invite third-party partners to connect their accounts using app invites.

Guides

Requirements

Account access

• A Pinterest Business account
• Access to Pinterest Ads Manager
• Appropriate permissions to create Custom Audiences

Supported identifiers

Your data must include at least one of these identifier types, mapped to the corresponding Rosetta Stone attribute: The connector also accepts the generic mobile_id_unique_identifier attribute when its type resolves to one of the identifiers above.

Delivering audiences

When configuring a connection to deliver data through the Pinterest Connector, you provide:

API connection settings

A connection’s quick_settings pick the interface and set how the connection delivers. The fields depend on the interface.

New audience (audience_first_party_new)

The connector creates a customer list and an audience on it in Pinterest when you create the connection.

Existing audience (audience_first_party_existing)

The connection keeps the write_mode it was created with.

Existing and new rows

A connection delivers every snapshot written to the dataset after the connection is created. The historical_data_enabled quick setting decides whether the connection also delivers data that was already in the dataset when you created it:

• With historical_data_enabled set to true, the connection first delivers data already in the dataset, then keeps delivering new snapshots as they land.
• With historical_data_enabled set to false, the connection delivers only snapshots written after it was created.

How far back the first delivery reaches depends on the connector, and each connector’s guide states it. For Pinterest, historical_data_enabled delivers the dataset’s snapshots from the 30 days before the connection was created, as one delivery. After that, each new snapshot is delivered as it lands. What an audience delivery does depends on write_mode:

• append uploads the delivery’s members into the audience’s customer list. Members stay in the list.
• overwrite uploads the delivery’s members into a new customer list named <audience name> - <yyyy-mm-dd>. Once Pinterest marks the new list ready, the audience switches to it, so the audience holds only the members of the latest delivery. Earlier customer lists stay in the ad account.

An overwrite connection replaces the audience with each snapshot, so pair it with a dataset whose own write_mode is overwrite. Each snapshot of that dataset holds the full audience.

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). The connector does not set an expiration on delivered identifiers — Pinterest’s customer list API has no membership duration parameter.

Inviting partners

The Pinterest Connector supports app invites, which let you onboard third-party partners without requiring them to have a Narrative account. In the App Invites tab, you can generate shareable invitation links that allow partners to connect their Pinterest accounts directly. Each invite includes a unique URL and code. When a partner opens the link and authorizes their Pinterest account, a profile is automatically created in your Narrative account.

Reconnect invites

You can also create app invites that allow a partner to refresh the OAuth token on an existing profile. When creating an invite, select Update existing profile token and choose the profile to reconnect. The partner receives a link that walks them through the same OAuth flow, updating the token on the existing profile rather than creating a new one. For more details on how app invites work, see App Invites.

---

Related content