Pinterest Tag & Conversions API Recipe
Set up the Pinterest Tag on Cloudflare Zaraz in 1 click.
Pinterest Tag Built-in Recipe
Section titled “Pinterest Tag ”Track conversions and sales from your Pinterest campaigns. The Pinterest Recipe sets up the Pinterest Tag in Cloudflare Zaraz, so your pages don’t load Pinterest’s own script.
What You Need
Section titled “What You Need”You only need your Pinterest Tag ID (a numeric string, e.g. 2612345678901).
Where to find it: In Pinterest Business Hub, go to Ads > Conversions > Tag Manager to find your unique Tag ID.
3-Step Setup
Section titled “3-Step Setup”- Go to WP Zbridge > Zaraz Recipes in WordPress.
- Toggle on Pinterest Tag and paste your Tag ID.
- Click Sync to Zaraz.
Events Tracked Automatically
Section titled “Events Tracked Automatically”| Customer Action | Pinterest Event | What’s Sent |
|---|---|---|
| Browsing pages | pageview | Page URL |
| Adding to cart | addtocart | Product details |
| Completing an order | checkout | Order value, currency, products |
| Searching the site | search | Search term |
| Submitting a form | lead | |
| Creating an account | signup |
Pinterest Conversions API Pro
Section titled “Pinterest Conversions API ”Add the Conversions API to send add to cart and purchases from Cloudflare’s servers, so blockers of Pinterest’s own tag don’t stop them (a blocker that stops Zaraz itself still does). Purchases reported by the Pro server fallback reach Pinterest too.
With Send customer details with server-sent purchases (Pro, under WP Zbridge > E-Commerce), those server-sent purchases also carry the buyer’s email, phone, name and address, which Zaraz’s Pinterest Conversions API tool hashes before sending. It’s off by default.
What you need: your Ad Account ID and a Conversion Access Token, both from the Conversions section of Pinterest Ads Manager. Enter them under Pinterest Conversions API in WP Zbridge > Zaraz Recipes, then sync.
Pinterest counts an event once only when the tag and the API send the same event_id. WP Zbridge splits the events so nothing is counted twice:
| Event | Pinterest Tag (browser) | Conversions API (server) |
|---|---|---|
| Page visit, search, lead, sign-up | ✅ | — |
| Add to cart | — | ✅ |
| Purchase | ✅ with the order’s event_id | ✅ same event_id |
Without the tag (Conversions API only), leads and sign-ups go through the API as well.
Limits:
- Zaraz’s Conversions API tool doesn’t receive Pinterest’s click ID, so Pinterest matches API events to ad clicks by IP address and browser.
- The tool forwards every store event, so Pinterest may show events it doesn’t recognize (for example
Product Viewed) as rejected. This doesn’t affect the events above.