Pinterest sends high-intent shoppers to online stores, but the data you use to optimise those campaigns is leaking. The Pinterest tag runs in the browser, so ad blockers stop it, iOS privacy settings hide it, and Safari limits shorten what it can measure. Pinterest sees fewer purchases than you actually got and optimises against a thin signal. The Pinterest Conversions API, part of the Pinterest API, fixes this by sending conversions from your own server, where ad blockers cannot reach. This guide covers what it is, why the tag alone falls short, and how to run it on WordPress and WooCommerce.
This is part of the wider move to server-side tracking. If it is new to you, start with our guide to server-side tracking on WordPress. Pinterest is one of the destinations a server-side setup feeds.
What is the Pinterest Conversions API?
The Pinterest Conversions API, sometimes called the Pinterest API for Conversions, is a server-to-server connection that sends customer actions straight from your server to Pinterest, instead of only from the browser tag. Because it does not run in the browser, ad blockers and browser privacy limits cannot stop it.
Pinterest recommends running the Conversions API alongside the tag, not instead of it. Each event carries a shared identifier, so when the tag and the API both report the same purchase, Pinterest counts it once.
Why the Pinterest tag alone is not enough
The browser tag depends on conditions that no longer hold. Several changes have eroded it:
- Ad blockers stop the tag request before it fires.
- The iOS App Tracking Transparency prompt cut the mobile signal that a large share of Pinterest traffic depends on.
- Safari and browser cookie limits shorten how long the tag can attribute a sale.
- Third-party cookies are being phased out, removing another path the tag relied on.
Each of these widens the gap between the sales you made and the conversions Pinterest can see, which means weaker optimisation and a higher cost per result.
What the Conversions API fixes
- More complete conversion data. Purchases blocked in the browser still reach Pinterest from your server.
- Better optimisation. With the real conversions in view, Pinterest delivery improves and your cost per result usually drops.
- Stronger matching. Server events can carry hashed customer details that help Pinterest match the conversion to the right person.
- More durable attribution. Server-side events do not rely on cookies that browsers delete early.
How the Pinterest Conversions API works on WordPress
On WordPress and WooCommerce, the setup has three parts: a plugin that captures the events, a server-side container that sends them to Pinterest, and Pinterest receiving them through the Conversions API.
The plugin watches your store for the actions that matter: a product viewed, an item added to the cart, a checkout started, a purchase completed. It pushes each one into the data layer and reads WooCommerce orders safely, including on stores using High-Performance Order Storage.
A server-side Google Tag Manager container on a first-party domain then forwards the events to Pinterest through the Conversions API. It sends the shared event identifier so Pinterest deduplicates against the tag, and it confirms purchases server to server, so a dropped browser event does not lose the sale.
Consent and customer data
The Conversions API sends customer data to Pinterest, so consent matters. Our setup runs Google Consent Mode v2, denied by default, so nothing fires until the visitor agrees. The customer details used for matching are hashed before they leave your site, and you decide what is sent.
Setting it up on your store
The manual path is real work: stand up a tagging server, add and configure the Conversions API tag, map every WooCommerce event, hash the customer fields, set up deduplication with the tag, and test consent.
We built our plugin and managed service to remove that. You install the plugin, import the container we provide into your Google Tag Manager, and point it at the tracking server we host. The Pinterest tag, deduplication, the WooCommerce funnel, and consent are already configured. There is no code to write and no server for you to run.
Want the Pinterest Conversions API set up on your store without the guesswork? See plans and pricing. It is one subscription from $15 a month and we set everything up for you.
Is it worth it?
If Pinterest is a real channel in your marketing, the Conversions API usually pays for itself. Cleaner data means Pinterest optimises against reality, which lowers your cost per result. If you do little on Pinterest, the tag may be enough for now. We will tell you which case you are in before you commit.