Overview
The connector routes conversion data — checkouts, signups, leads, page visits, and more — from any dataset in Narrative to a Pinterest ad account. Events are matched against Pinterest user accounts using hashed customer information. This connector supports:- Web conversions (e.g., website purchases, page visits)
- App conversions (Android and iOS)
- Offline conversions (e.g., in-store purchases)
Guides
Sending Conversion Events to Pinterest
Connect a dataset of conversion events
Setting Up API Access for Pinterest
Prerequisites, API keys, and profiles for the API guides
Sending Conversion Events to Pinterest via the API
Send conversion events with an API key
Prerequisites
- A Pinterest Business account with access to Pinterest Ads Manager and the ad account you want to deliver events to.
- A Narrative dataset containing the conversion data you want to send.
The pinterest_conversion_event attribute
The pinterest_conversion_event attribute is Narrative’s standardized Rosetta Stone schema for conversion events sent to Pinterest. When you map your dataset columns to this attribute, Narrative handles transformation, hashing, batching, and delivery to Pinterest’s API.
Top-level fields
Custom data fields
Additional event data used by Pinterest for attribution and reporting.Supported user identifiers
In addition to thepinterest_conversion_event attribute, your dataset must include at least one of the following Rosetta Stone identifier attributes. Pinterest uses these to match conversion events to user accounts. All PII values are SHA-256 hashed by Narrative before transmission.
Pinterest requires every event to carry at least one of: a hashed email, a hashed mobile advertising ID, or the IP address + user agent pair. Other identifiers improve match quality but do not satisfy Pinterest’s minimum on their own, so make sure your dataset includes at least one of the three.
Match enrichment attributes
These optional attributes improve Pinterest’s match quality when included alongside a supported identifier:Only email, phone, and mobile ad ID attributes accept pre-hashed values. Name, address, and demographic attributes must be provided raw — Narrative normalizes and hashes them to Pinterest’s specification, so pre-hashed values in those fields will not match.
Reference
Event names
Theevent_name field accepts the following values.
Action sources
Deduplication
Pinterest deduplicates events byevent_id within a 48-hour window. If you send the same events through both a Pinterest conversion tag (pixel) and the Conversions API, use the same event_id in both so Pinterest removes the duplicates before reporting. Offline events are excluded from tag/API deduplication.
Batching
Events are delivered in batches of up to 1,000 per API call. Narrative validates each event against Pinterest’s field constraints before delivery, so a single invalid row does not block the rest of the batch.API connection settings
A connection’squick_settings pick the interface and set how the connection delivers. The fields depend on the interface.
Conversion events (conversion_events)
Each event names its ad account in
pinterest_ad_account_id, so the connection has no ad account setting. The connection sends events up to 7 days old.
Existing and new rows
A connection delivers every snapshot written to the dataset after the connection is created. Thehistorical_data_enabled quick setting decides whether the connection also delivers data that was already in the dataset when you created it:
- With
historical_data_enabledset totrue, the connection first delivers data already in the dataset, then keeps delivering new snapshots as they land. - With
historical_data_enabledset tofalse, the connection delivers only snapshots written after it was created.
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.
A conversion connection sends each event in each snapshot it delivers. Uploading the same events again in a new snapshot sends them again.
Data privacy
Narrative normalizes and hashes all customer information fields (email, phone, name, address, birth date, gender) using SHA-256 before transmission, following Pinterest’s normalization rules for each field. Raw PII is never sent to Pinterest. IP address, user agent, click ID, and partner ID are passed through unhashed, as Pinterest requires.Related content
Pinterest Connector
Deliver custom audiences to Pinterest for ad targeting
Meta Conversions API Connector
Send conversion events to Meta
Data Activation Overview
Understand how connectors deliver data
Hashing PII
Prepare identifiers for delivery

