{# DE + SK hreflang odebráno 2026-05-24 — viz core/settings.py LANGUAGES. cross_lang_alternates is set False by views whose CS/EN versions live on DIFFERENT paths (KB articles/categories, blog posts) — there the naive same-path alternate would point at a non-existent URL, so we emit only the self-canonical instead of a wrong reciprocal. #}

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?

The Pinterest Tag (client-side) loses data to ad-blockers and iOS limits. The Pinterest Conversions API (CAPI) sends conversions straight from the server — with hashed identifiers for better matching and attribution.

How it works with DataNostro

In Connections you paste your Pinterest Ad Account ID and a conversion access token. Conversions (checkout, add_to_cart, page_visit) are sent server-side, deduplicated with the Pinterest Tag via event_id.

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

Why Pinterest through 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.

Frequently asked questions

Do I still need the Pinterest Tag?

We recommend dual tracking (Tag + CAPI). DataNostro deduplicates events automatically via event_id.

How do I set up the Pinterest Conversions API?

In Pinterest Ads you create a conversion access token, paste it with the Ad Account ID into DataNostro Connections, and conversions flow server-side automatically.

Improve your Pinterest campaigns

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

Try it free