Facebook CAPI for Lead Gen: Sending CRM Qualified Leads Back to Meta

The Standard Lead Gen CAPI Setup (and Its Limits)

Most lead generation businesses implement Facebook CAPI by sending a Lead event when someone submits a contact form. This tells Meta "this person submitted a form" — but it does not tell Meta whether the lead was actually any good. A business that generates 100 form submissions per month but only 5 become paying clients is training Meta's algorithm on all 100 submissions, 95% of which are unqualified.

The result: Meta optimises for form submitters, not for your ideal customers. Ad cost is high because the algorithm is targeting a much wider audience than it needs to.

The CRM Lead Value Chain

A more sophisticated approach sends multiple conversion events that mirror the qualification journey:

1. Lead: web form submitted (sent immediately from CAPI)
2. Qualified Lead: CRM or sales team marks the lead as qualified (sent from CAPI when qualification status changes)
3. Opportunity: lead moves to opportunity stage (sent from CAPI)
4. Purchase / Customer: deal closes (sent from CAPI with deal value)

By sending all four stages back to Meta, the algorithm learns which audience characteristics predict paying customers — not just form submitters.

How to Send CRM Events to CAPI

The key is storing the _fbp cookie and the ad click's _fbc cookie at the time of form submission, linking them to the CRM lead record. When the lead progresses (or converts), you have the attribution cookies to send with the downstream event.

Step 1: Capture at Form Submission

When a lead submits a form on your website:

• Capture: email, phone, _fbp cookie, _fbc cookie (if the visit was from a Meta ad), IP address, user agent
• Store these in your CRM alongside the lead record
• Send the Lead event to CAPI immediately

Step 2: Send Qualification Event from CRM

When your sales team qualifies a lead in the CRM (changes status to "Qualified"):

• Your CRM triggers a webhook or API call to your server
• Your server sends a CAPI event with event_name "QualifiedLead" (custom event name) using the stored _fbp, _fbc, and hashed email/phone from Step 1

Step 3: Send Purchase Event When Deal Closes

// When a deal closes in the CRM
{
  "event_name": "Purchase",
  "event_time": unix_timestamp_of_close,
  "event_id": "DEAL-456",
  "action_source": "crm",  // or "website" if the event conceptually started there
  "user_data": {
    "em": [hashed_email_from_crm],
    "ph": [hashed_phone_from_crm],
    "fbp": fbp_cookie_from_initial_submission,
    "fbc": fbc_cookie_from_initial_submission
  },
  "custom_data": {
    "value": 5000.00,  // Deal value
    "currency": "GBP"
  }
}

Value Optimisation for Lead Gen

Once you are sending deal values back to Meta, enable Value Optimisation on your campaigns. Meta's algorithm optimises to find users who generate the highest deal values — not just any form submitter. This can significantly improve lead quality over time.

Summary

For lead gen businesses, the highest-impact CAPI upgrade is sending downstream conversion events (qualified lead, opportunity, closed-won deal) from the CRM back to Meta — not just the initial form submission. Store attribution cookies at form submission, link them to the CRM record, and trigger CAPI calls when lead status changes. This teaches Meta's algorithm to find prospects who actually convert to customers, not just people who fill in forms.

See our Facebook CAPI Setup service for lead gen CAPI implementation.

Need CRM-to-Meta lead quality signals set up? Contact Adslytics.