Meta Pixel events double count on Shopify and WordPress sites because more than one thing is sending the same event: a plugin and a GTM tag, a hardcoded theme snippet and an app, or browser and server events without a shared event ID. The fix is to find every source, keep exactly one per channel, and confirm in Events Manager that each lead or purchase arrives once from the browser and once from the server, deduplicated.
This is one of the most common problems agencies inherit. A client has had three freelancers and two agencies, each of which "installed the Pixel", and nobody removed the previous install. Ads Manager reports more purchases than Shopify recorded, or more leads than the inbox received, and the media buyer is optimizing against inflated numbers. This guide is a practical checklist for finding and removing the duplicates.
Why double counting matters more than it looks
Inflated conversions do two kinds of damage. The obvious one is reporting: the client sees a cost per lead that is better than reality, until they compare it with their CRM and lose trust in the agency. The less obvious one is optimization. Meta's delivery system learns from the events you send. If a purchase counts twice, or a page load counts as a lead, Meta is being told some traffic converts better than it does, and it will look for more of it.
The usual sources of duplicates
1. A plugin and GTM both firing the Pixel
The most common case. Someone installed the Pixel through a WordPress plugin or a Shopify app, then a later agency added a Meta Pixel tag in Google Tag Manager. Both load the base code and both send PageView. Often both also send Lead or Purchase, each with its own trigger.
2. Hardcoded Pixel in the theme
Older installs often pasted the base code directly into header.php, a theme options box, or a Shopify theme file such as theme.liquid. Theme code survives plugin changes and agency handovers, and nobody remembers it is there. Event snippets pasted into a thank-you page template are similar.
3. Multiple Pixels on the same site
Sometimes there are two different Pixel IDs: an old one from a previous Business Manager and the current one. That is not double counting within one dataset, but it means events are split, and if both datasets are connected to the ad account, reporting gets confusing. Decide which dataset the ad account uses and remove the other.
4. Shopify: the Meta sales channel plus custom pixels
On Shopify, the usual official route is Meta's Facebook and Instagram app (sales channel), which can send both browser and server events depending on the data sharing level chosen. Shopify has also moved checkout and thank-you page tracking toward its customer events framework, where custom pixels run in a sandbox.
Duplicates appear when the Meta app is sending events and someone also added a custom pixel in customer events, a GTM container that loads the Pixel, or a third-party tracking app. Older stores may also still carry tracking code from the legacy checkout or additional scripts on the order status page. Check every one of these places, not just the one you expect.
5. WordPress plugins sending server events without dedup
Plugins such as the official Meta plugin for WordPress and WooCommerce, PixelYourSite and others can send both Pixel events and Conversions API events. When a single plugin does both, it usually generates a shared event ID and deduplication works. Problems start when:
- One plugin sends the browser Pixel and a different plugin or server GTM sends the server events, each with its own event ID.
- Two plugins both have Conversions API turned on.
- The plugin's server events use a different event name from the browser event for the same action.
- Page caching serves a cached page with an event ID baked into the HTML, so the browser and server IDs no longer match, or every visitor shares one ID.
Most of these plugins are fine on their own. The issue is almost always the combination. The deduplication guide explains exactly what has to match.
6. Thank-you page reloads and back buttons
If Lead or Purchase fires on a thank-you page view, every reload, every return visit from a bookmarked page, and every back-and-forward navigation sends it again. On Shopify, customers often revisit the order status page from their confirmation email. Unless the event uses the order ID as its event ID, or the tag checks whether the order was already tracked, each visit can count.
7. Form plugins firing on click, not on success
A Lead event on the submit button's click fires for failed validations, double clicks and spam submissions that the form plugin rejects. It should fire on confirmed success: the plugin's success event, a redirect to a thank-you page that cannot be reached otherwise, or a data layer push after the server accepts the submission.
How to diagnose it
Work from the outside in. You want a list of every source, not just the first one you find.
Step 1: Meta Pixel Helper
Install the Meta Pixel Helper browser extension and load the site's key pages. It shows each Pixel ID found and each event sent, and it warns when it sees the same event more than once or the base code loaded twice. Walk through a real conversion: landing page, form submission or checkout, thank-you page. Note every event and how many times it appears.
Pixel Helper only sees browser events. It will not show server events, and on Shopify it may not show everything sent from sandboxed custom pixels. Use it as a first pass.
Step 2: Find every install
- View the page source and search for
fbq(,connect.facebook.netand the Pixel ID. Note whether each hit is in the theme, a plugin script or GTM. - Open GTM and search the container for Meta or Facebook tags, custom HTML containing
fbq, and community templates. - WordPress: list active plugins and check each one that mentions Meta, Facebook, pixel, conversion or tracking. Check theme options and any header/footer script plugins.
- Shopify: check the Meta sales channel's data sharing settings, the customer events section for custom pixels, installed apps that mention tracking or pixels, and the theme code.
Step 3: Test Events in Events Manager
Open Test Events for the dataset and run a real conversion. Test Events shows browser and server events separately. For a clean setup you want, for each action: one browser event, one server event, the same event name, and a deduplication confirmation. Two browser events for one action means two Pixel installs. Two server events means two server senders.
Step 4: Compare with the source of truth
Pull Meta's reported conversions for the last 30 days and compare them with Shopify orders or CRM leads for the same period. Meta should report fewer than the total, because not every sale came from Meta. If Meta reports more purchases than the store had orders, or more leads than the form received in total, you have confirmed duplication, before you even look at attribution windows.
| What you see | Likely cause | Where to look |
|---|---|---|
| Pixel Helper shows the base code loaded twice | Two installs of the same Pixel | Theme code, plugins, GTM |
Two browser Lead events per submission | Plugin and GTM both send Lead | Plugin event settings and GTM triggers |
| Browser and server events arrive but are not deduplicated | Different event IDs or event names | Which tool sends each, and how IDs are made |
| Two server events per action | Two server senders | Plugins, Meta app settings, server GTM, Gateway |
| Purchase count climbs days after the order | Order status page revisits | Thank-you page tag and event ID |
