How to Track Pinterest Ads Conversions on Shopify

|Dan Giura
How to Track Pinterest Ads Conversions on Shopify

TL;DR

Pinterest's API for Conversions gives ads a server-side delivery path. What Shopify stores lacked was an integration that used it without a Google Tag Manager project. As of July 28, 2026, WeltPixel Conversion Tracking (WCT) ships Pinterest Ads as its eighth integration: the Pinterest tag loads on your storefront for attribution, and conversion events, seven in total, from page visit to purchase, are delivered through Pinterest's API for Conversions. The purchase comes from Shopify's order webhook rather than the buyer's browser, so ad blockers and closed tabs don't erase sales from your campaign reporting. This guide walks the exact setup: where each of the three credentials lives in Pinterest Ads Manager, the one-account rule that trips people up, how to verify events with Pinterest's test mode, and how to avoid double-tracking if you already run the official Pinterest for Shopify channel.

What Do You Need Before Starting?

Three values, all from Pinterest Ads Manager, all from the same ad account:

  1. Pinterest Tag ID. In Ads Manager, open Ads → Conversions. Your tag is listed there; the Tag ID is the numeric code next to its name, typically 13 digits [1]. If you don't have a tag yet, click Create tag and skip any "install the code on your website" step, because you won't be pasting code anywhere.
  2. Ad Account ID. The fastest source is your browser's address bar: the Ads Manager URL contains it, in the form ads.pinterest.com/advertiser/549712345678/ [1]. The same number is under Business Access → Ad accounts in Pinterest Business Hub.
  3. Conversions API access token. In Ads → Conversions, open the Conversions API section and click Generate new token. The token starts with pina_ and Pinterest shows it exactly once, so copy it before closing the dialog [1]. Lose it and you generate a new one; nothing breaks except your patience.

The one-account rule: all three values must belong to the same ad account. Mixing a Tag ID from one account with a token from another gets events silently rejected, and it is the single most likely misconfiguration in this setup.

In WCT, open the Pinterest integration, paste the three values, and save. If you skipped the app's theme embed at install time, enable it under Online Store, Themes, Customize, App embeds; the setup checklist in the app flags this, and without the embed the storefront tag never loads. The app validates the credentials against Pinterest's API on save, so a bad token fails immediately instead of failing quietly later. One catch worth knowing: that validation cannot detect a mistyped Tag ID, because the Tag ID is not part of the API call being tested. If conversions attribute nowhere, the Tag ID is the first thing to re-check.

What Actually Gets Tracked, and From Where?

The integration splits work the way server-side tracking should on Shopify, a division covered in depth in our Conversion API vs browser pixel guide:

  • The Pinterest tag loads on your storefront and handles attribution. You don't install any base code; the app's theme embed does it. The tag's job is the page visit and Pinterest's attribution machinery, not conversion delivery.
  • Seven events go to Pinterest's API for Conversions: page visit, product view, category view, search, add to cart, checkout start, and the purchase. The page visit, the one event both paths report, carries a shared event ID so Pinterest can deduplicate the pair.
  • The purchase never depends on the buyer's browser. It is sent when Shopify records the order, with the order's total as the conversion value. An ad blocker, a closed tab, or iOS privacy changes can hide your pixel; they cannot hide the order webhook.

That last point is the whole reason to care. The longer the gap between the ad click and the purchase, the more chances browser-side tracking has to lose the trail, and on a planning-oriented surface like Pinterest that gap can run long. Server-side delivery holds the thread at the moment it matters most: when the money actually moves.

Every event has its own on/off toggle in the app, so a store that only wants purchase and checkout data can trim the rest.

If You Already Run the Official Pinterest Channel

Shopify's Pinterest sales channel installs a Pinterest tag of its own. Running it alongside WCT against the same Tag ID means two integrations reporting to one tag, which can inflate your conversion counts. Pick one:

  • If you want the official channel for its catalog syncing, keep it for that and let one integration own the tracking.
  • Either way, run one integration per Tag ID, decided by you rather than by load order. WCT deliberately stands down its own tag if another Pinterest tag is already on the page rather than stacking a second copy, so an unresolved conflict silently costs you the app's attribution layer.

The same caution applies to a manually pasted Pinterest tag left over from an old setup: remove it. Leaving it in place makes the app stand down its own tag, which quietly costs you the attribution layer.

How to Verify Events Are Arriving

Pinterest ships a proper test surface, and WCT wires into it:

  1. In the app's advanced settings, enable Pinterest test mode.
  2. In Pinterest Ads Manager, open Campaign manager → Conversions → Test events.
  3. Browse your storefront, add something to cart, and run a test checkout. Events show up in the test view as they arrive.
  4. Turn test mode off as soon as you're done. The toggle is shop-wide: while it is on, real shoppers' events divert to the test view too, visible but never recorded for reporting or optimization. The storefront tag's page visits still record normally.

For ongoing monitoring, the app's recent-events feed shows what was sent to Pinterest alongside the other platforms, so an integration that stopped sending shows up as silence you can see.

What This Costs and Where It Sits

Pinterest Ads is part of WCT's paid plan: $39/month flat, unlimited orders, alongside GA4, Meta, TikTok, Google Ads, Reddit, and OpenAI ads, plus Klaviyo event sync. There is no per-order metering and no per-channel fee; Pinterest is the eighth integration at the same flat price the plan cost before it existed. The free plan covers GA4 tracking only.

Before this integration, the realistic Pinterest options for a Shopify store were the official channel or building a Google Tag Manager server container, a trade-off we mapped in our Pinterest tracking landscape article. The container route still makes sense for GTM-fluent teams that want full control; for everyone else, the point of this integration is that the server-side path no longer requires one.

Key Takeaways

  • Setup is three values from Pinterest Ads Manager: Tag ID (Ads → Conversions), Ad Account ID (the Ads Manager URL), and a pina_ Conversions API token that Pinterest shows exactly once.
  • All three credentials must come from the same ad account, or events are rejected.
  • With the app's theme embed enabled, the Pinterest tag loads for attribution on its own; no base code goes into your theme.
  • Seven events are delivered through Pinterest's API for Conversions, and the purchase is sent when Shopify records the order, valued at the order total, out of reach of ad blockers.
  • If the official Pinterest for Shopify channel or a manual tag is already tracking, run one integration per Tag ID, not two.
  • Verify with the app's test mode against Pinterest's Test events view, then switch test mode off.
  • Pinterest Ads is included in WCT's $39/month flat plan as the eighth integration.

FAQ

Does Shopify support Pinterest conversion tracking natively?

The official Pinterest for Shopify channel installs the Pinterest tag and, depending on the channel version, can send API events too. What it does not give you is unified control: one place where Pinterest sits next to GA4, Meta, TikTok, and the rest with the same event toggles and the same server-side purchase path. That is the gap a tracking app fills.

Do I need Google Tag Manager for Pinterest server-side tracking?

Not anymore. A GTM server container was the standard route to Pinterest's API for Conversions on Shopify, and it still works if you have the expertise. WCT's integration delivers the same API events without a container to build or maintain.

Where do I find my Pinterest Conversions API token?

Pinterest Ads Manager → Ads → Conversions → Conversions API section → Generate new token. It starts with pina_ and is displayed only once, at creation. Copy it immediately; if it's gone, generate a fresh one and update it in the app.

Why do my Pinterest conversions show a different value than my ad platform reports elsewhere?

WCT sends the purchase valued at the order total, including tax and shipping, the same basis it uses across GA4, Meta, TikTok, and the other platforms, so cross-channel comparisons stay apples to apples. Platforms that value conversions at subtotal will read lower on identical orders.

Can I test Pinterest tracking without polluting my campaign data?

Yes. The app's Pinterest test mode routes events to Pinterest's Test events view, where they are visible but not recorded for reporting or optimization. Turn it off after verifying, because while it is on, Pinterest is effectively not tracking your real server-side events.

Start Tracking Pinterest Conversions Today

If you run Pinterest ads on Shopify, the setup above takes about five minutes end to end. Install WeltPixel Conversion Tracking from the Shopify App Store, paste your three Pinterest values, and your campaigns start reporting real conversions, purchases included.

Sources

  1. WeltPixel Conversion Tracking setup documentation, Pinterest sections: https://weltpixel.com/pages/shopify-conversion-tracking-docs (verified July 29, 2026).
  2. Pinterest Ads Manager: https://ads.pinterest.com.

Questions or notes on this guide? Discuss it on r/WeltPixel.

Ready to upgrade your tracking?

Server-side tracking for Magento and Shopify — accurate data, better attribution, full privacy compliance.