Your Facebook campaign is bringing in enquiries. Some people ask for a quote, some book an appointment, and others never answer. Ads Manager can show the form submissions, but that alone does not tell Meta which enquiries were worth your time.
Meta Conversions API, usually called CAPI, can send later outcomes from your CRM back to Meta. With LeadSavvy Pro, you keep working the lead through your pipeline and the configured integration reports eligible stage changes. This guide explains that workflow, how it differs from website tracking, and what to check when events are missing.
What is the Meta Conversions API?
Conversions API is a way for a business system to send event data directly to Meta. An event describes something that happened: for example, a customer completing a purchase or a lead reaching a meaningful stage in your sales process.
People sometimes search for “Meta Conversion API” or “Facebook CAPI”. Meta's product name is Conversions API. Website events and CRM lead outcomes both use server-side reporting, but they answer different questions and need the right setup for their purpose.
Website tracking and CRM conversion tracking are different jobs
The Meta Pixel reports activity from a website, such as a visitor viewing a page or completing a form. Website CAPI can report server-side events alongside it. When the same action is reported through both channels, deduplication matters.
For Facebook Instant Forms, the sales conversation often happens elsewhere. Someone submits an enquiry inside Facebook, then speaks to you by phone, receives a quote and decides whether to buy. A website pixel cannot see that whole conversation. CRM CAPI supplies the later outcomes you record in your sales system.
- Lead capture: bring the original Instant Form enquiry into LeadSavvy Pro or Google Sheets.
- Follow-up: contact the prospect, keep notes and work the opportunity.
- CRM feedback: send supported pipeline outcomes back to Meta once the CAPI connection is configured.
These are separate parts of the workflow. A successful spreadsheet export does not prove that conversion feedback is working.
How LeadSavvy Pro connects Facebook leads to CRM outcomes
LeadSavvy Pro combines Facebook and Instagram lead capture, Google Sheets export and a visual sales pipeline. CRM CAPI is available on Grow and Scale. It is configured for the relevant bridge, so a business or agency can connect the appropriate lead source to its Meta dataset.
Imagine a local business receiving an enquiry from Alex about a quote. This is an example, not a claimed customer result:
- The enquiry arrives. LeadSavvy Pro retrieves the connected Instant Form lead. You can also send it to your Google Sheet.
- You see the notification. The iPhone app lets you open the enquiry and tap to call while you are away from your desk.
- You learn what Alex needs. Record the job, timing and next step in the contact's notes.
- You update the deal. Move it into a meaningful stage such as Qualified or Quote Sent when that outcome actually happens.
- The configured CAPI workflow reports the outcome. LeadSavvy sends an eligible CRM event associated with the original Meta lead. Check the event in Meta rather than assuming the stage change alone proves it was received.
This keeps conversion reporting close to the work you already do. You do not need to reconstruct the sales journey from a spreadsheet at the end of the month.
Use pipeline stages that mean something
Choose names your team understands: New Lead, Contacted, Qualified, Quote Sent and Won are examples. Decide what each stage means before using it as a reporting signal. “Qualified” should describe a genuine business milestone, not everyone who happens to answer the phone.
LeadSavvy derives CRM event names from pipeline stage names. Its workflow excludes stages configured as lost or abandoned outcomes. Editing a note or renaming a stage is not the same as a lead entering a new stage, and revisiting an already successfully reported lead/event combination does not create another successful event for that same combination.
If you use the LeadSavvy Pro ChatGPT integration through early access, you can review enquiries and notes, then update the relevant deal as part of the conversation. Check the record and outcome just as you would in the web or mobile app. Accurate pipeline use gives the reporting workflow useful information.
Set up CRM CAPI and verify a real outcome
Use the LeadSavvy Pro CRM CAPI setup guide for the current screens and connection steps. You will need the appropriate Meta dataset access, a Grow or Scale account, and the bridge you want to configure.
- Prepare the CRM dataset and connection details using the guide.
- Open the bridge's CAPI settings, enter the dataset ID and access token, and test the connection.
- Save the configuration for that bridge. Check each source separately if you have several Pages or clients.
- Work a suitable Meta-origin lead through a genuine eligible pipeline change.
- Check LeadSavvy's event result and the corresponding dataset in Meta Events Manager. Confirm the event name and the information Meta received.
A connection test checks the connection. It does not demonstrate that a real sales outcome has been matched to a lead or that a campaign is using that outcome for optimisation. Keep tokens out of screenshots and shared documents.
Why are CRM conversion events not showing in Meta?
The lead arrived in Sheets, but lead_status changes do nothing
Check which integration is responsible for sending outcomes back. Do not assume every Google Sheets connection watches a column called lead_status. LeadSavvy's CRM CAPI workflow responds to eligible deal-stage changes in LeadSavvy; editing a spreadsheet cell is not its trigger. Our Facebook leads to Google Sheets guide covers incoming delivery.
The connection test passed, but there is no outcome event
Confirm that settings were saved on the correct bridge, the lead is linked to the original Meta submission, and the deal actually entered an eligible stage. Check whether the same lead/event combination was already reported successfully. A contact edit alone is not a new milestone.
There is a failed event or a permission error
Check the destination dataset, token and access for that connection. Look at the recorded error before repeatedly changing settings. A copied endpoint URL is not an access token. Correct the specific problem and verify the next event; do not create artificial sales outcomes just to make a dashboard look active.
Meta received the event, but campaign results have not changed
Event receipt, event matching and campaign optimisation are different checks. Confirm that Meta can associate the outcome with the lead, then review the campaign's available optimisation settings and data requirements. Small volumes, inconsistent stages and weak enquiries can limit what the feedback tells you. CAPI does not guarantee better leads or a lower acquisition cost.
Meta Conversions API best practices: matching and deduplication
Event matching connects a reported outcome with the relevant person or lead. Accurate contact details and the original Meta lead identifier help maintain that connection. An accepted API request is not proof that Meta matched every event or attributed it to an ad.
Deduplication prevents the same business action being counted twice. If you report one website action through both Pixel and CAPI, the event name and shared event ID must identify that same action. Separate CRM milestones are different outcomes; do not describe a quote and a completed sale as the same event.
Use consistent stages, report real outcomes and review failures. More events are not automatically more useful events. Sending customer information through a server also does not remove your responsibility to handle it appropriately.
Where Zapier fits—and what to compare
Zapier can connect a CRM to Meta when you need automation across several systems. Its Facebook Lead Ads app is Premium and requires a paid plan for ongoing new-lead workflows. Compare the full workflow's task usage, not just the number of incoming enquiries. See our Zapier plan and task guide for the limits and the scope of its advertised Meta task promotion.
LeadSavvy Pro is a focused option when you want Instant Form capture, a pipeline, mobile follow-up and CRM outcome reporting together. Check the number of connected lead sources and the features on the current plans rather than comparing a basic lead-export plan with a full CAPI workflow.
Common questions about Facebook CRM CAPI
Do I need a website pixel for Facebook lead-form CRM outcomes?
A website pixel and CRM outcome reporting serve different purposes. Do not install a website pixel just to represent a phone conversation. If you also advertise a website, assess its Pixel and website CAPI setup separately.
Can CAPI recover missing Facebook leads?
CAPI reports events back to Meta. Incoming lead capture and recovery are separate features. If an enquiry is missing, check the source submission and delivery connection before investigating its later conversion event.
Will this stop people submitting low-quality enquiries?
No tool can promise that. CRM feedback can provide useful outcome information, but your offer, form questions, audience, first response and sales process still matter. Track reached leads, qualified opportunities and customers alongside cost per lead.
Start with a workflow you can maintain. Receive the lead, respond while the enquiry is fresh, record what happened and verify that the configured outcome reached Meta. Try LeadSavvy Pro, or follow the CRM CAPI setup guide if you already use Grow or Scale.