Attribution & Analytics
Pinterest Tag
Pinterest Tag is Pinterest's browser-side code for tracking visits and actions on an advertiser's website. It records configured events such as page visits, add-to-cart activity, signups, and checkout, supporting conversion reporting, campaign optimization, audience creation, dynamic shopping workflows, and optional enhanced matching when implemented under applicable privacy requirements. It is most useful for retailers and visual discovery advertisers that need to connect Pinterest exposure with downstream website behavior and can verify product identifiers, event values, consent, and tag health.
What it does
The Pinterest Tag is the browser-side tracking code an advertiser installs on their website to measure what people do after seeing or clicking Pinterest ads. It fires on events you configure — page visits, add-to-cart, signups, checkouts, and custom actions — and reports them back so campaigns can be optimized toward real outcomes rather than clicks. Advertisers pair it with conversion goals, build retargeting audiences from site visitors, and feed value data for return-on-ad-spend reporting. Because browser signals are increasingly blocked, Pinterest recommends combining the tag with the server-side Conversions API so attribution stays complete even when cookies or scripts are restricted.
Where it fits
It sits at the measurement-setup layer, connecting site behavior back to Pinterest ad spend.
Core features
- Standard events for page visits, cart, signup, and checkout
- Custom event and parameter tracking for value and order data
- Retargeting audience building from site visitors
- Conversion-goal campaign optimization
- Return-on-ad-spend and funnel reporting
- Pairs with the server-side Conversions API for resilient attribution
Best for
- Advertisers optimizing Pinterest campaigns toward conversions
- Ecommerce brands building retargeting audiences
Beginner notes
- Verify events fire correctly with Pinterest's tag helper before trusting the data.
- Add the Conversions API alongside the tag so browser blocking doesn't break attribution.
- Pass order value on checkout events to get real ROAS, not just conversion counts.