Meta Pixel and Conversions API counting leads or purchases twice
Events Manager or Ads Manager shows roughly twice as many leads or purchases as the CRM or store, usually starting when the Conversions API was added or a plugin was installed.
Steps checked against the platforms' documentation on November 20, 2026.
Quick answer
Meta only removes a duplicate when the browser and server events have the same event name and the Pixel's eventID matches the Conversions API event_id, within 48 hours. If either side is missing the ID, generates its own, or uses a different name, both events count. Check the Event Deduplication tab in Event Details first, then compare the two payloads in Test Events.
1. The event ID is missing on one side, or each side generates its own
Deduplication needs one ID per conversion, shared by the browser and the server. A common mistake is generating a random ID in the browser tag and another one in the server tag, so they never match.
How to check
- 1In Events Manager, open the event, click
Event Detailsand open theEvent Deduplicationtab. CheckRate of Events DeduplicatedandRate of Deduplication Key Usage. - 2Complete a test conversion with
Test Eventsopen and compare the browser and server events. Note the event ID on each. - 3In Google Tag Manager
Preview, check the Pixel tag passeseventIDas the fourth argument, for examplefbq('track', 'Purchase', {value: 12, currency: 'USD'}, {eventID: 'EVENT_ID'}).
How to fix
- 1Generate one ID per conversion, push it to the data layer, and read that same value into both the Pixel tag (
eventID) and the Conversions API payload (event_id). - 2For orders, an order ID is a natural choice. For leads, use a submission ID created once when the form succeeds.
- 3Retest and confirm the deduplication rate rises over the following days.
2. The event names do not match exactly
Meta requires the Pixel event to match the Conversions API event_name. A browser Lead and a server lead, or a Pixel Lead and a server generate_lead, are treated as different events.
How to check
- 1In
Test Events, compare the event names from the browser and the server character by character. - 2Check server-side Google Tag Manager or the plugin's event mapping for renamed or lowercased events.
How to fix
- 1Use exactly the same name on both sides. For standard events, use Meta's spelling, such as
Lead,PurchaseandCompleteRegistration. - 2Meta's docs do not say matching is case-insensitive, so treat case as significant.
3. The server event arrives more than 48 hours after the browser event
Meta deduplicates only events received within 48 hours of the first event with a given event_id. Setups that send the server event later, for example after a CRM status change or a nightly batch, fall outside that window.
How to check
- 1In
Event Details, open theEvent Freshnesstab and look at the average delay for server events. - 2Check whether the server event is sent at the moment of conversion or by a scheduled job.
How to fix
- 1Send the server copy of the event in real time, at the same moment as the browser event.
- 2If you also want to send a later CRM milestone, such as a qualified lead, give it its own event name rather than resending
Lead.
4. Two tools are sending the same event from the same side
A Shopify sales channel or WordPress plugin sends Pixel and server events, and someone also added the same events through Google Tag Manager or theme code. Each tool generates its own IDs, so nothing deduplicates. Meta's Data Advisor documentation lists duplicate Pixel code on a page as a common issue.
How to check
- 1Open the conversion page with Meta Ads Data Advisor and look for the same event firing more than once, or for duplicate Pixel warnings.
- 2In the Pixel's
Overview, checkConnection Methodfor more integrations than you expect. - 3List every place that can send events for this Pixel: platform integrations, plugins, theme code, Google Tag Manager containers and server-side containers.
How to fix
- 1Pick one owner for each event on each side, browser and server, and disable the others.
- 2If you keep the platform's built-in integration, let it handle both Pixel and Conversions API events and remove the manual tags.
- 3Also check the event does not fire twice in the browser, for example on the button click and again on the thank-you page, or again when the thank-you page is reloaded.
5. The setup relies on fbp or external_id instead of an event ID
Meta can also deduplicate by matching the event name with fbp and/or external_id, but its docs say this generally only works when the browser event is received first and the server event second. When the server event arrives first, the duplicate stays.
How to check
- 1In
Test Events, check whether events carry an event ID at all, or onlyfbpandexternal_id. - 2Check
Rate of Deduplication Key Usagein theEvent Deduplicationtab for low overlap between browser and server keys.
How to fix
- 1Add a shared
event_idandeventIDto every event sent through both channels. Meta recommends the event ID method. - 2Keep sending
fbpandexternal_idas well, since they also help matching.
Stop it happening again
- Create the event ID once, at the moment of conversion, and pass it to every tag that sends that event.
- Keep a written list of which tool sends each event, browser and server, for every client.
- After installing any Meta plugin or platform integration, check whether manual tags for the same events need removing.
- Review the
Event Deduplicationtab monthly and after any tracking change.