Expand Navigation HeaderCollapse Navigation Header
Create Ads from a Facebook Page
Beginner's GuideFeaturesBoost PostsPage LikesCall-to-ActionWebsite VisitorsWebsite PurchasesWebsite Purchases With Your CatalogAutomated Ads
Create Ads from Ads Manager
Create Campaigns, Ad Sets, AdsEdit CampaignsEvent AdsOffer AdsLead AdsDynamic CreativeCreative TipsMobile App AdsFacebook Ads Manager for ExcelBid StrategiesBudgetsDelivery
Create Ads from Instagram
Beginner's GuideAdvertising from InstagramInstagram Shopping
Create Ads from the Ads Manager App
Ads Manager App
Objectives
Brand AwarenessReachLead GenerationBrand ConsiderationMessagesDynamic AdsAutomotiveTravelCollaborative AdsConversions
Audiences
AudiencesCustom AudiencesLookalike Audiences
Formats
ImageCarouselCollectionInstant ExperienceVideo & SlideshowStoriesBranded Content
Placements
Placement OptimizationInstagramMessengerAudience NetworkMarketplaceFacebook In-Stream Video
Track Ongoing Campaigns
Track Ads in Ads ManagerAutomated Rules in Ads Manager
Ads Reporting
MetricsFacebook Ads Manager for ExcelAudience InsightsView Results & Run ReportsAnalyze Results
Optimization
Facebook Attribution
Events
Offline ConversionsApp EventsFacebook PixelConversions API
Experimentation
Experiment ConceptsA/B TestingExperiments ToolFacebook-Managed Tests
Payments Settings
Monthly Invoicing
Billing
How Billing WorksPayment MethodsSpending LimitsTaxesAbout Manual paymentsBudgets
Management Tools
Business ManagerUsers in Business ManagerAccounts in Business ManagerData Sources in Business ManagerSecurity and Safety in Business ManagerLeads CenterCatalogsCreative HubConnect Your WebsiteBrand SafetyAd Account PermissionsBusiness Suite
Policies
Ads About Social Issues, Elections or PoliticsPersonal HealthCryptocurrencyAdvertising Policy on Real Money Gaming and Gambling (RMG)Drug and Alcohol Addiction Treatment

Business Help Center

Business Help Center

About Deduplication for Facebook Pixel and Conversions API Events

Get help, tips, and more...
Last updated: Jan 29, 2021

About Deduplication for Facebook Pixel and Conversions API Events

The Facebook pixel and Conversions API let you share standard and custom events with us so you can measure and optimize ad performance. The pixel lets you share web events from a web browser, while the Conversions API lets you share web events directly from your server.

If you connect website activity using both the pixel and Conversions API, we may receive the same events from the browser and the server. If we know that the events are the same and therefore redundant, we can keep one and discard the rest. This is called deduplication.

Deduplication isn’t always necessary, it depends on how you set up your events. If you want to send web events using both the pixel and Conversions API, you have 2 setup options:

  • Share different events from the browser than from the server (deduplication isn’t necessary). For example, you share add to cart events from the browser, and purchase events from your server. Deduplication isn’t necessary in this instance because you aren’t sending redundant events from both the browser and the server.
  • Share the same events from both the browser and the server (deduplication is necessary). For example, you send the same purchase events from the browser as you do from the server. This may help recover events that can’t be counted by your pixel alone. If your redundant browser and server events aren’t deduplicated, you would see two purchases show up in your report (one sent from the browser and one sent from the server) when only a single purchase has actually occurred. Deduplication is necessary in this instance so that the same purchase doesn’t show up twice in your reporting.

For events to be deduplicated, you or your developer should add 2 event parameters that help us determine if the events are the same: the event name (for example, Purchase or AddToCart) and the event ID. Learn more about server event parameters on Facebook for Developers.

After you set up the event name and event ID parameters, we deduplicate all but the first event we receive if the events have the same event ID, have the same event name, are received by the same pixel ID and are received within 48 hours of the first event.

For example, we would deduplicate the following events:

  1. Redundant pixel events.

    We deduplicate pixel events with identical event and eventID parameters.

  2. Redundant server events.

    We deduplicate server events with identical event_name and event_id parameters.

  3. Redundant pixel and server events.

    We deduplicate pixel and server events that meet both of the following conditions:

    • The pixel's event matches the Conversions API's event_name.
    • The pixel's eventID matches the Conversions API's event_id.
  4. Redundant pixel and server events using fbp and/or External ID.

    We deduplicate pixel and server events that meet both of the following conditions:

    • The pixel's event matches the Conversions API's event_name.
    • The pixel's external_ID matches the Conversions API's external_ID.

    We also deduplicate pixel and server events that meet both of the following conditions:

    • The pixel's event matches the Conversions API's event_name.
    • The pixel's fbp matches the Conversions API's fbp.

You can check which events are deduplicated using the Test Events tool in Events Manager.

Was this information helpful?

More in this section: EVENTS

EVENTS |

Facebook Pixel