Social media · Tracking
The Pixel tracks from the browser, the Conversions API from your server. Running both, deduplicated, gives Meta the data it needs to find you customers.
Pixel and server events together
Deduplicate with a shared event ID
Aim for Good event match quality
Tell us what you need and we’ll get back to you. Or book a free 30-minute call. Or call 954-539-5678.
The Meta Conversions API (often called CAPI) sends conversion events such as leads and purchases from your server, website platform or CRM directly to Meta. The Meta Pixel sends the same kind of events from the visitor’s browser. Meta’s best-practice guide recommends using both and sending the same events through each: the Pixel catches browsing behavior on the page, while the Conversions API can still report events the Pixel loses, for example to connection problems, page loading errors or browser restrictions. When both send the same event, Meta deduplicates them using a shared event ID.
For most small businesses, setup takes an afternoon through a built-in integration on Shopify, WooCommerce, or another platform. Custom sites need a developer or Meta’s Conversions API Gateway. The result is more complete conversion data, which helps Meta’s delivery system find people who actually buy or inquire.
JavaScript code in the head of your web pages. It loads in the visitor’s browser and reports page views and actions, using cookies to match visitors to Meta accounts. Easy to install, but it can be blocked.
A server-to-server connection. Your site or platform sends events to Meta’s endpoint with customer information, such as a hashed email, to match the event to a person. Not affected by browser blocking.
Meta’s developer documentation says server events sent through the Conversions API are processed like events sent using the Pixel, linked to the same dataset, and usable for measurement, reporting and optimization. It also says you must have a Pixel ID to use the Conversions API, and to use the same Pixel for browser and server events if you already have one.
If the Pixel and the server both report the same purchase, Meta needs to count it once. Meta’s documentation describes the main method: the Pixel’s eventID must match the Conversions API’s event_id, and the Pixel’s event name must match the server’s event_name. Events are deduplicated only if they arrive within 48 hours of the first one. When both copies arrive, Meta generally keeps the one received first.
There is a fallback that matches on event_name plus the fbp cookie or an external ID, but Meta notes it generally only works when the browser event arrives first. A shared event ID is the reliable method. Platform integrations handle this for you; custom builds must generate one ID per action and send it through both channels.
Send the few events that match your business goals, with the same names in the browser and on the server:
Book a free 30-minute call. We look at your Pixel and conversion setup with you and tell you what we would fix first. No obligation. Pick a time.
Meta matches server events to people using customer information parameters. The more accurate parameters you send, the better the match.
Only send data your privacy policy covers and your customers agreed to. Health, financial and legal businesses should be especially careful about what events and data leave their site. This is general information, not legal advice; confirm with counsel for regulated data.
JLB USA has helped growing businesses with web design, marketing and IT for more than 15 years, with 500+ clients and 1,000+ projects. We install and audit the Pixel and Conversions API, connect CRM events through our systems integration work, and run the campaigns that use the data. See our paid advertising services and our Shopify versus WooCommerce comparison if you are choosing a store platform.
Book it now · Free
Pick a time. We look at what you have now with you and tell you what we would change first. No obligation.
Prefer to talk now? Call 954-539-5678, or send the form and we’ll contact you.
Meta recommends both. The Pixel captures browser activity and the Conversions API fills gaps when the browser blocks it. Meta deduplicates events sent through both.
Meta does not charge for it. Costs come from setup time, apps, or hosting if you use the Conversions API Gateway in your own cloud account.
In Events Manager, open your dataset’s settings and use the generate access token link in the Conversions API section. Only people with developer permissions for the business see it.
Meta scores it out of 10 and treats a rating of Good or Great as optimal. Sending more accurate customer information, such as hashed email and phone, usually raises it.
Usually the browser and server events have different event IDs or names, or there are two Pixels on the site. Fix the IDs so they match and remove duplicate Pixels.
