Facebook Pixel Duplicate Purchase Events: Find the Source and Fix It
Quick fix
Facebook pixel duplicate purchase events usually mean more than one thing is sending the same purchase to Meta. Typical sources are the Shopify app, site code and Tag Manager. Find which sources send purchase events, keep one, or give server and browser events a matching event ID.
- Check for duplication in Events Manager or Meta Ads Data Advisor.
- List every place the pixel ID is installed: Shopify, theme code, Tag Manager.
- Remove the extra sources, keeping one.
- If you use server and browser events, match their event IDs.
Can't fix it yourself? Send me the details
What this error means
Meta counts a purchase each time it receives one. If two integrations both log the same order, it is counted twice, inflating sales and ROAS in your ads reporting.
Why it happens
1Two integrations send the purchase
The Facebook and Instagram app and a site pixel can both log it.
How to tell if this is you: Data Advisor shows two Purchase events.
2Pixel ID added in more than one platform
Adding the ID to Shopify or Tag Manager as well creates another source.
How to tell if this is you: The ID appears in Shopify and in Tag Manager.
3Server and browser events both enabled
Shopify Enhanced sharing sends via the Conversions API as well as the pixel, so matching IDs matter.
How to tell if this is you: Data sharing is set to Enhanced or Maximum.
How to fix it
Find the source
For: Two integrations send the purchase, Pixel ID added in more than one platform
- Check for duplication in Events Manager or Meta Ads Data Advisor.
- Ask your web developer which integrations send purchase events.
Keep one source
For: Two integrations send the purchase, Pixel ID added in more than one platform
- Remove the pixel ID from the extra platforms.
- In Shopify, review the settings under Facebook and Instagram.
Deduplicate server and browser events
For: Server and browser events both enabled
- Add the same event ID to the pixel and server events.
- Remember Meta only deduplicates within 48 hours.
How long it takes
Meta doesn't publish a timeline for this.
How to stop it happening again
- Install the pixel in one place and record where.
- Re-check for duplicates after changing integrations.
- Use event IDs whenever you send server and browser events.
From my desk
Nearly always it's the pixel installed twice. Once through the Shopify channel or the theme, and again through Tag Manager or an agency plugin. I open the Meta pixel helper on the thank you page and count the Purchase events, then trace each one back to where its code lives and remove the extra source.
Muhammed Abdul Kalam
When to get help
- You've worked through the checks and the numbers or status still aren't right.
- The setup involves a tag manager, Shopify app or developer you cannot reach and nobody can explain it.
- Results are suffering during a launch or sale and every day costs real money.
Stuck on this? Send me the details.Tell me what the platform shows and what you've tried so far.
Send me the detailsFAQs
Why would Meta get purchases twice?
Events are sent two or more times when more than one channel logs them.
What causes it on Shopify?
Using the Facebook and Instagram app and also adding the pixel ID to Shopify or Tag Manager.
How do I check for duplication?
In Events Manager or with Meta Ads Data Advisor.
Does server tracking cause duplicates?
Shopify Enhanced sharing uses the Conversions API as well as the pixel, so events need matching IDs to deduplicate.
Is there a time limit on deduplication?
Yes. 48 hours from the first event with that ID.
Related fixes
- Facebook Conversions API Duplicate Events: Why They Happen and How to Fix Them
- Facebook Ads Manager Results Do Not Match Shopify: Why and What to Check
- Facebook Pixel Not Firing: How to Find the Cause and Fix It
- Facebook Pixel Not Working in Google Tag Manager: What to Check
- All Meta Pixel and Conversions API fixes