TikTok Duplicate Event Names
Your TikTok Pixel has multiple events configured under the same name. Two `CompletePayment` entries, two `AddToCart` entries. When both fire on the same site action, TikTok counts the conversion twice. Reported volume is inflated and bidding optimizes on a phantom signal.
Why It Matters
Duplicate events typically come from a migration that left old configurations in place. A team rebuilt their pixel through GTM and forgot to remove the hardcoded snippet. A new agency added a fresh CompletePayment event without checking whether one already existed. The pixel now has two paths to the same name, and both fire on the same `ttq.track()` invocation or two separate trigger sources hit the same action. The damage shows up in three places. Reported conversions and revenue inflate, sometimes by 2x. Smart Performance Campaigns optimize against a signal that does not match reality, so cost-per-action targets get set on inflated denominators. And deduplication against Events API server-side hits breaks, because TikTok cannot reconcile two client events with one server event when both clients share an event name and trigger window. For agencies inheriting an account, this is one of the quickest wins on the audit list. Volume reconciles immediately and reported ROAS realigns with the source-of-truth order system.
How To Fix It
- Open TikTok Events Manager and sort the event list by name. Identify every name that appears more than once.
- For each duplicate, open both events and compare their trigger source, parameters, and recent fire timestamps. The one that ships from your current GTM container or current code path is the keeper.
- Pause and delete the older or hardcoded duplicate. Do not just rename it; rename leaves the trigger live under a new label.
- Walk a real test transaction. Confirm only one `CompletePayment` lands in TikTok Test Events.
- Reconcile the next 24 hours of TikTok-reported conversions against your order system. The inflated multiplier should drop to roughly 1.0.
This TikTok Pixel has multiple events configured under the same name, which causes TikTok to count the same site action more than once. Per TikTok's Pixel setup documentation, each conversion should map to a single event configuration; duplicate names typically result from incomplete migrations between hardcoded snippets and GTM containers, or from a second team adding an event without auditing the existing setup. The downstream impact is inflated conversion and revenue volume in TikTok reporting, Smart Performance Campaigns optimizing on a phantom signal, and broken deduplication against Events API server-side hits. Fix: identify the keeper configuration for each duplicate name, pause and delete the redundant one, and reconcile TikTok reported volume against the source-of-truth order system in the following 24 hours. Source: ads.tiktok.com/help/article/get-started-pixel.
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