Pinterest Standard Event Names
Some events on this Pinterest Tag are configured as Custom but use names that map almost exactly to a Pinterest standard event. A custom event called `checkout_complete` or `add-to-cart` does the same job as `Checkout` or `AddToCart`, except Pinterest does not give it the same treatment. Standard events get richer optimization, default audience templates, and the documented funnel diagnostics. Custom events do not.
Why It Matters
Pinterest defines a set of standard events (PageVisit, ViewCategory, Search, AddToCart, Checkout, Lead, Signup, WatchVideo, Custom) and gives them platform-level affordances. Smart Bidding has built-in optimization paths for them. Events Manager funnel diagnostics expect them. Default audience templates use them. Catalog Sales campaigns reference Checkout and AddToCart by name. When the implementation ships a custom event named like a standard event, Pinterest cannot connect the dots. The campaign team has to manually configure conversion-objective optimization against the custom event, audience templates that would have worked out of the box need rebuilding, and funnel diagnostics in Events Manager omit the event from the standard view. None of this is broken. It is just measurably worse than the same volume flowing through a standard event. The shape that produces this is usually a developer naming events to match the dataLayer convention on the site (snake_case, kebab-case) rather than the Pinterest convention (PascalCase standard event names). The fix is a string change on the tag side; the dataLayer can keep its own conventions.
How To Fix It
- Open the audit detail for the flagged custom events and compare each name to the Pinterest standard event list.
- For each event that maps to a standard (for example `checkout_complete` to Checkout, `add-to-cart` to AddToCart, `signup_form` to Signup), update the Pinterest Tag call to use the standard event name.
- Republish the tag and verify the standard event begins recording volume in Events Manager.
- Migrate any campaigns or audiences from the custom event to the new standard event.
- Archive the custom event once dependents have been moved and confirm the standard event is now feeding Smart Bidding and audience templates.
Example
Problem: pintrk('track', 'checkout_complete', { value: 84.5, currency: 'USD' })
Better: pintrk('track', 'Checkout', { value: 84.5, currency: 'USD' })This Pinterest Tag has custom events with names that closely resemble Pinterest standard events such as Checkout, AddToCart, Lead, or Signup. Pinterest gives standard events platform-level treatment: Smart Bidding optimization paths, default audience templates, Events Manager funnel diagnostics, and Catalog Sales campaign integration. Custom events with similar names produce the same volume but do not inherit any of these affordances, so the campaign team must configure conversion-objective optimization manually, audience templates need rebuilding, and funnel diagnostics omit the event from the standard view. The implementation works but trades default platform behaviour for naming choices that almost certainly do not need to differ from the Pinterest convention. Fix: rename the affected events to the matching Pinterest standard event, republish the tag, migrate campaigns and audiences onto the standard event, and archive the custom event once dependents have moved. Source: help.pinterest.com/en/business/article/install-the-pinterest-tag.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.
References
Audit your own files for this check
AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.
Run a free audit