Skip to content

Job template · Tracking and analytics

Job template: fix duplicate Meta Pixel purchase events

By The Microployed teamUpdated 2 min read

The short answer

Use this scope when Ads Manager shows far more purchases than your store records. A tracking pro finds every place that sends a Purchase event, removes or connects the duplicate, and proves the fix with a test order in Events Manager. Most jobs take 30 to 90 minutes.

Ready-to-post scope

Fix the Meta Pixel so each purchase is counted once

Typical time for a pro: 30 minutes to 1.5 hours

Ads Manager shows about twice as many purchases as our store records. Find every place that sends a Purchase event (theme, apps, Google Tag Manager, Meta integration or Conversions API), remove or connect the duplicate, and confirm with a test order that each purchase is counted once.

Check first

  • Compare purchases in Ads Manager with orders in your store for the last 7 days
  • List the apps, theme edits and tag manager containers that might add Meta code
  • Find out whether you also send events through the Conversions API

Access to give

  • Partner access to your Meta pixel in Business settings
  • A staff account on your store with access to themes and apps
  • User access to Google Tag Manager, if you use it

Done when

  • A test order sends one Purchase per source in Events Manager's Test events
  • Browser and server events show as deduplicated if both are used
  • A short note lists what was removed or changed, and where

When to use this template

Post this job when Ads Manager reports noticeably more purchases than your store, especially when the gap stays close to double from one day to the next. That pattern almost always means two setups are sending the same Purchase event, and Meta is counting each order twice. If you'd like to try the fix yourself first, our guide on Meta Pixel purchase events firing twice walks through it.

What the pro will do

The pro opens a recent order confirmation page with Meta Pixel Helper to count the pixels and events that load, then traces each one to its source: your theme code, your apps, Google Tag Manager, or Meta's sales channel or partner integration. They remove the extra install, or connect the browser pixel and the Conversions API with a shared event ID if both should stay. Finally, they place a test order with Events Manager's Test events open and confirm that the Purchase arrives once per source.

How to review the work

Ask for a short note listing what was found, what was removed and where. Then open Test events yourself and place a small order, or watch the pro's test order come through. Over the following few days, compare purchases in Ads Manager with orders in your store. They won't match exactly because of attribution settings, but the steady two to one gap should be gone.

Things that commonly trip this job up

Old pixels pasted into theme files survive theme changes more often than people expect, so the pro may need to search older theme versions too. Upsell and post-purchase apps sometimes fire their own Purchase event without mentioning it in their settings. And if someone added a custom server connection next to your platform's official integration, removing one of the two is usually simpler than making them share event IDs.

The next level up

Add the Conversions API so fewer purchases go missing

With each purchase counted once, adding Meta's Conversions API alongside the pixel sends purchases from your server as well, so sales still reach Meta when a browser blocks the pixel. Sending value, currency and product IDs that match your catalog gives Meta more to work with when it looks for buyers.

Post the Conversions API job

Questions people ask

Do I need to give the pro my Meta login?

No. Add them as a partner on your pixel in Meta Business settings with the permissions the job needs, and remove that access when the job is approved.

Will my ads stop running while this is fixed?

No. The ads keep running. You'll see reported purchases drop to their real level once the duplicate is gone.

What if the duplicate comes from an app I need?

The pro can usually turn off that app's pixel setting while keeping the app itself. If the app has no such setting, they'll tell you and suggest the cleanest option.

Sources

Checked against these pages on .