If you run Facebook lead gen ads, you've probably had this conversation: the dashboard says cost per lead is down, lead volume is up, the ad set is "performing." Meanwhile, your sales team is on the other end going, "These leads aren't converting." Or your client is asking why the pipeline doesn't reflect the numbers.
The pattern shows up across lead gen accounts again and again. Most advertisers are optimizing their campaigns against the wrong outcome—and Meta has no way to tell them.
The fix is Meta's Conversions API for CRM (CAPI for short), wired up through Zapier. Don't be intimidated! The setup is more accessible than it sounds. The thinking behind which events to send is where most teams get it wrong.
Here's how to think about it, and the playbook to put in motion right now.
Table of contents
What Meta is actually seeing right now
A typical Meta lead gen setup sends one signal back to the platform: Someone submitted the form. That's it. Whether they were a tire-kicker, competitor, bot, or your next biggest customer, Meta sees the same thing. A lead.
So the algorithm goes and finds more people who look like form-fillers. Not buyers, or even qualified leads—just form-fillers.
Without those downstream signals, Meta has no idea whether a lead progressed, stalled, or ever converted to revenue. You're paying Meta to optimize for the first thing it can see, and hoping the rest works out.
The good news: The data Meta needs to do better already exists. It's sitting in your CRM.
What CAPI for CRM does, in plain English
Conversions API is Meta's server-to-server pipe. Instead of relying only on the pixel firing in someone's browser, you send events directly from your systems to Meta. CAPI for CRM is the version designed for the moment after the lead lands in your CRM, like when a deal stage changes, an appointment is booked, or a sale closes.
Once those events are flowing back, Meta can do something it couldn't before: connect the people who became actual customers to the ads they originally saw. From there, the optimization shifts. You can point Meta at the audience that matters—people who progress to qualified or actually buy, and not just fill out forms.
According to Meta, advertisers using CAPI for CRM see roughly 21% lower cost per quality lead on instant form campaigns and 9.5% lower on website form campaigns on average. Your mileage will vary based on your funnel and how much downstream signal you can actually feed back.
The three events worth wiring up first
Jared Weiss, a Zapier solution partner at Matix Flows who's set up CAPI for dozens of teams, has a baseline he checks every time he audits an account: Are these three foundational events firing? If not, that's where he starts.
1. New lead event. This fires when a new lead lands in your CRM. This is the entry point—the moment your CRM knows about the person, regardless of whether they came from an instant form, a website form, a chatbot, or somewhere else.
2. Funnel event. This fires when the lead progresses through a meaningful stage in your pipeline. For a home services company, that might be "appointment booked." For a B2B SaaS team, it could be "demo completed." For a gym franchise, it might be "intro class attended." We'll come back to how to pick this one in the next section, because it matters more than the others.
3. Purchase event. This fires when revenue happens, like a contract is signed, a payment is processed, or a membership starts. For eCommerce this is straightforward, but service businesses will need to decide what counts as "purchased" and stay consistent.
These three events are the floor, not the ceiling. Once these are stable, you can layer in more granular signals, like second-call scheduled, proposal accepted, and repeat purchase. But if any of the three is missing, the loop has a hole in it.
How to pick the funnel event that drives optimization
This is the section worth slowing down on because it's where most accounts go sideways.
You'll be tempted to optimize Meta against your final outcome—the sale. Don't. Here are two reasons why:
Meta's attribution window for quality events is 28 days. If your average sales cycle to closed-won is 60 days, the closed-won event will fire outside the window for most of your leads. Meta won't be able to attribute it back, and the optimization signal weakens.
The event needs to happen often enough to learn from. If only 5% of your leads ever hit the stage you picked, Meta doesn't get enough data to learn what those people look like. A useful rule of thumb from Meta's optimization guidance is to pick a stage that's completed by roughly one-third to one-half of your leads. It's frequent enough for the algorithm to learn, but rare enough to mean something.
The right funnel event usually sits in the middle of your pipeline (that means not the first form fill or the final invoice. For a lot of accounts, that's something like "qualified" or "discovery call completed." Find the stage in your CRM that's both predictive of revenue and happens within 28 days of the lead coming in. That's your optimization target.
Connecting Facebook Conversions to your CRM with Zapier
The Facebook Conversions integration on Zapier has pre-built templates for common CRMs like Salesforce, HubSpot, Pipedrive, ClickFunnels, Google Sheets, and webhook-based custom setups. These templates make it easy to get started, but you can also build your own automated workflows from scratch.
Here's a brief overview of how to set up your first few Facebook Conversions Zaps.
Confirm permissions in Meta Business Manager
In the Meta Business Suite, click All tools in the left-hand menu and go to the Events Manager tab. Then click the big + sign in the Events Manager navigation toolbar.
Choose the kind of conversion data you want to track. From the Select a partner menu, click Zapier. Meta will prompt you to connect your Zapier account. From there, you can connect your CRM with Meta.
Build Zap 1: Add lead events to your CRM
Go to the Zap editor, and start a new Zap. For the trigger step, choose your CRM from the list of apps, and select the equivalent of "New lead" as your trigger event. You'll also need to connect your CRM account to Zapier, if you haven't already. Then click Continue.
Note: It's always a good idea to test your trigger before setting up the action step!
For the action step, choose Facebook Conversions for the app and Send lead event for the action event. Then click Continue.
Next, you'll need to do a bit of data mapping for the lead's email address, phone, first name, last name, and unique contact ID.
You'll definitely want to test your action step to make sure it's working as intended before clicking Publish.
You can also use a Zap template to get started—they come preconfigured, so all you need to do is connect your CRM and Meta accounts. Here are a few of some of the most popular CRMs:
Send funnel events to Facebook Conversions from Pipedrive
Send funnel events to Facebook Conversions from HubSpot
Send funnel events to Facebook Conversions from Salesforce
Build Zap 2: Add funnel events to your CRM
Similarly to the previous Zap, select your CRM as the trigger app and Deal stage updated (or its equivalent, depending on your particular CRM) as the trigger event. Click Continue.
You'll then need to specify the type of deal stage you want to track—in this example, we've selected New deal.
For the Zap's action step, choose Facebook Conversions as the app and Send funnel event as the action. You'll need to do a little data mapping again to specify exactly what deal information you want to send back to Meta. Then test your Zap and, if everything works as expected, click Publish to turn it on.
Just like the previous use case, you can use a pre-made Zap template to get started even faster:
Update Facebook Conversions leads when deal stages are updated in Pipedrive
Send Facebook Conversions funnel events for new or updated Zoho CRM contacts
Build Zap 3: Add purchase events to your CRM
Now it's time to set up your final Zap. Like the others, you'll want to select your CRM as the trigger app and the equivalent of Closed won as the trigger event.
For the action step, Facebook Conversions is the right app and Send purchase event is the correct action. A little more data mapping, a test to make sure everything works, and voila—you're tracking conversions automatically!
Here are a couple of Zap templates to help you get started quickly:
Create Facebook Conversions purchase events from new Pipedrive deals
Create purchase events in Facebook Conversions from new contacts in list in HubSpot
Finally: Watch it for 30 days
Plan to check the new account twice a week for the first month, looking at match rate, error rate, and formatting consistency. CAPI takes a few days to digest the data after each run, so don't panic if Events Manager looks quiet on day one.
Five tips for boosting your match rate
These are the issues that come up over and over when teams troubleshoot their CAPI implementations. None are dramatic on their own—they just compound. Here's what to look out for.
1. Leave event_time blank when you set up your Zap. If you fill in a custom timestamp, you'll eventually send one outside Meta's allowed window and the event will fail. Leaving it blank tells Zapier to use the moment the Zap fires, which is what you want for streaming events.
2. Reformat fields if needed. Your CRM and Facebook Conversions may format data like phone numbers or names differently.
To make sure your data is formatted in a way Meta can understand, you can use Zapier's inline formulas to reformat data without a separate Formatter step. Just add lowercase(trim(...)) in the data fields you need to reformat.
3. Reformat phone numbers and order values. CRMs love to store phone numbers as (555) 123-4567 and order value as $1,250.00 USD. Meta wants +15551234567 and 1250.00.
Once again, you can use an inline formula to extract the phone number or order value without adding an extra Formatter by Zapier step.
4. Separate your pixels for dedup if you can. If you're sending events from both your website pixel and your CRM, deduplication gets complicated fast. Jared's hack: Keep one pixel for website events and a separate one for CRM events. Cleaner reporting, easier debugging, and Meta's optimization knows which signal it's looking at.
5. Select the offline events pixel at the ad level. It's easy to set up CAPI correctly and forget the last step: opening each ad and confirming the offline events pixel is checked under tracking. If it's not, you've built the loop but it's not connected to the campaigns you're trying to optimize.
How to tell it's working
Here are two places to watch:
In Meta Events Manager, open the Overview tab on the data set. You should see your lead, funnel, and purchase events listed with recent receipt times. Give it three to five days after going live before you start judging—the pixel needs to digest. Once data is flowing, Meta will eventually prompt you to configure the funnel and pick which stages count as the strongest signal. Take that prompt seriously; it's how Meta learns the priority order.
In Zapier, check your Zap History to make sure your three Zaps are running. You're looking for a high success rate, no recurring errors on a specific field (which usually means a data formatting issue), and run frequency that matches your real lead flow.
If lead volume in your CRM is 200 a week and your new lead Zap only ran 80 times, you have a trigger problem before you have a CAPI problem.
A simple reporting view works best: cost per lead and lead volume, plotted across the period that includes the CAPI go-live date. You're looking for the curves to bend in the right direction over four to six weeks, not for an overnight miracle.
Where to start
If you do nothing else, do this:
Pull your Meta lead gen account up and look at what conversion event your campaigns are optimized against today. If it's "lead" or "form fill," you have room to upgrade.
Map your CRM pipeline on paper. Mark the stage that sits within 28 days of lead creation and is completed by roughly a third to half of leads. That's your funnel event candidate.
Build the new lead Zap first. It's the lowest-risk way to learn the workflow before you wire up the rest.
You don't need a developer. You don't need a six-month rollout. You need three Zaps, an hour of focused setup, and a month of monitoring.
The leads were always going to come in. The question is whether Meta can tell which ones became customers—and find you more of those.
Want to see the build live?
Zapier hosted a deep-dive webinar on this with Heriberto Salcedo (product marketing manager at Meta) and Jared Weiss of Matix Flows, including a live Zapier build and audience Q&A. Watch the on-demand recording.
