Case study · Ecommerce

Meta Pixel and Conversions API with clean deduplication for ecommerce stores

Removed an old app integration that sent duplicate events, then rebuilt Meta tracking from browser and server with matching event IDs so each purchase counts once.

Case study cover: Meta Pixel and Conversions API with clean deduplication for ecommerce stores
Client
Shopify and WooCommerce stores
Market
United States, Netherlands and Belgium
Business model
Online stores selling through Meta Ads
Platform
Shopify, WooCommerce
Period
Recent client projects
Scope
Meta Events Manager audit, Pixel and Conversions API in web and server-side GTM, deduplication, purchase data

Evidence: the work and the verified results below are shown in my own project screenshots. They are kept private because they contain client account details.

01The business problem

After Apple's iOS 14 changes, browser-only Pixel tracking was missing sales. At the same time, some stores still had an old app integration sending its own events, so the same action could reach Meta twice.

Meta was optimising on numbers that weren't real: some purchases missing, some actions counted twice.

02Why it was technically difficult

Sending events from the server fixes the missing data, but only if Meta can tell that a browser event and a server event describe the same action. Without a shared event ID, adding the Conversions API makes duplication worse, not better.

Old integrations are easy to forget. They keep firing in the background, so the first job is finding every source that sends events, not adding another one.

03My approach

I started in Meta Events Manager, looking at which sources sent each event. The duplicate checkout event pointed straight at the old app integration.

With that removed, I rebuilt the tracking in one place (Google Tag Manager) so every event has a single, controlled source in the browser and on the server.

04How it fits together

  1. Store website
  2. Meta Pixel (browser)
  3. Meta
  1. Store website
  2. Server-side GTM
  3. Conversions API
  1. Same event ID
  2. Deduplication
  3. One event counted
Browser and server events with shared event IDs (generic labels)

05What I implemented

  • Events Manager auditFound and removed the old app integration that sent duplicate events.
  • Pixel and Conversions API in GTMMeta Pixel tags in web GTM and Conversions API tags in a server-side GTM environment, covering the key ecommerce events.
  • Event ID deduplicationThe same event ID sent with the browser and server version of each event, so Meta keeps one and discards the copy.
  • Purchase data and advanced matchingPurchase value, currency and content IDs on each purchase, plus hashed customer data for advanced matching.

06Testing and validation

Checked in Meta Events Manager that events arrive from both browser and server and are deduplicated.

Compared the event list before and after: the duplicate checkout event from the old integration no longer appears.

07Outcome

Delivered

  • Old duplicate-sending integration removed
  • Pixel and Conversions API running from browser and server through GTM
  • Event ID deduplication on key events
  • Purchase value, currency, content IDs and advanced matching data sent with purchases

Verified

  • Events Manager shows events received from browser and server and deduplicated, with one event per action.

Not known / not published

  • Campaign results after the change are client data and are not published.

08Technical stack

  • Shopify
  • WooCommerce
  • Google Tag Manager
  • Server-side GTM
  • Meta Pixel
  • Meta Conversions API
  • Meta Events Manager

09Related services

10Go deeper

Jobair Mahmud
Jobair Mahmud

AI-driven Performance Marketing & Web Analytics Consultant · About me

See all case studies or book a tracking consultation.

Let's Talk

Dealing with a similar problem?

Tell me what you're seeing in your reports. I'll reply with what I'd check first and whether I can help.

or reach me directly