Bags & accessoriesShopifyMeta
A split Meta setup was costing Troop London clean purchase data
- Meta setups, rebuilt as one
- 2 → 1
- Meta purchase tracking
- Restored
- core ecommerce events validated
- 4
- Pixel + Conversions API together
- CAPI
The gap
What Meta could see, before and after
A third-party app had set up its own Meta events alongside the store’s existing ones. The setup was split in two: some purchases reached Meta twice, some not at all.
Purchases Meta received, beforePurchases Meta received, after
1 dot = 1 orderI see 5 missing and 6 counted twice.Purchases reach Meta again, with duplicates minimized.
- Received
- Missing
- Counted twice
Example
What our team did
Audit, configure, validate
-
Tracking audit
We reviewed every Meta event the store was sending, and found a third-party app sending its own set alongside the existing setup.
-
One Meta setup
We removed the overlap and rebuilt the store’s Meta events as a single setup.
-
Browser and server-side, deduplicated
Purchases go to Meta from the browser and through the Conversions API, with deduplication between the two.
-
Validation
We ran test purchases and checked event delivery and deduplication in Meta Events Manager.
Results
Meta purchase tracking, restored
Our team rebuilt the store’s Meta setup as one, so purchases reach Meta cleanly again, from the browser and server-side, with duplicate events minimized.
Platforms involved
- Shopify
- Meta Pixel
- Meta Conversions API
- Meta Events Manager