Meta Pixel and Conversions API Setup
The Meta Pixel tracks actions in the browser. The Conversions API sends the same events from your server, which survives ad blockers and browser limits. Run both, deduplicate with a shared event ID, and add CRM outcomes so Meta learns which leads turn into revenue.
Do you need both the Pixel and the Conversions API?
Yes, for most advertisers. Browsers and blockers stop some Pixel events from arriving. The Conversions API sends events server to server, and Meta recommends using it together with the Pixel (Meta developer docs). Better data means better optimization in Advantage+ and more accurate reporting.
// Browser: Meta Pixel event with an event ID
fbq('track', 'Lead', {}, { eventID: 'lead-8c21' });
// Server: same event sent through the Conversions API
{ "event_name": "Lead", "event_id": "lead-8c21",
"action_source": "website", "user_data": { "em": ["<hashed email>"] } }How does deduplication work?
When the same event arrives from the browser and the server, Meta matches them on event name and event ID and counts it once. Generate the ID in the browser, pass it to your server with the form data, and send it on both. Without a shared ID, conversions are double counted and optimization goes wrong.
How do you set it up?
- Partner integration: Shopify, WordPress and many site builders connect the Conversions API in a few clicks.
- Server-side tagging: a server container in Google Tag Manager can send events to Meta. See server-side tracking.
- Direct API: your developers send events from the backend, the most control.
- CRM events: send qualified and won stages so Meta learns lead quality. See Meta lead ads.
What about consent and privacy?
Only send events you have permission to send. Hash personal data such as email before it leaves your server, or let the partner integration do it. Respect consent choices from your cookie banner; in GTM that is handled with consent mode. Privacy rules differ by region, including Quebec’s Law 25; see consent and privacy for analytics. Event naming should follow your event tracking plan.
Measure revenue, not form fills.
The most valuable event you can send Meta is the one closest to money.
What should you check?
- Pixel installed on every page, with standard events on key actions.
- Conversions API sending the same events with matching event IDs.
- Event Match Quality reviewed in Events Manager.
- Test events verified with the Test Events tool.
- Qualified-lead events flowing from the CRM within a few days of the lead.
Budget for testing comes from Meta Ads cost.
Frequently asked questions
What is the Meta Pixel?
A JavaScript snippet that tracks visits and actions on your website for Meta ads.
What is the Meta Conversions API?
A way to send conversion events from your server to Meta, which works around browser limits and ad blockers.
Do I need both the Pixel and the Conversions API?
Meta recommends using both, deduplicated with a shared event ID.
How does Meta deduplicate events?
By matching the event name and event ID sent from the browser and the server.
Can I send CRM data to Meta?
Yes. Send qualified, opportunity or won events so Meta optimizes for leads that become revenue.
Does the Conversions API need a developer?
Not always. Many platforms offer a partner integration. Custom setups use server-side tagging or a direct API.
Sources & further reading
Ad platforms change quickly. These sources let you check the dated facts directly. Ads shown are mock-ups for a fictional advertiser.