Pinterest

Pinterest

Pinterest Conversions API v5 with epik cookie propagation and server-side event delivery through TrackLayer.

Pinterest is straightforward once the ad account, token, and browser identifiers are aligned. This guide walks through the minimum setup required to get a verified event into Pinterest Conversions Diagnostics without adding a separate Pinterest-specific payload path to your app.

Setup

1. Open your Pinterest ad account and collect the Ad Account ID for the destination account. Then generate a Conversion Access Token for the same account. Make sure the user or business that created the token still has access to the ad account.

2. In TrackLayer, open Platforms and connect Pinterest. Enter the Ad Account ID and Conversion Access Token exactly as provided. Save the platform and fix any credential validation issues before sending test traffic.

3. Fire a test event from a real browser session. PageVisit, AddToCart, Checkout, or Purchase all work for validation. Use a session that came through a Pinterest ad click when possible so the browser already contains Pinterest identifiers.

4. Open Conversions Diagnostics in Pinterest and verify that the event arrives through the Conversions API path. Check for any warnings around missing fields, invalid event names, or weak match quality.

5. Once the event validates cleanly, decide whether you still need the browser pixel in parallel. If you do, keep a stable event identifier strategy so Pinterest can reconcile browser and server signals. If not, remove the redundant client-only path after testing.

How the event flows

Browser / app
  -> TrackLayer /ingest
  -> normalize + attach epik and user data
  -> server-side Pinterest CAPI v5 request
  -> Pinterest

TrackLayer receives the event in the same normalized schema used for other platforms, then translates it into Pinterest's Conversions API request format. That keeps the application-side integration simple even when Pinterest changes field requirements or endpoint versions.

What we handle for you

TrackLayer covers the operational work that usually gets scattered across frontend and backend code:

• propagation of epik and related browser context when it is available during the session
• stable event identifier handling so duplicate client and server signals do not inflate counts
• payload shaping for Pinterest Conversions API v5
• endpoint and version maintenance so platform updates do not force an immediate code change in your store

That means your job is to send correct source data once. TrackLayer handles the Pinterest-specific delivery path after that.

Data to send

Pinterest performs better when the original browser context survives through checkout. Preserve the epik cookie and any landing-page click context across redirects and domain changes. If checkout runs on a different subdomain or external host, make sure the identifiers still reach TrackLayer with the final conversion event.

For purchase flows, include a stable order ID, value, and currency. For lead or signup flows, send the event time and any normalized user data you already collect, such as email or phone. Do not invent identifiers that were not present at the time of the event; Pinterest will accept a lean payload, but diagnostics and attribution quality will be weaker.

If you run both browser and server delivery, use one event identity strategy. The common failure mode is sending an uncoordinated browser event and a second server event with no shared dedup key, which makes diagnostics harder to interpret.

Troubleshooting

No events in Conversions Diagnostics

First verify the Ad Account ID in TrackLayer matches the account you are inspecting in Pinterest. Then confirm the Conversion Access Token is still valid. If both are correct, check whether the source event reached TrackLayer before debugging Pinterest.

Low match quality

The usual cause is missing epik, missing user identifiers, or loss of browser context between the landing page and the conversion event. Review redirects, subdomain boundaries, and any checkout handoff that may be dropping Pinterest identifiers.

Diagnostics warnings on test traffic

Pinterest often accepts the event while still warning about incomplete fields. Read the warning literally. If it mentions missing value, currency, order ID, or user data, improve the source event instead of retrying the same incomplete payload.

Once Diagnostics looks clean, watch acceptance rate and match quality over your first day of live traffic before retiring any previous Pinterest event path.

-> Back to all platforms