Fix guide · WordPress · easy · about 30 min

Duplicate Meta Pixel events on WordPress

For the finding “Duplicate Meta events”. Also for: Any website, Shopify, Webflow, Framer.

What this means

The same event (for example PageView, AddToCart or Lead) was sent twice for the same pixel ID within about a second, or the same pixel was set up twice on the page. On WordPress this nearly always means two plugins, or a plugin and a pasted code snippet, both load the Meta Pixel (still often called the Facebook Pixel).

Why it costs you money:

  • Meta counts some conversions twice (double-counting), so your reports look better than reality and your cost per result looks lower than it is.
  • Meta’s optimization learns from inflated data and may spend budget on the wrong people.

This is about two identical browser events. A browser event plus a server (Conversions API) event for the same action is expected; Meta merges those when they share an event ID.

How to confirm it yourself

  1. Log out of WordPress or use a private (incognito) window: some tracking plugins skip logged-in administrators, so you may not see the duplicate while logged in.
  2. Open developer tools (F12), go to Network and filter by facebook.com/tr.
  3. Load the page and accept cookies.
  4. In each request’s payload, id is the pixel ID and ev is the event name. Two requests with the same id and the same ev at almost the same moment are a duplicate. Different id values mean two different pixels, which may be intended (for example an agency pixel and your own).
  5. On a WooCommerce store, also click Add to cart on a product: AddToCart should appear once per pixel ID.

Meta Ads Data Advisor (Meta’s Chrome extension, formerly Meta Pixel Helper) reports “Duplicate Pixel code” as a common setup error, and the Test events tool in Meta Events Manager shows the event twice.

How to fix

  1. List every place the pixel can come from. Right-click the page, choose View page source and search for fbevents.js and fbq('init'. Then check:

    • Plugins > Installed Plugins in your WordPress dashboard for Meta Pixel for WordPress (Meta’s official pixel plugin), Meta for WooCommerce (formerly Facebook for WooCommerce), PixelYourSite, Pixel Manager for WooCommerce or any other tracking plugin;
    • snippet plugins such as WPCode, and Elementor Pro’s Custom Code;
    • your theme’s options (for example Divi’s Theme Options > Integration tab) and the theme’s header.php file;
    • your Google Tag Manager (GTM) container, and how GTM itself is added (Site Kit by Google, GTM4WP or a snippet).

  2. Choose one installation to keep. Usually:

    • WooCommerce store: Meta for WooCommerce, or one tracking plugin such as PixelYourSite. PixelYourSite documents that when it detects Meta for WooCommerce it makes sure the pixel is not loaded twice and takes over all pixel tracking, while Meta for WooCommerce keeps the catalog sync.
    • Site without WooCommerce: Meta Pixel for WordPress, one tracking plugin, or GTM.

    If you use a plugin that also sends server events (Conversions API), keep that one, so browser and server events share event IDs.

  3. Remove the other copies.

    • Meta Pixel for WordPress next to Meta for WooCommerce: the WordPress plugin stops its own WooCommerce events when Meta for WooCommerce is active, but it still loads the pixel. Deactivate it unless you need its form integrations, and if you keep it, check the Network tab for double PageView events.
    • Meta for WooCommerce kept only for the catalog, with tracking done elsewhere (for example in GTM): WooCommerce documents a snippet that turns off the plugin’s pixel and its Conversions API: add_filter( 'facebook_for_woocommerce_integration_pixel_enabled', '__return_false' );. Add it with a snippet plugin.
    • Pasted code: delete the pixel snippet from WPCode, Elementor Custom Code, theme fields or theme files. Removing only the fbq('track', ...) lines is not enough if the base code with fbq('init', ...) is still there twice.
    • GTM: delete Meta tags for any events your plugin already sends.

  4. Make sure GTM is added only once. In Site Kit, whether it adds the container is the Let Site Kit place code on your site toggle under Site Kit > Settings > Connected Services > Tag Manager > Edit (Site Kit warns when it finds a container already on the site while you connect Tag Manager). GTM4WP can also add the container, and so can a snippet in the theme. Keep one. In the Network tab, filter by gtm.js: each container ID should load once. If two copies of the same container load, every tag in it can fire twice.

  5. Check GTM for overlapping tags, for example a Lead tag on a form trigger and another Lead tag on the thank-you page.

  6. Update your Meta plugin. Meta for WooCommerce has fixed duplicate AddToCart events more than once, most recently in version 3.7.2 (June 2026) for repeated AJAX cart updates.

  7. Clear every cache (plugin, host and CDN), so visitors stop getting pages with the old code.

Common causes

  • Meta Pixel for WordPress and Meta for WooCommerce are both active with the same pixel.
  • A tracking plugin loads the pixel, and Meta’s base code is also pasted into a snippet plugin, a theme field or Elementor Custom Code.
  • The pixel is in a plugin and in a GTM tag.
  • GTM is added twice, for example by Site Kit or GTM4WP and by a snippet in the theme.
  • An older version of Meta for WooCommerce sends AddToCart twice on AJAX add-to-cart.
  • A theme or child theme came with a pixel in its header.php.

How to verify the fix

  1. Clear all caches. In a private window, accept cookies and check that each event appears once per pixel ID: on page load, after a button that sends an event, and after Add to cart on a store.
  2. Re-run the check on IsPixelWorking. The issue should be gone.

Sources