Skip to content
Pinterest

Server-side Pinterest Conversions API

Send conversions to Pinterest through the Conversions API server-side — higher match rate, better attribution, and ad-blocker resistance.

Try it free Contact us

Why server-side for Pinterest?

Pinterest measures conversions via the browser Pinterest Tag, which loses 20–35% of events to ad-blockers, Safari ITP and declined consent — so Pinterest optimises on incomplete data and CPA rises. The Pinterest Conversions API (CAPI) sends conversions straight from the server and avoids that loss.

How Pinterest CAPI works with DataNostro

On arrival from a Pinterest ad the _epik click ID is stored. On an event (checkout, add_to_cart, signup) the server-side GTM container sends it straight to Pinterest CAPI — with a SHA-256 hashed email, _epik, value and an event_id. The browser tag doesn't even need to run.

What gets sent to Pinterest CAPI

  • event_name — checkout, add_to_cart, page_visit, signup, lead
  • event_id — for deduplication with the Pinterest Tag
  • user_data — em (SHA-256 email hash), click_id (_epik), hashed_maids
  • custom_data — value, currency, order_id, content_ids, num_items
  • action_source — "web"

Deduplication with the Pinterest Tag

When both the Pinterest Tag and CAPI run, Pinterest matches them by event_id — the conversion isn't double-counted. DataNostro sends the same event_id as the client tag, so dedup works out of the box.

Higher match rate via hashed email

Server-side you have reliable access to the logged-in/ordering customer's email. Sending its SHA-256 hash raises Pinterest match rate — more conversions attach to a user and attribution is more accurate than a cookie-only tag.

Setup in DataNostro — no developer

In Connections you enter the Pinterest ad account ID and CAPI token, enable _epik capture and map e-commerce events. Works with the GA4 data layer and store plugins (Shopify, WooCommerce). Done in minutes.

Detailed guide How to set up Pinterest server-side — step by step
WHY PINTEREST

Proč Pinterest přes DataNostro?

📌

Pinterest Conversions API

Server-to-server events for more reliable measurement with no dependency on the browser.

🎯

Higher match rate

Hashed identifiers (email, phone) improve conversion attribution.

🔄

Deduplication

Automatic deduplication of Pinterest Tag + CAPI — no duplicate conversions.

Easy setup

Ad Account ID + access token in Connections — done in 5 minutes.

FAQ

Frequently asked questions

What is the Pinterest Conversions API (CAPI)? +

A server-to-server interface that sends conversions straight from your server to Pinterest — instead of only the client-side Pinterest Tag. It's resilient to ad-blockers and Safari ITP.

How does deduplication between the Pinterest Tag and CAPI work? +

Via a matching event_id. Send the same event_id from the tag and CAPI and Pinterest treats it as one event, not two. DataNostro handles it automatically.

What is _epik and why does it matter? +

_epik is the Pinterest click ID stored on arrival from an ad. DataNostro captures it and sends it with the conversion to CAPI for correct campaign attribution.

Does server-side raise Pinterest match rate? +

Yes. Server-side you have a reliable customer email; its SHA-256 hash increases match rate and attribution accuracy vs cookie-only measurement.

Do I still need the Pinterest Tag? +

Not necessarily, but tag + CAPI gives the best coverage. Thanks to event_id dedup, conversions aren't counted twice.

Improve your Pinterest campaigns

Server-side Pinterest Conversions API in 5 minutes. With no server of your own.

Try it free