Skip to content

3 ways to send conversions to Meta Ads from Salesforce

Meta optimises better when it receives a conversion signal it can match to the original ad click. The best moment to send that signal depends on where leads originate and whether the chosen stage produces enough events inside Meta's attribution windows.

The three routes at a glance

Three practical routes cover most setups. Use Converly when a form is submitted on your website. Use the tracking snippet plus Zapier when a lead becomes qualified, an opportunity is created, or a deal closes. Use Meta's Conversions API for CRM if you run Lead Ads. The deciding factors are lead origin, event volume and timing.

1. Method 1: Using Converly — send the event at form submission

Converly triggers on a website form submission, a booked meeting or a chat start. It supports Salesforce Web-to-Lead as well as widely used form and booking products including Typeform, Jotform and Calendly. At the moment of submission it gathers the lead's name, email address and phone number together with the Facebook identifiers FBCLID, _fbc and _fbp, and forwards a server-side event to Meta through the Conversions API. Sending server-side with those identifiers attached is what typically lifts Meta's Event Match Score into the 9–10 range; a setup that only records thank-you page views tends to land far lower, around 3. A conversion log records each captured conversion, the payload delivered to Meta and whether delivery succeeded.

This route fits when:

  • Your weekly closed deals sit under the roughly 50 conversions per ad set that Meta likes to see for optimisation, so form submissions give you the greater event count.
  • Your sales cycle runs past 7 days, since Meta attributes clicks over a 7-day window and a closed deal can land after it expires.
  • You want the least involved configuration and a fast start.

2. Method 2: Use the tracking snippet + Zapier — capture identifiers now, send at a later milestone

With the tracking snippet plus Zapier, the Meta event is held back until a later Salesforce milestone — qualification, opportunity creation or a closed-won opportunity. Begin by installing the snippet on the site and adding hidden fields for FBCLID, FBC and FBP. When someone reaches the site from a Meta ad, the snippet records FBCLID, _fbc and _fbp in the browser and, at form submission, writes those values into the hidden fields. The values then accompany the lead into Salesforce, whether via Web-to-Lead, a third-party form integration or Zapier.

At the later stage, build a Zap whose trigger is the Salesforce milestone you chose, set Facebook Conversions as the action and 'Send Other Event' as the Action Event. That action is the one that accepts fbclid, fbp and fbc mappings; without them, matching falls back to email address alone, and the email tied to someone's Facebook profile is often one they no longer use. In Zapier, point the snippet's fbc field at Click ID (fbc) and its fbp field at Browser ID (fbp). Supplying these identifiers is what typically raises the Event Match Score to 9 or 10 and substantially improves how many conversions Meta can tie to individual people.

This route fits when:

  • The bottleneck is the calibre of leads rather than their number, and you want Meta's system to recognise the profile of a genuinely qualified prospect.
  • Your sales team qualifies leads within a day or two, so the event still falls inside the 7-day window.
  • You produce roughly 50 or more qualified leads or opportunities each week.

3. Method 3: Use the Conversions API for CRM for Lead Ads

Lead Ads let people complete a prefilled form inside Facebook or Instagram without visiting your website. That convenience can raise volume but lower quality: submissions may be accidental, prefilled email addresses may be old, and the person may never have researched your offer. Sending qualified-lead feedback back to Meta helps its system distinguish useful leads from accidental ones.

Store the Meta Lead ID on each Salesforce lead. When a lead reaches a quality milestone, create a Zap triggered by that Salesforce action (for example Lead Status changed to 'Qualified'), select Facebook Conversions as the tool and 'Send a Funnel Event' as the action, mapping the Meta Lead ID, Contact Email and Contact Phone from Salesforce. Allow real leads to flow for about a week, then open Events Manager, choose the dataset and use Settings to configure funnel stages and identify the stage Meta should optimise for.

Choose this route when:

  • Leads come from Lead Ads instant forms, not website forms.
  • You receive plenty of leads but sales considers many of them poor quality.
  • Qualification occurs within 28 days, while Meta stops accepting updates for leads older than 90 days.
  • You can supply around 50 CRM events over 7 days across at least two stages, consistently. In practice this suits a few hundred Lead Ad leads per month with a well-maintained CRM. Meta's own captured figure claims about 21% lower cost per quality lead once the loop is running; treat that as an unverified reference, not a guaranteed result.

Decision checklist

Ask two questions first: do leads come from your website or from inside Meta, and which funnel stage has enough volume? Website leads with low later-stage volume belong at form submission with Converly. Website leads with poor quality but fast qualification belong at the qualified stage with the tracking snippet plus Zapier. If you need both optimisation and revenue visibility, combine Converly form-submission events for optimisation with the tracking snippet plus Zapier deal events for campaign reporting and customer audiences. Lead Ads with sufficient volume belong in the Conversions API for CRM route; low-volume Lead Ads may work better as website traffic.

Which route fits your setup?
Your situationBest methodWhy
Website forms; fewer than 50 qualified leads per weekMethod 1: ConverlyHighest-volume signal; inside 7-day window; quick setup
Website forms; poor quality; qualification within 1-2 daysMethod 2: tracking snippet + ZapierTeaches Meta what a qualified lead looks like while staying inside the window
Website forms; need deal and revenue visibilityMethods 1 + 2 togetherOptimise on submissions while reporting deals and building customer audiences
Lead Ads; 150+ leads per month; CRM kept currentMethod 3: Conversions API for CRMBuilt for Lead Ads; uses Meta Lead ID to return qualified-lead feedback
Lead Ads; only a handful per weekConsider website traffic insteadCRM funnel may never reach roughly 50 events per week

Meta's 21% figure is Meta's own claim, not independently verified here.

Frequently asked questions

When should I send the conversion if my sales cycle is long?

Send it at form submission. That stage normally has the highest volume and always falls inside Meta's 7-day click window, which matters when deals take longer to close or weekly volume is below roughly 50 conversions per ad set.

When does a later-stage Salesforce event work better?

Send it when a lead is qualified or an opportunity is created, provided qualification happens within a day or two and you reach about 50 such events per week. That teaches Meta to find more qualified buyers rather than more form fillers.

Can I use the Conversions API for CRM for website leads?

No. That route is built around the Meta Lead ID, which only exists for forms completed inside Facebook or Instagram. Website form leads should use the form-submission or later-stage website routes instead.

What if I only get a handful of Lead Ads each week?

It generally will not activate. Meta looks for around 50 CRM events over 7 days across at least two stages, sent consistently. At low Lead Ads volume, sending traffic to a website form may open more workable options.