# Pinterest Conversions Destination

## About this integration

Pinterest 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 Pinterest to see how well your campaigns perform and optimize them over time—all without installing the Pinterest Tag.

[Mode How we forward source data to the destination: through Customer.io's servers or directly from our JavaScript client.](/cdp/destinations/getting-started/#connection-mode)

[Web sources Indicates whether or not this integration supports our the JavaScript client.](/cdp/sources/getting-started/#types-of-sources)

[API sources Indicates whether or not this integration supports our server libraries (Go, NodeJS, Python), API, Mobile SDK, and other data sources.](/cdp/sources/getting-started/#types-of-sources)

[Supported calls The API methods this integration supports.](/cdp/sources/source-spec/source-events/)

[Integration name The name of this integration if you want to enable or disable it in the `integrations` object.](/cdp/sources/source-spec/common-fields/#the-integrations-object)

Standard

N/A

Pinterest Conversions API

## Getting started[](#getting-started)

1.  Go to **[Data & Integrations > Integrations](https://fly.customer.io/workspaces/last/journeys/integrations/all/directory)** and select the **Pinterest Conversions** entry in the *Directory* tab.
    
2.  (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.
    
3.  Configure your integration.
    
    1.  **Ad Account Id**: Unique identifier of an ad account. This can be found in the Pinterest UI by following the steps mentioned [here](https://developers.pinterest.com/docs/conversions/conversions/#Find%20your%20%2Cad_account_id).
        
    2.  **Conversion Token**: The conversion token for your Pinterest account. This can be found in the Pinterest UI by following the steps mentioned [here](https://developers.pinterest.com/docs/conversions/conversions/#Get%20the%20conversion%20token).
        
4.  Click **Enable Destination**.
    

## Actions[](#actions)

When you’re done setting things up, you can go to the *Actions* tab to see how we map incoming data to your integration.

You may need to add actions for this integration

While we often have default triggers for actions, we don't always add those actions as defaults. You may need to add actions to make sure that you're sending all the data that you want to send to your integration. See our [actions](/integrations/data-out/actions/) page for help setting up actions.

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[](#deduplication-with-pinterest-tag)

Pinterest doesn’t know if conversions 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 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:

1.  Events have non-empty and non-null values for `event_id` and `event_name`
2.  The `action_source` for events is not `offline` (for example, events that occurred in the physical world, like in a local store) where the `action_source` parameter is one of – `app_android`, `app_ios`, `web`, or `offline`.
3.  The duplicate events arrive within 24 hours of initial, unique events.

## Limited Data Processing[](#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”

### Hashing Personally Identifiable Information (PII)[](#hashing-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
*   Email
*   Phone
*   Gender
*   Date of Birth
*   Last Name
*   First Name
*   City
*   State
*   Zip Code
*   Country

### User Data Parameters[](#user-data-parameters)

We automatically map user data fields to their corresponding Pinterest parameters [as expected by the Conversions API](https://developers.pinterest.com/docs/conversions/best/#Authenticating%20for%20the%20Conversion%20Tracking%20endpoint#The%20%2Cuser_data%2C%20and%20%2Ccustom_data%2C%20objects#Required%2C%20recommended%2C%20and%20optional%20fields#Required%2C%20recommended%2C%20and%20optional%20fields#User_data%2C%20and%20%2Ccustom_data%2C%20objects).

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`

Email

`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[](#custom-data-parameters)

We automatically map custom data fields to their corresponding parameters [as expected by the Pinterest’s Conversions API](https://developers.pinterest.com/docs/conversions/best/#Authenticating%20for%20the%20Conversion%20Tracking%20endpoint#The%20%2Cuser_data%2C%20and%20%2Ccustom_data%2C%20objects#Required%2C%20recommended%2C%20and%20optional%20fields#Required%2C%20recommended%2C%20and%20optional%20fields#User_data%2C%20and%20%2Ccustom_data%2C%20objects).

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[](#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`.