--- title: 'Meta CRM conversion leads: send qualified lead stages' description: 'What Meta misses without CRM feedback, which lead-stage fields to return, and how the 7-day upload and 28-day optimization windows differ.' canonical: 'https://plainrouter.com/library/meta-crm-conversion-leads' format: Guide published_at: '2026-10-21' last_updated: '2026-10-21' --- # What do you lose when Meta ads run without a CRM connection? If you send Meta only an Instant Form submission, it can count the lead but cannot see whether your team later qualifies it or closes a deal. Sending CRM lead stages back through Conversions API for CRM supplies those downstream outcomes; it is a separate integration from website conversion tracking or offline store sales. ## Which information is missing after the form submission? The missing information is the lead's progress through your sales process, not the original form response. Downloading a lead into your CRM and returning its later stages to Meta are two different directions of data flow. | Data flow | What it tells Meta | What it does not establish | Source checked | | --- | --- | --- | --- | | Instant Form submission only | Someone submitted a lead form | Whether sales qualified the lead or won the deal | Meta CRM integration, 21 October 2026 | | CRM stages returned for Conversion Leads | The lead reached your recorded funnel stages | A guaranteed match, attributed sale or improvement in lead quality | Meta CRM payload specification, 21 October 2026 | | Offline or store-sale events | A purchase or other outcome occurred outside the website | The CRM lead-funnel setup required for Conversion Leads | Meta offline-events guide, 21 October 2026 | This distinction comes from [Meta's CRM integration overview]() and [offline-events guidance](). Meta documents Conversion Leads optimization here for Facebook and Instagram Instant Forms; do not treat it as a universal optimization goal for every CRM record. ## How do you send CRM lead stages back to Meta? Keep the Meta lead ID when importing the lead, map your CRM stages, and return each stage as it changes, including the initial stage. Use Meta's CRM integration setup to choose the receiving dataset and validate the events before configuring the sales funnel. | Field | What your integration supplies | | --- | --- | | ` event_name ` | The stage recorded in your CRM, consistently named across the funnel | | ` event_time ` | The actual stage-change timestamp, in Unix seconds | | ` action_source ` | ` system_generated ` for this Conversion Leads integration | | ` user_data ` | At least one supported matching parameter; preserve and use the valid Meta ` lead_id ` where available | | ` custom_data.lead_event_source ` | The CRM or internal system the lead stages come from | | ` custom_data.event_source ` | ` crm ` | Fields and values checked against [Meta's CRM payload specification]() on 21 October 2026. This is a field reference, not a captured integration result or a payload to send unchanged. The Meta lead ID comes from the lead-generation webhook's ` leadgen_id ` or the equivalent field in your download. Store it separately from your CRM's internal record ID. Meta's payload specification recommends the lead ID and describes alternative matching parameters; email and phone values must be hashed as specified. Follow the requirements of your chosen setup rather than substituting an internal CRM ID. See [where Meta exposes the lead ID](). ## Which timing window matters? The upload window and the optimization guidance answer different questions. Meta's payload specification allows a stage event up to seven days before upload, and its timestamp must be after the original lead was generated. Its integration guidance separately describes a target stage reached within 28 days of lead generation. Send updates regularly: Meta's [CRM FAQ]() recommends at least daily uploads. Do not alter old stage timestamps to make a backfill look recent. Meeting the upload window does not by itself make a funnel suitable for optimization. ## Where Plainrouter fits Plainrouter does not import CRM lead stages today. [Signals]() covers supported website and backend conversion events; that is not a replacement for a Conversion Leads CRM integration. ## Frequently asked questions ### Does connecting my CRM automatically send qualified leads to Meta? Not necessarily. A connector that downloads new leads may only handle the inbound direction. Check that it also returns the required stage events and matching information through the CRM integration. ### Is a CRM sale the same as an offline conversion? A CRM is a system of record, not the location of a sale. Use the [offline-conversions guide]() for store or other offline outcomes, and the CRM specification for lead-funnel optimization. ### Can the Meta Pixel show whether sales qualified a lead? A browser event alone does not tell Meta what your sales team later recorded. Keep website event delivery separate from CRM stage feedback; the [Conversions API overview]() explains the website/server distinction. ## Sources Checked 21 October 2026: Meta's [CRM integration overview](), [payload specification](), [CRM FAQ](), [lead ID guide]() and [offline-events guide]().