One Meta pixel, firing once per event
Look at: whether the pixel loads more than once. This is the most common cause of inflated Meta purchases.
Good: one pixel ID, and each event fires once per action.
Ads Manager says 40 purchases. Shopify says 61. Or the other way round. This checklist finds where your Meta, Google and TikTok tracking breaks, in about 30 minutes.
One client account, ten campaigns. A past result, not a promise. See the screenshot
No fluff pages. Here's what the actual content looks like.
Look at: whether the pixel loads more than once. This is the most common cause of inflated Meta purchases.
Good: one pixel ID, and each event fires once per action.
Meta keeps one copy of a purchase only when the browser and server versions share the same event_name and event_id.
A classic break: a theme snippet sends a random ID while an app sends the order number.
em | Email, normalised then SHA-256 hashed |
fbp | Browser ID from the _fbp cookie |
fbc | Click ID from _fbc or fbclid |
Double-hashing is a quiet killer.
Higher than store: duplicate pixels or broken dedup.
Much lower than store: no server-side tracking, consent blocking tags, or payments that never return to the thank-you page.
Yes. It's a free PDF sent to your inbox. You'll also get the occasional practical email from Wassam, and you can unsubscribe any time.
You need admin access and patience to click through settings. Each check says where to look, what good looks like and the usual fix. A few fixes, like server-side GTM, may need a developer.
Yes. Where Shopify and WooCommerce differ, the checks give both paths.
It can't promise that. It finds where tracking breaks so the numbers you make decisions on are closer to your real orders.
Free PDF, straight to your inbox.