Pinterest Conversions Destination
UpdatedAbout this integration
Pintrest lets you create campaigns encouraging people to take actions on your website with checkout, signup, lead, or addtocart events. This integration lets you track and send conversion events to Pintrest to see how well your campaigns perform and optimize them over time—all without installing the Pintrest Tag.
Getting started
Go to the Data Pipelines tab and click Connections.
Click Add New under Destinations.
Select the Pinterest Conversions destination.
(Optional) Select the sources that you want to connect to this destination. You can always connect sources to your destination later. We’ll only show you eligible sources.
Configure your destination.
Ad Account Id: Unique identifier of an ad account. This can be found in the Pinterest UI by following the steps mentioned here.
Conversion Token: The conversion token for your Pinterest account. This can be found in the Pinterest UI by following the steps mentioned here.
Click Enable Destination.
Actions
When you’re done setting up your destination, you can go to the Actions tab to see how we map source events to your destination.
| Action | Default Trigger | Description |
|---|---|---|
| Report Conversion Event | Report events directly to Pinterest. Data shared can power Pinterest solutions that will help evaluate ads effectiveness and improve content, targeting, and placement of future ads. |
Deduplication with Pinterest Tag
Pinterest doesn’t know if aonversions reported by the Pinterest Tag and conversions reported by the API are the same. Because Pinterest recommends using both the API for Conversions and the Pinterest Tag, they automatically deduplicate events to avoid double-counting of events sent through multiple sources.
For example, imagine that a user triggers an add to cart event and the tag reports the data using 123 as the event ID, and your web server later reports the conversion to the API, also using 123 as the event ID. They’ll look at the event IDs to confirm they correspond to the same event. If they do, Pinterest won’t count the conversion twice, which helps you report conversions using both the tag and the API without having to worry about over-counting conversions.
You should use deduplication for any events they expect to be reported by multiple sources across the API and the Pinterest Tag.
Conversion Events must meet the following requirements to be deduped:
- Events have non-empty and non-null values for
event_idandevent_name - The
action_sourcefor events is notoffline(for example, events that occurred in the physical world, like in a local store) where theaction_sourceparameter is one of –app_android,app_ios,web, oroffline. - The duplicate events arrive within 24 hours of initial, unique events.
Limited Data Processing
Starting from Jan 1, 2023, Pinterest introduced the Limited Data Processing setting per the California Consumer Privacy Act (CCPA). This flag helps you comply with CCPA.
You’re responsible for complying with user opt-outs, as well as identifying the user’s state of residency when you implement the Limited Data Processing setting.
This setting can impact campaign performance and targeting use cases. Pinterest recommends that you use the Limited Data Processing setting on a per-user basis for best results.
LDP relies on 3 fields and is enabled only when all 3 combinations are met, if one of them is not met then LDP is disabled / ignored.
| Field Name | Field Description | Required Value for LDP |
|---|---|---|
opt_out_type | Opt Out Type based on User’s privacy preference | “LDP” |
st | State of Residence | “CA” |
country | Country of Residence | “US” |
Hasing Personally Identifiable Information (PII)
We create a SHA-256 hash of the following fields before we send them to Pinterest. This ensures that your user data is stored safely in Pinterest.
- External ID
- Mobile Ad Identifier
- Phone
- Gender
- Date of Birth
- Last Name
- First Name
- City
- State
- Zip Code
- Country
User Data Parameters
We automatically map user data fields to their corresponding Pinterest parameters as expected by the Conversions API.
| User Data Field | Conversions API User Data Parameter |
|---|---|
| External ID | external_id |
| Mobile Ad Id | hashed_maids |
| Client IP Address | client_ip_address |
| Client User Agent | client_user_agent |
em | |
| Phone | ph |
| Gender | ge |
| Date of Birth | db |
| Last Name | ln |
| First Name | fn |
| City | ct |
| State | st |
| Zip Code | zp |
| Country | country |
Custom Data Parameters
We automatically map custom data fields to their corresponding parameters as expected by the Pinterest’s Conversions API.
| User Data Field | Conversions API Custom Data Parameter |
|---|---|
| Currency | currency |
| Value | value |
| Content IDs | content_ids |
| Contents | contents |
| Number of Items | num_items |
| Order ID | order_id |
| Search String | search_string |
| Opt Out Type | opt_out_type |
Server Event Parameter Requirements
Pinterest requires the action_source server event parameter for all events sent to the Pinterest Conversions API. This parameter specifies where the conversions occur and is one of app_android, app_ios, web, or offline.
