Meta Pixel firing twice
When the Meta Pixel loads twice, Meta counts every page view and every purchase twice. Campaigns look better than they are, and Meta optimises on wrong numbers. Usually the pixel is simply installed in two places.
How you notice
- Events Manager receives roughly twice as many PageView events as you have visitors.
- Purchases in Meta are clearly higher than the orders in your shop.
- Meta Pixel Helper shows the same pixel ID several times or warns about duplicate events.
Common causes
Two installation paths at once
The pixel is in the theme code and also comes via an app, a plugin or Google Tag Manager. Each path loads it once.
Two plugins doing the same job
For example a shop plugin with a built-in Meta connection plus a separate pixel plugin. Both send the same events.
Pixel and Conversions API without matching
If you also send events through the Conversions API, both need a shared event ID. Without it Meta can't merge the browser and server event.
How to check it yourself
- 01Install the Chrome extension Meta Pixel Helper and open your website. It lists every pixel it finds with its ID and events.
- 02For a closer look open the developer tools (F12) and go to the Network panel. Type facebook.com/tr into the filter and reload the page.
- 03Per page view there should be exactly one request with ev=PageView per pixel ID. Two requests with the same ID mean the pixel loads twice.
- 04Then check the order confirmation with a test purchase: the Purchase event should also arrive only once.
How to fix it
- Pick one installation path (for example the official shop integration or Google Tag Manager) and remove all others.
- Search the theme code for fbq( and your pixel ID to find forgotten installs.
- If you also send events through the Conversions API, give the browser and server event the same event ID.
Let it be checked automatically
On every check Trackneat sees which pixels load on the page and tells you when the same pixel loads more than once.
The free check shows you in about a minute which tracking tags run on your website and whether anything fires before cookie consent. No account needed.