Sign in Start free trial
Facebook Conversion API CRM

Teach Facebook which leads
actually become customers.

A Facebook Conversion API (CAPI) CRM is a CRM that sends conversion events — like which leads became qualified or closed — from your sales pipeline back to Meta server-side, so Facebook optimises ad delivery for people who actually buy, not just people who fill out forms. Salesgem sends each pipeline stage change to Meta using the original lead's ID, so your campaigns learn from real sales outcomes instead of guessing from form fills.

Connect Meta account See it in action
Server-side, no ad blockers No developer needed SHA-256 hashed, privacy-safe
Conversion API events
Live
Salesgem CRM Pipeline stages
Meta Ads Optimise for buyers
Pipeline → CAPI events Server-side
Lead Contacted → Meta
Rohan K. · leadgen_id matched · 200 OK
just now
Lead Qualified → Meta
Priya S. · stage: marketing_qualified · 200 OK
18s
Deal Won → Meta (₹85,000)
Ananya R. · converted · value sent
51s
Lead Qualified → Meta
Tara D. · sales_qualified · 200 OK
2m
The problem

The Pixel can't see what happens in your CRM.

The Facebook Pixel tracks events in the browser with JavaScript — but browsers block it. iOS privacy settings, cookie restrictions and ad blockers prevent the Pixel from firing on a growing share of traffic. And even when it does fire, it stops at your website. It never learns whether a lead became a paying customer in your CRM.

  • Ad blockers and iOS kill browser signals — the Pixel silently fails on a significant share of users, under-reporting conversions.
  • The Pixel only sees the website — it can track form submissions, but never whether that lead was qualified or closed in your sales pipeline.
  • The Conversions API fills both gaps — server-side events aren't blocked, and they can report offline outcomes like a closed deal. Best practice is to use both together.
Signal comparison
Facebook Pixel (browser)
Blocked by iOS / ad blockers
Can't see CRM pipeline outcomes
Tracks on-site page views & clicks
Conversions API (server-side)
Not blocked — server to server
Reports offline CRM outcomes
Near-100% match via leadgen_id
Conversion Leads — funnel stages
Lead Ad submitted
Facebook captures lead + assigns leadgen_id
Contacted → event fired
Salesgem sends stage to Meta server-side
Marketing Qualified → event fired
Meta learns which ad produced warm leads
Converted → event fired (+ deal value)
Meta optimises toward revenue, not form fills
Conversion Leads optimisation

Let Meta optimise for buyers, not form-fillers.

Meta's Conversion Leads optimisation lets Facebook find and target people who actually convert into customers — but only if it receives your CRM's pipeline progression back through the Conversions API. Salesgem feeds Meta your funnel stages automatically so your campaigns learn from real sales outcomes.

  • Meta reports ~19% lower cost per quality lead for advertisers using Conversion Leads optimisation. (Meta's finding, based on early adopter data — not a Salesgem result.)
  • All four stages sent automatically — contacted, marketing qualified, sales qualified, converted — so Meta's model gets a complete picture of your funnel.
  • Needs ~200+ leads/month to learn well — below that, CAPI still improves attribution, but the algorithm has less signal to optimise with.
See Facebook Lead Ads CRM
How it works

How a CAPI CRM works, step by step.

From the moment a lead ad is submitted to a won deal reported back to Meta — Salesgem handles the full loop automatically.

01

Lead ad submitted

Facebook or Instagram Lead Ad form is filled. Meta assigns a unique leadgen_id to the submission.

02

Salesgem captures lead

The lead lands in Salesgem immediately, with the leadgen_id stored alongside the contact record.

03

Rep works the lead

As the rep moves the lead through pipeline stages, each change fires a server-side CAPI event to Meta with the original leadgen_id.

04

Meta learns & optimises

Meta matches events to the original ad click. The "converted" event can include deal value, so Meta optimises toward revenue — not just conversions.

Setup

Set up Facebook CAPI without writing code.

Setting up the Conversions API by hand means managing access tokens, building event payloads and deploying server code — the reason most teams never turn it on. Salesgem handles all of that infrastructure for you.

  • Connect your Meta dataset — paste your Pixel ID and system access token in the Salesgem settings screen. That's the only technical step.
  • Map your pipeline stages — choose which Salesgem stages correspond to Meta's funnel events (contacted, qualified, converted) using a dropdown. No JSON, no code.
  • Events fire automatically — once connected, every pipeline stage move triggers a CAPI event. No manual exports, no Zapier chains, no developer needed.
Start free trial View all integrations
CAPI setup — 2 steps
Step 1 — Connect Meta dataset
Pixel ID
1234567890123456
System Access Token
EAA••••••••••••
Step 2 — Map pipeline stages
Contacted→ Lead_Contacted
Sales Qualified→ Lead_Converted
Won→ Purchase
Events now firing automatically
Data handling — what gets sent
Hashed before sending (SHA-256)
Email address · Phone number · Full name
Meta never receives these in plain text.
Sent as-is (required for matching)
Meta leadgen_id — needed to tie the event back to the original ad click.
Connection
Server-to-server over HTTPS · Verified Meta Tech Provider
Privacy

Privacy-safe by design.

Every personal detail — email, phone, name — is hashed with SHA-256 before it leaves Salesgem. Meta never receives it in plain text; this is Meta's own standard requirement for all Conversions API implementations.

  • SHA-256 hashing on all PII — email, phone and name are one-way hashed. Meta uses the hash to match audiences; the original data isn't exposed.
  • Lead ID sent as-is — the Meta leadgen_id is sent in plain form because Meta needs it to match the event to the original ad click. It contains no personal information.
  • Salesgem is a Verified Meta Tech Provider — events are transmitted server-side over a secure connection, meeting Meta's data handling standards.
FAQ

Facebook Conversion API CRM — answered.

Got a question that's not here? Our team is happy to help.

Contact support
A Facebook Conversion API (CAPI) CRM is a CRM that sends conversion events from your sales pipeline back to Meta server-side — telling Facebook which leads became qualified or closed, not just who submitted a form. Salesgem sends each pipeline stage change (contacted, qualified, converted) to Meta using the original lead's ID, so your ad campaigns can optimise for the people who actually become customers.
The Pixel tracks events in the browser with JavaScript, so it's blocked by ad blockers, cookie restrictions and iOS privacy settings — and it can't see what happens after a lead leaves your site, like whether they closed in your CRM. The Conversion API sends events server-to-server directly from your CRM to Meta, so it isn't blocked and it can report offline outcomes like a deal won. Most reliable setups use both.
When a Facebook lead ad is submitted, the CRM captures the lead along with its Meta lead ID. As your team works the lead through the pipeline, each stage change fires a server-side event to Meta with that lead ID. Meta matches the event to the original ad click and learns which ads produce leads that convert — then finds more people like them. In Salesgem this runs automatically once you connect your account and map your funnel stages.
No. Setting up CAPI by hand involves access tokens, event payloads and server code — but Salesgem handles all of that. You connect your Meta dataset (Pixel) ID and access token, map your pipeline stages to Meta's funnel events in the settings screen, and Salesgem sends the events for you. No code, no developer.
Conversion Leads is a Meta ad optimisation that lets Facebook optimise for leads who actually convert into customers, rather than for the volume of form fills. It works by receiving your CRM's funnel progression — contacted, qualified, converted — back through the Conversions API. Meta reports it can lower cost per quality lead by around 19% for advertisers who use it. It typically needs about 200+ leads per month per advertiser to learn effectively.
Meta's Conversion Leads optimisation generally needs around 200 or more leads per month per advertiser to gather enough signal to optimise well. Below that, you can still send CAPI events and improve attribution, but the algorithm has less data to learn from.
Yes. Personal details like email, phone and name are hashed with SHA-256 before they're sent, so Meta never receives them in plain text — this is Meta's standard requirement. The lead's Meta lead ID is sent as-is because Meta needs it to match the event. Salesgem is a Verified Meta Tech Provider and sends this data server-side over a secure connection.
Yes. Instagram and Facebook lead ads run on the same Meta platform, so leads from both flow into Salesgem and fire the same Conversions API events as they move through your pipeline — no separate setup.
Ready in minutes

Start teaching Facebook
which leads become customers.

Free 14-day trial. No credit card. No developer. Connect your Meta account in minutes.

No credit card needed 14-day trial Free migration support
Try Salesgem free — no card needed Start trial