Meta Pixel + CAPI Deduplication Checker

Verify browser (Pixel) and server (CAPI) event pairing. Ensure identical event_id and event_name to prevent costly conversion double-counting in Meta Ads.

Event Pairing Inputs

Case-sensitive (e.g. Purchase, Lead)

Must match browser event name exactly

Generated on client (GTM variable / dataLayer)

Generated on server (webhook / sGTM)

Client dispatch timestamp

Must be within 48h of browser event

First-Party Cookie Parameters
Deduplication Status

Perfect Deduplication Match

Both browser and server events share the exact same event_id and event_name. Meta will merge both payloads into 1 deduplicated conversion with maximized EMQ match rates.

Verification Checks

  • ✓
    Event ID Exact MatchBoth payloads contain identical alphanumeric IDs
  • ✓
    Event Name Exact Case MatchBoth events use standard casing
  • ✓
    Timestamp Window ValidEvents arrived within 2 seconds of each other (well within 48h limit)
  • ✓
    Cookie Signal Integrity_fbp and _fbc present for deterministic attribution

Why Deduplication is Critical

When you run Meta Pixel alongside Server-Side CAPI without matching event_id, Meta treats the two signals as two distinct transactions. This inflates reported purchases by 100%, causing Smart Bidding to over-estimate ROAS and misallocate budget.

INTERACTIVE DEMO Want to test how this tool works?
Save these results as a PDF report A clean, branded copy to share with your team or client.
Free PDF report

Where should we put your name on the report?

Your PDF downloads straight away. Your tool data never leaves your browser.

Jobair Mahmud, Web Analytics & Tracking Architect
Tool Creator

Jobair Mahmud

Founder & Tracking Architect

100% Top Rated
5.0 / 5.0

Seeing duplicate purchases in Ads Manager?

I rebuild Pixel + Conversions API setups so every purchase is counted once, with shared event IDs and a verified test in Events Manager.

Fix duplicate conversions →

How to use the Meta CAPI Deduplication Checker

When the Meta Pixel and the Conversions API both send the same purchase, Meta needs to know it is one purchase, not two. It decides by comparing event_name and event_id. This checker shows whether your browser and server events would be treated as one event or counted twice.

Step by step

  1. Copy the event name and event ID from your browser Pixel event (Meta Pixel Helper or the network tab shows both).
  2. Copy the same two values from the matching server event (your server GTM preview or backend log).
  3. Run the check and read which conditions pass and which fail.
  4. Confirm in Events Manager → Test events: the browser and server events should appear with the server one marked as deduplicated.

How to read your result

All checks pass

Matching event name and event ID: Meta keeps one event. Check a few real orders to be sure the ID is the same on every purchase.

Event ID differs

Meta counts both events, so reported purchases and ROAS are inflated. The ID must be generated once and reused for both events.

Event name differs

Even with the same ID, "Purchase" and "purchase" are different events. Use Meta's standard event names exactly.

Common mistakes

  • Generating a new random ID on the server instead of passing the browser's ID along.
  • A platform integration and a manual GTM Pixel both firing, which creates duplicates CAPI can't fix.
  • Using a timestamp as the event ID, so retries get a different value.

Questions

What is the best value to use as event_id?

For purchases, the order number works well because it is unique and available in both the browser and the server. For leads, generate a random ID when the form is submitted and send it with both events.

How long does Meta look for a duplicate?

Meta deduplicates browser and server events with matching event name and event ID received within 48 hours of each other.

Seeing duplicate purchases in Ads Manager?

I rebuild Pixel + Conversions API setups so every purchase is counted once, with shared event IDs and a verified test in Events Manager.