> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/pinterest.md).

# Pinterest

Send offline hashed data to Pinterest Ads and build Custom Audiences.

The Pinterest connector sends offline hashed data from mediarithmics to Pinterest Ads and creates Custom Audiences. Being server-side, it pushes the audience every time the segment is updated.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/social-and-retail-media.md">Social &#x26; retail media</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Email hash (SHA-256), Mobile IDs, Phone number hashes</td></tr><tr><td><strong>Authentication</strong></td><td>Refresh token generated in Pinterest, passed to your account manager</td></tr></tbody></table>

## Description

### What you can do with this connector

* Build a Pinterest Custom Audience from a mediarithmics segment.
* Enrich a Pinterest audience that already exists.
* Set how long Pinterest retains the audience.

### Which identifiers are sent

* **Email hash (SHA-256)**
* **Mobile IDs**
* **Phone number hashes**

{% hint style="info" %}
For SHA-256, use lowercase characters and strip any extra spaces before, after or between the email addresses.
{% endhint %}

{% hint style="warning" %}
**One identifier and one compartment ID per feed.**
{% endhint %}

## Connector setup

### Prerequisites

* A Pinterest Ads account, and its account ID.
* A **refresh token** generated in Pinterest.

### Authentication

Generate a refresh token in Pinterest and pass it to your mediarithmics account manager.

{% hint style="danger" %}
**The authorisation code is valid for 15 minutes only.** Schedule a call with your mediarithmics account manager and your Pinterest admin so the exchange happens in one sitting.
{% endhint %}

### Setup steps

{% stepper %}
{% step %}
**Set up a call with your account manager and your Pinterest admin, and generate the refresh token.**

The code expires in 15 minutes, so do this together.
{% endstep %}

{% step %}
**Select the Pinterest connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="300">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies the feed within Navigator.</td></tr><tr><td><strong>Pinterest account ID</strong></td><td>The account to send data to. Used to fetch its credentials.</td></tr><tr><td><strong>Identifying Resources</strong></td><td>See below.</td></tr><tr><td><strong>Audience Name</strong> <em>(optional)</em></td><td>The name of the audience generated in Pinterest Ads. Defaults to the mediarithmics segment name.</td></tr><tr><td><strong>Audience description</strong></td><td>Fill this in to enrich an existing Pinterest Ads audience. Left empty, the segment description is used, or the segment name.</td></tr></tbody></table>

The identifying resources available:

<table data-search="false"><thead><tr><th width="300">Resource</th><th></th></tr></thead><tbody><tr><td><code>USER_EMAIL</code></td><td>Emails from UserEmail - global identifiers.</td></tr><tr><td><code>USER_PROFILE</code></td><td>Emails and/or phone numbers from UserProfile data, depending on the datamart configuration file. Only the selected compartments are used.</td></tr><tr><td><code>MOBILE_ADVERTISING_ID</code></td><td>GAID and IDFA from registries 2 and 3. Only the selected registries are used, and IDFAs cannot be distinguished from GAIDs.</td></tr></tbody></table>
{% endstep %}

{% step %}
**Set the advanced fields if you need them.**

<table data-search="false"><thead><tr><th width="340">Field</th><th></th></tr></thead><tbody><tr><td><strong>Pinterest audience ID</strong></td><td>The ID of your audience list for the <strong>Customer list</strong> type. An existing value enriches that audience, and you then do not fill in the customer list ID.</td></tr><tr><td><strong>Pinterest audience related customer list ID</strong></td><td>The ID of the audience customer list in Pinterest, for the Customer list type. In this case the <strong>Pinterest audience ID is mandatory too</strong>.</td></tr><tr><td><strong>Retention in Days</strong> <em>(optional)</em></td><td>How long the audience is retained.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## FAQ

#### The authorisation failed. What went wrong?

Most likely the 15-minute window. The Pinterest authorisation code expires quickly - do the exchange with your account manager and your Pinterest admin on the same call.

#### Can I send two identifiers in one feed?

No. One identifier and one compartment ID per feed.

#### Can IDFAs and GAIDs be sent separately?

No. `MOBILE_ADVERTISING_ID` collects both from registries 2 and 3, and the connector makes no distinction between them.

## Partner documentation

Pinterest documents its own platform at <https://help.pinterest.com/en/business/topics/advertise>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/connectors/destinations/pinterest.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.