Pinterest Duplicate Event Names

Pinterest configures bidding and reporting on the event name. Two Checkout events under one tag is not a redundancy. It is two distinct objects that each get their own audiences, their own optimization counters, and their own row in reporting. The shapes that produce duplicates are predictable. A migration from a legacy tag template left the old Checkout in place when the new one launched. A staging configuration got promoted to production without removing the test event. A second GTM container loaded by a forgotten embed re-registered an event already published by the primary container. In every case, the front end still works. Events fire. The dashboard shows numbers. But the numbers are split, and the optimizer is running on half-evidence. For agencies reviewing a Pinterest account, duplicate events are also the cleanest indicator that the implementation has been touched by multiple owners without governance. Even when reporting impact looks small, the configuration is a red flag for the rest of the audit.

1. In Pinterest Events Manager, sort the event list by name and identify every event that appears more than once.
2. For each duplicate pair, determine which event is currently used by active campaigns and audiences and which is dormant.
3. Pause the dormant event, confirm no campaign or audience depends on it, and then archive it.
4. If both events are in use, consolidate the campaigns onto the canonical event before archiving the other.
5. Reload the page and verify that each event name appears exactly once and that subsequent Checkout, Lead, or Signup hits land on the canonical event only.