Setting up Meta Pixel and Conversions API the right way
Why browser tracking alone is no longer enough, and how to combine Pixel and Conversions API for reliable data.
By the AdPlus Services team
Meta's ad delivery depends on conversion data. If your tracking misses purchases or leads, the algorithm optimises for the wrong people and your reported results look worse than reality. Getting tracking right is often the quickest win in a Meta account.
Pixel and Conversions API do different jobs
The Meta Pixel is a piece of code that runs in the visitor's browser and sends events such as PageView, Lead and Purchase. Browser tracking can be blocked by ad blockers, privacy settings and short cookie lifetimes. The Conversions API (CAPI) sends the same events from your server, which is more reliable. Meta recommends using both together.
Deduplicate events
When the Pixel and CAPI both send the same purchase, Meta needs to know it's one event, not two. Send the same event name and a shared event ID from both sources so Meta can deduplicate them. Without this, conversions can be double counted.
Send good customer information
Meta matches server events to people using customer information such as email address and phone number, which are hashed before sending. Better matching means better attribution and optimisation. Check the Event Match Quality score in Events Manager, and improve it by passing the parameters you legitimately collect, with appropriate consent.
Choose the events that matter
- Lead: when a form is submitted successfully, not when the form page loads
- Purchase: with value and currency so you can measure return on ad spend
- CompleteRegistration, Contact or Schedule where they reflect real business steps
- Avoid optimising for events that don't connect to revenue
Ways to set up CAPI
There are several routes. Platforms such as Shopify and WooCommerce offer built-in or plugin integrations. Google Tag Manager server-side containers give more control. Meta's Conversions API Gateway is another option for businesses without developer time. Choose based on your platform and how much flexibility you need.
Test before you rely on it
Use the Test Events tool in Events Manager to trigger events from your site and confirm they arrive from both the browser and the server, with matching event IDs. Then watch the diagnostics tab for warnings about duplicates, missing parameters or domain issues.
Verify your domain and configure events
Verify your website domain in Business Settings and review which events are prioritised for optimisation. These small admin steps prevent many reporting problems later.
