Skip to content

Guide · Tracking and analytics

Meta Pixel purchase events firing twice: how to find the cause and fix it

By The Microployed teamUpdated 3 min read

The short answer

Doubled purchase events almost always mean two setups are sending the same event, such as a pixel pasted into your theme plus Meta's sales channel app, or a browser pixel and a Conversions API connection that don't share an event ID. Find the two sources with Meta Pixel Helper and Test events, remove or connect the extra one, then place a test order and confirm that only one Purchase arrives.

The steps, about 30 minutes

  1. Step 1: Open an order confirmation page with Pixel Helper

    Install Meta Pixel Helper in Chrome and open the confirmation page of a recent test order. The badge on the extension's icon shows how many pixels loaded, and the popup lists the events each one sent.

  2. Step 2: Compare the pixel IDs

    Two different IDs usually mean an old pixel from a previous agency or theme is still installed. The same ID listed twice means two separate installs are sending events to one pixel.

  3. Step 3: Find where each install lives

    Search your theme files for fbq(, then check your apps, your Google Tag Manager container and your Meta sales channel or partner integration. Write down every place that adds Meta code.

  4. Step 4: Remove the extra install

    Keep the install that's easiest to maintain, which is usually your platform's official Meta integration, and remove the other one. If the extra one is in Tag Manager, pause the tag first so you can roll back.

  5. Step 5: Check deduplication if you use the Conversions API

    Browser and server events only count once when the pixel's eventID matches the server's event_id and both use the same event name. Confirm your integration sends a shared ID for Purchase.

  6. Step 6: Place a test order and watch Test events

    Open Test events in Events Manager, place a small order, and check that each Purchase appears once per source and shows as deduplicated when both browser and server events arrive.

Why purchases get counted twice

When Ads Manager reports roughly twice as many purchases as your store, the cause is nearly always that two separate setups are sending the same Purchase event. Meta has no way to know they describe one order, so it counts both. These are the setups we see most often on small stores:

  • A pixel pasted into the theme years ago, and the pixel added later by Meta's sales channel app or another partner integration.
  • The same pixel fired from Google Tag Manager and from the theme at the same time.
  • An app, such as an upsell, reviews or analytics tool, that adds its own Purchase event without telling you.
  • A browser pixel and a Conversions API connection that both send the purchase but don't share an event ID, so Meta can't match them.
  • An order confirmation page that fires the event again every time a customer reloads it or returns from the order email.

How to tell which one you have

The fastest test is to open a recent order's confirmation page with Meta Pixel Helper (opens in a new tab) running. It shows how many pixels loaded and every event each one sent, along with errors such as a pixel that didn't load. Two Purchase events on the first load point to two installs. If the page looks clean on the first load but sends another Purchase when you refresh it, the install is fine and the problem is that the event isn't limited to the first visit. The fix there is to guard the event so it only fires once per order, usually by checking the order ID before firing.

You can also run the page through our free tracking checker. It reads the page source and lists every Meta pixel ID it finds, which is a quick way to spot a leftover pixel from an old theme. Pixels set up inside Tag Manager won't appear there, so use Tag Manager's Preview mode for those.

How Meta matches browser and server events

If you send purchases through both the pixel and the Conversions API, Meta can count each order once, but only when the two events carry matching identifiers. According to Meta's deduplication documentation (opens in a new tab), the recommended method is to send the same event ID from both sides: the pixel's eventID has to match the server's event_id, and the event names have to match as well. Events are only deduplicated when they arrive within 48 hours of the first event with that ID.

What arrivesShared event ID?What Meta counts
Browser Purchase and server PurchaseYes, identicalOne purchase
Browser Purchase and server PurchaseNo, or differentTwo purchases
Two browser Purchase events from two installsNot applicableTwo purchases
Server Purchase arriving 3 days lateYesCounted again, outside the 48 hour window

Most official platform integrations handle the shared ID for you. Problems usually start when someone adds a second server connection, such as a custom script or a third party app, next to the official one.

Checking that the fix worked

After you remove the extra install, place a small test order with Test events open in Events Manager and confirm that the Purchase shows up once per source. Then compare Ads Manager with your store's orders over the next few days. The two will rarely match exactly, because Ads Manager credits purchases to ads based on your attribution settings and some browsers block the pixel, but a steady two to one gap should be gone.

If the order confirmation page is the cause, test it twice: once on the first load and once after a refresh. Only the first load should send a Purchase.

When it makes sense to hand it off

Finding the second install takes most people 20 minutes to an hour, depending on how many apps and past developers have touched the store. If you'd rather not dig through theme files, our job template for this fix has the scope written out, including the exact access to give.

Short on time? Hand this one off.

Post it as a small job and a pro who knows Meta Ads picks it up, with the price set before anyone starts. Most pros finish it in 30 minutes to 1.5 hours. Businesses in the beta get credits to try it.

Post this as a job on Microployed

The next level up

Send richer purchase data so Meta can find more buyers like yours

Once every purchase fires once, the next step is sending more of what Meta can use: the order value and currency, product IDs that match your catalog, and hashed customer details through Advanced Matching. Adding the Conversions API alongside the pixel means purchases still reach Meta when a browser blocks the pixel, so fewer sales go missing from your reporting.

Have a pro add the Conversions API

Questions people ask

Why does Ads Manager show more purchases than my store?

Ads Manager credits purchases to ads based on your attribution settings and reports them by the date of the ad interaction, so daily numbers rarely match your store exactly. A gap that stays close to double, day after day, points to a duplicate event rather than attribution.

Will removing a duplicate pixel hurt my ads?

Reported purchases will drop to their real level, which can look alarming at first. Campaigns that optimize for purchases are working from more accurate data afterward, though results can move around for a few days while delivery adjusts.

Is it OK to have two different pixels on one site?

Yes, if it's intentional, for example when two ad accounts each need their own data. The problem is one order sending the same event twice to the same pixel.

How long does Meta take to deduplicate browser and server events?

Meta only deduplicates events that arrive within 48 hours of the first event with the same event ID, so a server event sent days later is counted as a new purchase.

Sources

Checked against these pages on .