Server-side tracking for Pinterest conversions
Your conversions leave your server for the Pinterest Conversions API. The purchase is fired by the validated order in your shop, not by a page loading.
Pinterest has a long buying cycle: someone pins today and buys weeks later. That is precisely the case where a server-side send, carrying a usable identifier, can still tie the sale back to the pin.
Where a shop loses its Pinterest conversions
The Pinterest tag lives in the browser, and the gap between discovery and purchase is exactly when the browser forgets.
The delay erases the trail
Weeks often pass between the pin and the purchase. Third-party cookies do not survive that; a server send with an identifier does.
The tag is blocked
As everywhere, a share of visitors never runs it. Those sales exist, they are simply not counted.
Steps with no equivalent
Pinterest has no event for every funnel step. Sent carelessly, they inflate the purchase count: we send them as a generic event, which keeps them without distorting the total.
Three steps, and nothing to rewrite
The connector installs on your shop; everything else is set in the console.
1: Install the connector
The PrestaShop module, the WooCommerce plugin or the Shopware extension, downloaded from your console.
2: Paste two values
The ad account ID and the Conversions API token, taken from your own Pinterest account.
3: Watch the Inspector
Every event sent appears with Pinterest's answer, accepted or refused, and the reason.
What Pinterest receives, event by event
Pinterest calls the purchase “checkout”. Steps with no official equivalent go out as a generic event rather than being forced into a near-enough name: they stay visible without inflating your purchases.
| Our name | Name at the platform |
|---|---|
page_view | page_visit |
view_content | page_visit |
add_to_cart | add_to_cart |
initiate_checkout | custom |
add_payment_info | custom |
purchase | checkout |
lead | lead |
complete_registration | signup |
search | search |
view_item_list | view_category |
What Pinterest will not do
Pinterest's vocabulary is shorter than ours. Here is how we handle the gap, rather than hiding it.
Two steps go out as a generic event
Checkout start and payment details have no Pinterest equivalent. We send them as a custom event: they stay visible in your reports without inflating the purchase count, which is what would happen if we passed them off as checkout.
Content view and page view merge
Pinterest has only one page_visit for both. This is not a data loss, the distinction stays intact in your console, but it does not exist on Pinterest's side, and it is better to know before comparing the two interfaces.
What the console will show you for this destination
An argument we can make because the page exists: you do not have to take our word for it, you look.
Every event, with the platform's answer
The Inspector lists what left, what the destination made of it, and the exact reason for a refusal. An invalid identifier or an expired token reads in plain words, the same day.
Identifier coverage
How many of your events carried enough to tie the conversion to a person. That is what decides match quality, and therefore the ROAS you will read at the advertiser.
The periods when nothing left
The costliest and quietest anomaly: an empty dashboard reads like a bad week, never like an outage. The console names them.
What you need
Two values, from your own Pinterest account.
The ad account ID
Ads Manager → Business Access → Ad accounts. It is a number.
A Conversions API token
Generated in the same place, sent as a Bearer token. Encrypted at rest here.
Nothing else
No password, no access to your account: we never write into your campaigns, we send conversions.
What does not leave our infrastructure
A product handling customer data owes you a statement of where it stops.
Identifiers are hashed before sending
Normalised then hashed here: the destination receives a fingerprint, never the email address or the phone number.
Consent decides, server-side too
Every event carries the consent state your banner recorded. A refusal stays a refusal: going through the server bypasses nothing.
Hosted in the European Union
The dispatcher, the database and the console are in Germany. Your tokens are encrypted at rest and never reappear in a page.
Simple to install, with no cost added on top
A design decision, not a sales promise: there is nothing to host, and nothing to unlock tier by tier.
A module, like any other
The connector installs like any other extension of your shop. Nothing to host: no container to rent, no server to maintain, no subdomain to configure.
Every destination, on every plan
Including the free one. Plans differ only by the number of sites and events, no destination is reserved for a tier, which is nonetheless the norm.
Starting costs nothing
The free plan covers one site and 10,000 events a month, with no card. Nothing breaks if you go over the quota.
Questions fréquentes
Why does server-side matter so much on Pinterest?
Because the delay is long. Weeks often pass between the pin and the purchase, and third-party cookies do not survive that. A send from your server, carrying an identifier, can still tie the sale to its source.
Will my conversions be counted twice?
No: the Pinterest tag and the server send carry the same event id, built from your order number.
What personal data is sent?
Identifiers are normalised then hashed before sending. Pinterest receives a fingerprint, never the address itself, and nothing goes out without the consent your banner recorded.
Can I check what actually left?
Yes. Your console's Inspector lists the events with Pinterest's answer for each, and the exact reason for a refusal.
The logical next step
Install the connector on your shop, know what it measures, and check what actually left.
PrestaShop module
Installing on a PrestaShop shop, step by step.
WooCommerce plugin
Installing on WordPress and WooCommerce.
Shopware extension
Installing on Shopware 6.
What we measure
The 28 events in plain words, and what a site without a shop sees.
Insights: the dashboard
Where you check what left, and what the destination made of it.
All destinations
The seven platforms one event can go to.
Connect this destination in minutes
The free plan includes every destination. No commitment, no card.