Conversions API

The Conversions API sends conversion events to Pinterest from your server instead of from the visitor's browser.

You send events, checkouts, sign-ups, and purchases, straight from your backend to Pinterest over a server connection. Because it does not depend on the browser, it recovers events that ad blockers and privacy settings drop from the tag. You run it alongside the tag, and Pinterest deduplicates the overlap using a shared event ID so a single purchase is not counted twice.

A store keeps the tag firing and adds a server event on every completed order, and Pinterest recovers checkouts that a shopper's ad blocker would otherwise have hidden.

Deduplication is not automatic if you are careless. Send the same event from browser and server without a matching event ID and Pinterest counts it twice, inflating conversions and misleading the optimizer. People wire up the server feed, forget the shared ID, and end up with numbers that look great and mean nothing.

Two pipes, one event, or your reporting lies to you.