Integrations
Pinterest Conversions API
Send Pinterest Ads conversions from the server through the Pinterest Conversions API, so they arrive even when the browser blocks the Pinterest Tag. Every event is assembled from the whole DataCops platform, so Pinterest receives clean, verified conversions, counted once. Paste a token, no code.
What it is
The Pinterest Conversions API is Pinterest's server-to-server way to report ad conversions, instead of relying only on the Pinterest Tag in the browser. DataCops sends each conversion from the server to your Pinterest ad account, with the epik click ID and the hashed details Pinterest uses to match it to the person who saw or clicked your Pin.Pinterest is one of eight ad platforms DataCops sends to: Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Reddit, Pinterest and X. Microsoft, Reddit and Pinterest connect with a key or token you paste in. Meta, Google Ads, TikTok, LinkedIn and X connect with a sign-in.
Sending from the server is only half of it. DataCops builds each Pinterest event from every part of the platform: first-party capture, the edge worker, the 400-day identity, IP intelligence, email verification, the fraud check and the consent check. Pinterest receives a checked record of a real conversion, not just a tag firing.
Why the Pinterest Tag loses sales
The Pinterest Tag runs in the browser, which is where tracking is weakest:
- It gets blocked. Ad blockers, Safari limits and rejected consent all stop it, so the conversion never reaches Pinterest.
- It arrives thin. When it fires, it often carries little Pinterest can tie to a real account.
- It counts bots. A browser tag fires for any visitor, so Pinterest can learn from conversions that were never real.
These are data problems. DataCops fixes the data before Pinterest ever sees the event.
How DataCops builds each event
A DataCops Pinterest event is assembled as the visitor moves through your site. Each part of the platform adds what it knows, so the event is complete and checked by the time a conversion happens.Here is what each part adds, in order:
- The Cloudflare Worker catches the epik. Pinterest adds an epik value to the link when someone clicks a Pin. It is caught by the optional DataCops Cloudflare Worker on your domain, not by the core DataCops pixel. Add the Worker if you want epik on your Pinterest events. Without it, events still go out and match on email, phone, IP and device.
- First-party capture keeps the visit. Page, device and visitor details are captured on your own domain, out of reach of most blockers.
- The 400-day durable identity attaches the person. If someone converts anonymously today but identified themselves earlier, DataCops attaches their email and a stable ID. Extra emails and phones the person gave you ride along too.
- IP intelligence supplies a clean IP. The same IP checked for fraud is the one sent to Pinterest.
- Email verification checks the match key. The email is checked before it becomes a hashed match key.
- Real people only can gate out fakes. Turn it on for Pinterest and bot and datacenter traffic is held back before it is sent. It is set per platform and is off by default. Blocking VPN, proxy and Tor traffic is an extra option.
- The consent check decides if it can go. The server checks consent again before every send. If consent was rejected, the event is skipped for Pinterest and the skip is logged.
The match signals sent to Pinterest
Pinterest matches a conversion to a person using the signals attached to it. DataCops sends the full set Pinterest accepts. Every personal detail is normalised and hashed with SHA-256 on the server before it leaves, so Pinterest never receives a raw email, phone or name.
| Signal | What it does for matching | Where DataCops gets it |
|---|---|---|
| epik | The Pinterest click ID. The most direct link between a conversion and the Pin that drove it. | Read from the ?epik= link, caught by the optional DataCops Cloudflare Worker |
| Email (hashed) | Matches the buyer to their Pinterest account when there is no click ID. | Verified real, then lowercased, trimmed and hashed on the server |
| Phone (hashed) | A second strong match key. | Digits only, then hashed on the server |
| External ID (hashed) | Your own stable ID for the person, so repeat events join to one customer. | 400-day durable identity |
| Name, city, region, postcode, country (hashed) | Extra details that help Pinterest confirm a match. | Normalised and hashed on the server, when you have them |
| IP address | A device and location signal Pinterest expects on a server event. | IP intelligence, the same clean IP used for the fraud verdict |
| User agent | Pairs with the IP to describe the device. | First-party capture |
Each event also carries the conversion itself: the event name mapped to a Pinterest event such as checkout, lead, signup, add_to_cart or page_visit, the time it happened, and the order value and currency. Pinterest needs at least one of email, epik or IP address, so an event with none of them is skipped and logged instead of being sent empty.
Counted once, never twice
Every DataCops event carries one steady event ID, shared across all the platforms it goes to. Pinterest uses the event ID to spot a repeat, so if your Pinterest Tag and DataCops report the same conversion with the same ID, Pinterest counts it once.
That means you can turn on server-side delivery without removing anything. Keep the Pinterest Tag, check the server events in your delivery log, and decide later what to keep. DataCops also catches a repeat of the same order before it goes out.
Connect with a Pinterest token
No code, no container, no developer.
Create a token in Pinterest
In Pinterest Ads Manager, generate a Conversions API access token for your ad account. Note the ad account ID.
Paste them into DataCops
Add the token and ad account ID on the Pinterest card in DataCops.
Map your events
In Event Manager, map each conversion to a Pinterest event, one time.
Add the Cloudflare Worker (optional)
If your site runs on Cloudflare, add the DataCops Worker so the epik click ID is caught too.
Good to know before you start
- The token is scoped to your own ad account, so you can start sending right away.
- The epik click ID comes from the optional Cloudflare Worker.
- Pinterest also matches on hashed email, phone and address details.
- Your Pinterest Tag can keep running next to DataCops.
An honest delivery log
A browser tag fires and forgets. DataCops records every send: one row per event, marked sent, skipped or failed, with the reason shown, like rejected consent, a missing ad account or an event with nothing to match on. The order value shows in the log too. So you can see, per conversion, exactly what reached Pinterest and why.
Pinterest is one of the newer connections in DataCops. Check your first sends in the delivery log and in Pinterest Ads Manager, then let it run.