On this page
What the Pixel and Conversions API do
The Meta Pixel is a piece of code on your website that sends events from the visitor’s browser to Meta: page views, leads, purchases and so on. Browser restrictions, ad blockers, cookie consent choices and slow pages mean some of those events never arrive.
The Conversions API sends events from your server directly to Meta. Running both, with deduplication so the same event is not counted twice, gives Meta a more complete picture. That helps reporting, but more importantly it helps delivery: campaigns optimise on the events they receive, so missing events mean weaker optimisation.
Which events to send
Meta provides standard events such as Lead, Contact, Schedule, AddToCart, InitiateCheckout and Purchase, and allows custom events for anything else. We map events to real business actions: a Lead fires only after a successful form submission, a Purchase only after payment is confirmed, and a Contact when someone taps a WhatsApp or call button. Clear, honest events make both reporting and optimisation more dependable.
Signs your tracking needs work
- Meta reports far fewer leads or purchases than your CRM or store shows.
- Events Manager shows warnings about duplicate events, missing parameters or low match quality.
- Your “Lead” event fires on page load or on a button click rather than a real submission.
- You rely on WhatsApp enquiries or phone calls that are not tracked at all.
- Your website was rebuilt and nobody checked whether tracking survived.
What’s included
- Audit of current Pixel events, parameters and Events Manager diagnostics.
- Event plan: which standard and custom events represent real business actions for you.
- Pixel installation or cleanup, usually through Google Tag Manager.
- Conversions API setup through a platform integration (such as Shopify or WooCommerce), a gateway, or a direct server integration for custom sites.
- Event ID deduplication between browser and server events.
- Customer information parameters, hashed as required, to improve Event Match Quality.
- Domain verification and event configuration where needed.
- Testing with the Test Events tool, plus a short document explaining each event.
How we set it up
- Map the journey. List every action that matters: form submit, WhatsApp click, add to cart, checkout, purchase, booking.
- Choose the method. Native platform integration for common stores, or custom server-side code for bespoke sites and apps, which we can build.
- Implement. Browser and server events are sent with matching event names and IDs.
- Test. Events are checked live in Events Manager to confirm they arrive, deduplicate and carry the right parameters.
- Improve match quality. Where consent allows, customer information such as email or phone is sent hashed to improve matching.
- Document. You get a plain record of each event and what triggers it.
Sending CRM and offline events
For lead-based businesses, the most valuable event often happens outside the website: a lead becomes qualified, a site visit is completed, a consultation is booked, or a deal closes. The Conversions API can accept these events from your CRM or backend, so Meta can learn what a good lead looks like instead of only counting form fills.
Timeline, cost and privacy
A standard e-commerce setup through a native integration is usually quick. Custom websites, multiple domains or CRM-based events take longer because server code and testing are involved. Cost depends on the number of events, the platform and whether custom development is required.
Customer data sent to Meta is hashed and should only be sent where your privacy policy and consent approach allow it. We will point out where consent handling needs attention, but your legal obligations should be confirmed with your own adviser.
Common tracking mistakes
- Pixel and Conversions API both sending events without deduplication, doubling counts.
- Installing the Pixel twice through a plugin and a theme.
- Using page views of a thank-you page that people can reach without converting.
- Sending purchases without value or currency.
Frequently asked questions
Do I still need the Pixel if I set up the Conversions API?
Meta recommends using both. The Pixel captures browser behaviour and audiences, while the Conversions API fills gaps from the server side. Deduplication prevents double counting.
What is Event Match Quality?
It is Meta’s score for how well the customer information in your server events can be matched to Meta accounts. Better matching generally helps attribution and delivery.
Does it work with Shopify and WooCommerce?
Yes. Both have integrations that support the Conversions API. We check the configuration and event parameters rather than assuming the default is correct.
Can you track WhatsApp enquiries?
Clicks on WhatsApp buttons can be tracked as events, and conversations from Click-to-WhatsApp ads are reported in Ads Manager. Qualified outcomes can be sent from your CRM.
What is a Conversions API Gateway?
It is a Meta-supported option for sending server events without writing custom server code, hosted in your own cloud account. It suits some sites; custom integrations suit others.
Talk to us about meta pixel & conversions api setup
Server-side tracking so conversions still get attributed after browser restrictions.