On this page
Short answer: The Meta Conversions API (CAPI) sends conversion events from your server or CRM straight to Meta, instead of relying only on the Pixel in the visitor’s browser. For lead-generation businesses it does two jobs: it recovers leads the Pixel misses because of ad blockers and browser privacy settings, and it lets you tell Meta which leads became qualified or paying customers, so Meta can find more people like them. Run it alongside the Pixel, send the same event ID from both so Meta removes duplicates, and pass back lead stages from your CRM.
Last updated: 15 November 2026.
Pixel vs Conversions API
| Factor | Meta Pixel | Conversions API |
|---|---|---|
| Where it runs | In the visitor’s browser | On your server, CRM or a tag server |
| Blocked by ad blockers | Often | No |
| Can send offline events | No | Yes, such as a lead turning into a booking |
| Setup effort | Paste a code or use a plugin | Integration, partner app or developer work |
| Best used | Together with CAPI | Together with the Pixel |
Why it matters more for lead-gen than for e-commerce
An online store sees the sale on its website. A travel agency, clinic or real estate business usually closes the sale later, on a call, on WhatsApp or in person. Meta never sees that sale unless you send it back. Without that signal, Meta optimises for whoever fills forms fastest, which is often not who buys. That is the gap we describe in cost per lead vs cost per booking.
Which events should a lead-gen business send?
| Event | When to send it |
|---|---|
| Lead | A form is submitted on your website or an instant form arrives |
| Contact | Someone clicks to call or starts a WhatsApp chat from your site |
| Schedule | An appointment, site visit or callback is booked |
| Qualified lead (custom) | Your team marks the lead as genuine and in budget |
| Purchase | The customer pays, with the value in rupees |
Keep the list short. Five clean, correctly timed events are worth more than twenty noisy ones.
Conversion leads: optimising for leads that buy
If you run instant form campaigns, Meta can optimise for conversion leads instead of the cheapest form fills. To use it, your CRM sends Meta each lead’s stage (for example, contacted, qualified, booked) through the Conversions API, matched by the lead ID Meta gave you. Over time Meta learns which kinds of people move down your pipeline and shows your ads to more of them. You need a steady flow of stage updates for this to work, so it suits businesses that get leads every day.
How to set up the Conversions API
- Check your Pixel first. In Events Manager, confirm the Pixel fires on the right pages and events.
- Pick a setup route. A partner integration in Events Manager (for WordPress, Shopify and many CRMs), Meta’s Conversions API Gateway, server-side Google Tag Manager, or a direct integration by your developer.
- Send customer information. Include hashed email and phone, plus the browser IDs (fbp and fbc) when the event starts on your website. More matched information means a higher Event Match Quality score in Events Manager.
- Deduplicate. When the Pixel and CAPI send the same event, give both the same event name and event ID so Meta counts it once.
- Test. Use the Test Events tool in Events Manager, then watch the Overview tab for a few days for errors and duplicates.
- Add CRM stages. Connect your CRM so qualified leads and bookings flow back as events.
What about leads that come in on WhatsApp?
Click-to-WhatsApp ads start conversations, not form submissions, so there is no website event to track. Meta has a version of the Conversions API for business messaging that lets you report outcomes such as a lead or purchase that happened in the chat. Keep your WhatsApp conversations and lead stages in one place, such as Adwix Connect for chats and Adwix Atlas for travel bookings, so you have clean data to send back. The ad side is covered in Click-to-WhatsApp ads in India.
Common mistakes
- Sending the same Lead event from the Pixel and CAPI without a shared event ID, which doubles your reported leads.
- Sending events with no customer information, so Meta can’t match them to people.
- Firing a Purchase event when a form is submitted, which teaches Meta the wrong goal.
- Sending lead stages once and then stopping.
- Collecting phone numbers for tracking without telling people in your privacy notice.
Keep learning
Frequently asked questions
Do I still need the Meta Pixel if I use the Conversions API?
Yes. Meta recommends running both. The Pixel captures browser activity, the Conversions API fills the gaps and adds offline events, and a shared event ID stops double counting.
Is the Meta Conversions API free?
Meta doesn’t charge for it. You may pay for a partner app, a tag server or a developer’s time to set it up.
What is a good Event Match Quality score?
Higher is better. Meta rates it out of 10 in Events Manager. Sending hashed email, phone and browser IDs with each event usually raises it.
Can the Conversions API track WhatsApp leads?
Meta offers a Conversions API for business messaging that can report outcomes from chats, such as a lead or purchase. It needs your messaging and CRM data to be recorded in a structured way.
Want your tracking checked? Book a free 30-minute call and we’ll look at your Events Manager with you.
We run the ads, the WhatsApp follow-up and the pipeline.
Book a free 30-minute strategy call. Bring your numbers and we'll show you what we'd change.



