Skip to content
growthcontrolBook a consultation

How to send qualified leads from your CRM back to Meta

Send qualified lead events back to Meta by saving the Meta lead ID from each Instant Form submission and sending a CRM stage change through Conversions API for CRM. Start with a stage your team can define and apply. Verify that Meta receives the events before choosing that stage as the signal for campaign optimization.

Growth Control implementation notes · · 5 min read

Map the two directions between Meta and your CRM

DirectionRecord to checkWhat it proves
Meta → CRMInstant Form submission with its Meta lead ID on the inquiry recordYour team received a lead it can follow up.
CRM → MetaAn event from a recorded stage change and the matching lead IDYour CRM sent a later outcome back to Meta.
Meta Events ManagerThe expected event in the correct data source and any diagnosticsMeta received the event. Campaign optimization is a separate check.

Conversions API for CRM sends events from your sales system. Meta documents a separate setup from website events and limits the Conversion Leads performance goal to Lead Ads using Instant Forms.

Send the outcome back to Meta

  1. Instant Form

    Meta supplies the lead ID.

  2. CRM inquiry

    Keep the ID with the record.

  3. Stage change

    The team confirms qualification.

  4. Meta receives it

    Check the event in Events Manager.

The form sends the inquiry to your CRM. The CRM sends the later outcome back to Meta.

Choose a stage your team records the same way

A booked estimate can work if your team records it reliably and enough leads reach it. A qualified inquiry can be a better starting point when wins take weeks. For example, a rental inquiry qualifies after the team confirms a service area, available date and job type. A missed call or a request with no response stays unresolved.

Use Meta’s current fit guidance to check your monthly volume, how soon leads reach the stage and how often your team can send updates. With too few events, fix lead handling and collect a reliable baseline before switching the campaign goal.

Diagnose why Meta leads are dropping out before choosing a signal.

Send the qualified lead event once

  1. Capture the Meta lead ID from the form integration as text and keep it with the inquiry. Verify that retries and CRM updates preserve the original ID.
  2. Write a map from each eligible CRM stage to the event your integration sends. Include the initial stage as required by your setup and the downstream stages you intend to report.
  3. When a record reaches the mapped stage, send the event through the configured CRM connection. Use the actual stage time and the permitted matching data required by Meta.
  4. Keep a stable event identity and a delivery record for retries. If a deal is edited without a stage change, avoid sending another copy of the same event.
  5. Check Events Manager for the expected event, data source and diagnostics. Reconcile a small set of authorized records before changing the campaign’s performance goal.

Test the records that usually expose a gap

Test caseExpected result
Instant Form lead enters the CRMThe lead ID is present on the right inquiry.
The team marks the lead qualifiedThe mapped CRM event reaches the right Meta data source.
The CRM sync retriesThe original stage event keeps the same ID and is counted once.
The lead ID is missingThe record is flagged for review. The record keeps an empty ID until someone can verify the source.
The lead came from another channelThe team follows its approved matching rules and can explain which channel supplied the lead.

For an illustrative test, trace a single form lead from received to qualified. Check the CRM stage timestamp against the event log. If a connector reports success but you cannot find the expected event in Meta, check the data source and event mapping before changing the campaign.

Hand the workflow over with one owner

Document who owns the stage definition, who reviews delivery errors and what to do when the team changes a CRM stage. Measure real outcomes such as qualified inquiries and booked estimates in your CRM. Use Meta’s reporting to see what the platform credits to its ads.

Growth Control can scope and implement the CRM-to-ad-platform handoff, test the mapping and give your team a repeatable review.

Explore paid media management with CRM outcomes.

Questions and answers

Is Conversions API for CRM the same as website CAPI?

They use different sources. The CRM integration sends sales stages from the CRM, while website CAPI sends site events.

Can I use the Meta Conversion Leads goal for website forms?

Meta currently documents this goal for Lead Ads using Instant Forms. Website lead tracking uses a different setup.

Should I send only won deals to Meta?

Choose a meaningful stage with enough reliable and timely records. A qualified inquiry or confirmed estimate may arrive more often and sooner than a won deal.

What if a contact in the CRM has no Meta lead ID?

Review how the contact entered the CRM and what matching fields your supported setup permits. Keep unmatched records visible for review.

Sources and further reading

Continue with the next question

Put the process into practice

Growth Control implements the tools, workflow and team handoff around an agreed business result.

Explore connect qualified CRM outcomes to your advertising platforms