Fix guide · Any website · easy · about 20 min

Two TikTok Pixels on one site: when it's fine, how to fix

For the finding “More than one TikTok Pixel”.

What this means

Your page loads more than one TikTok pixel. A plain ttq.track(...) call is then sent to every pixel loaded on the page; TikTok’s documentation says it “will report all the installed Pixels’ events”.

That can be intended: an agency and a client, or two brands that advertise the same site, may each need their own pixel. But TikTok recommends one pixel per website, and an unplanned second pixel usually means an old, foreign or test pixel is still installed, so your data is split.

Why it can cost you money:

  • If your campaigns optimize on one pixel and part of your events go to another, conversions are missing where they matter.
  • A pixel belonging to a former agency keeps receiving your visitors’ data.
  • Two installations often come with duplicate events (see “Duplicate TikTok events”).

How to confirm it yourself

  1. Open a private (incognito) window, open developer tools (F12), go to the Network tab and filter by analytics.tiktok.com.
  2. Load the page and accept cookies.
  3. Look at the event requests (/api/v2/pixel): the pixel ID is in the payload under context.pixel.code. The script requests also show it, as sdkid= in the events.js address. More than one value means more than one pixel.
  4. Compare each ID with the pixels listed in TikTok Events Manager (Tools > Events > Data sources). Write down any ID you do not recognize.
  5. The TikTok Pixel Helper extension lists every pixel it finds on the page.
  6. Search the page source and your tag manager for ttq.load( to find where each ID is loaded.

How to fix

If the second pixel is not yours or no longer needed:

  1. Find where it is loaded: site header or theme code, a tag manager tag, a plugin or app, or code left from an earlier agency or test setup.
  2. Remove its base code (the ttq.load('<ID>') call and, if it came as a separate copy, the whole snippet). Remove event calls that only served that pixel.
  3. Publish and clear any cache.

If you need both pixels (for example agency and client):

  1. Load each pixel with its own ttq.load('<ID>') call, as TikTok’s documentation shows for multiple pixels.

  2. Decide which events each pixel should receive. ttq.track(...) goes to every loaded pixel. To send an event to only one of them, use ttq.instance:

    ttq.instance('<PIXEL-ID-A>').track('Purchase', {
  value: 49.90,
  currency: 'EUR'
}, { event_id: 'order-10482' });

  3. If you also send server events, send each one to the pixel it belongs to (event_source_id), with the same event_id as the browser copy: TikTok deduplicates per pixel.

  4. Keep the consent setup the same for both: each pixel must wait for consent.

Common causes

  • An agency or freelancer installed their own pixel and it was never removed.
  • A test pixel created during setup stayed in the code.
  • A shop app or plugin installed a new pixel next to the one pasted by hand.
  • Two tag manager containers each load a different pixel.

How to verify the fix

  1. In the Network tab, only the pixel IDs you expect appear.
  2. If you kept two pixels on purpose, each receives only the events you meant for it.
  3. Re-run the check on IsPixelWorking. If two pixels are intended, you can ignore this finding; it is reported with low severity.

Sources

More TikTok guides