Free scan

Pixel and tag checks

How to check your Pinterest tag is working

The Pinterest tag works if the browser loads core.js from s.pinimg.com and sends requests to ct.pinterest.com/v3 with tid set to your tag ID and an event such as pagevisit. On Pinterest, a purchase is the checkout event, and it should carry a value, a currency and an order ID.

Skip the DevTools: the free scan loads your page in a real browser, accepts and rejects the cookie banner, and shows what the Pinterest tag actually sent.

At a glance

Tag script
s.pinimg.com/ct/core.js
Event request
ct.pinterest.com/v3/?tid=<tag ID>&event=pagevisit
Tag ID
A 13-digit number
Click ID
epik
Purchase event
checkout, with value, currency, order_id and event_id

Check it yourself in two minutes

  1. Open DevTools on the Network tab, filter on pinterest, accept the banner and load a page.
  2. Check the ct.pinterest.com/v3 requests: tid is your tag ID (shown under Conversions in Pinterest Ads Manager) and event is init or pagevisit.
  3. Complete a test order and look for event=checkout. Its event data should contain the value, currency and order ID.
  4. The Pinterest Tag Helper extension for Chrome lists the same events and flags missing parameters; Ads Manager's Conversions page shows events received in the last hours.

Why the Pinterest tag breaks, and how to fix it

Purchases sent as the wrong event

Pinterest has no "purchase" event: the completed order is checkout. Integrations that copy Meta or GA4 naming send a custom event Pinterest cannot use for checkout optimisation. The call should be:

pintrk('track', 'checkout', {
  value: 84.50,
  currency: 'USD',
  order_quantity: 1,
  order_id: '10045',
  event_id: 'order-10045'
});

Tag and Conversions API counted twice

Pinterest deduplicates browser and server events with the same event_id. Shop integrations that send both but only add the ID on one side report each order twice. Check the browser event has an event_id and that it matches what the server sends.

Enhanced match sends data the wrong way

Enhanced match passes the customer's email with pintrk('load', '<tag ID>', { em: … }) so Pinterest can match more conversions. Pass it through the tag's own field, which Pinterest hashes, never as part of a URL or custom parameter where it travels in plain text.

The tag loads before consent

The Pinterest tag sets cookies when it loads. In the EU and the UK it must wait for the visitor to accept marketing cookies, through your consent tool or a GTM consent condition. See Ad pixel fires before consent or after "reject".

epik lost in a redirect

Pinterest adds epik to ad clicks and the tag stores it for attribution. A redirect that drops the query string loses it. Test it with the click ID redirect tester.

What the free scan checks

  • Pinterest tag loads, and sends at least a page view
  • Only one Pinterest ID, or a warning if there are more
  • Pinterest tag waits until the visitor accepts cookies
  • Pinterest tag stops after the visitor clicks "reject all"
  • No email addresses in plain text in Pinterest tag requests
  • The epik click ID survives your redirects

Server-side events (Conversions APIs, server-side tagging) are invisible to a public scan, so the report never marks them as working or broken.

Related

Sources

Updated 2026-10-27. Based on the platforms' public documentation and the requests their public tags make; menus and names change, so check the linked pages if a step looks different.

Other platforms