# How to Send CRM Stages to Meta, Step by Step

> Pick the CRM stages worth sending, map them to Meta events in Nask AI, check how each one matches to its lead, and run a dry run before you go live.

- Canonical: https://nask.ai/send-crm-stages-back-to-meta
- Published: 2026-11-11
- Author: Rodrigo Nask (https://rodrigonask.com/), Nask AI

---

## Key takeaways

- Send the CRM stages that move a lead toward a payment: lead, qualified, call held and won.
- Cancel and Refund adjust your reports in Nask AI and are never sent to Meta.
- Each CRM stage becomes a named stage in Nask AI, and a custom stage reaches Meta under its own name.
- A stage is tied to its lead by email first, then looser keys, and Nask AI holds the match instead of guessing.
- Run the brand in Dry run until Matched and Would send look right, then go live.

Sending CRM stages to Meta means reporting what happens to a lead after the form, such as a call held or a deal won, back to Meta as conversion events, so Meta learns which ads bring people who pay.

You run Facebook ads for a service business, and your CRM knows things Meta never hears about. Ana booked a call, the call happened, the deal closed. Meta still thinks the best thing your ads ever did was produce a form fill, so it keeps looking for more people who fill in forms.

This tutorial sends those later stages to Meta from your CRM, with [Nask AI](https://nask.ai/how-it-works) doing the matching in between. You will pick the stages, map each one, check how it finds its lead, and test it before a single server event reaches Meta.

## Which CRM stages are worth sending to Meta?

Send the stages that move a lead toward a payment. For most service funnels that is four:

1. **Lead.** The form was sent. Meta event: Lead.
2. **Qualified.** Your team looked at the lead and decided it is worth a call. This one is optional, and it is a custom stage, so it reaches Meta under the name you give it, such as Qualified.
3. **Call held.** The call happened. Nask AI suggests the name CallHeld.
4. **Won.** The deal closed and money moved. Meta event: Purchase.

Two stages are never sent. Cancel and Refund exist in Nask AI so your reports can show a customer who left or got their money back, and the Events and values card marks both with "Reports only, never sent to Meta." There is no switch to turn them on.

> **Figure (animated on the web version):** Four bars rising like a ladder, labeled Lead, Qualified, Call held and Won, each with the event name Meta receives: Lead, Qualified, CallHeld and Purchase. Below the ladder two greyed rows read Cancel and Refund, Reports only, never sent to Meta.
>
> Send the stages that move a lead toward a payment. **Cancel and Refund adjust your reports and never go to Meta.**

Send fewer stages than you think: each is a new place for the chain to break. The guide to [tracking leads from Facebook ads to sales](https://nask.ai/track-leads-from-facebook-ads-to-sales) explains how to choose the deepest stage that still happens regularly. Here the job is the CRM side.

## What do you need in place first?

You need three things before the CRM can send anything useful.

First, the lead has to exist in Nask AI. Matching ties a later stage to a lead of the same brand, and the lead must be older than the event. So the nsk.js pixel on your site, covered in the [Nask AI pixel setup guide](https://nask.ai/nask-ai-pixel-setup-guide), comes first. It stores the click and browser details the later stage will borrow.

Second, the CRM needs to keep the email the person typed in the form, the strongest key for matching.

Third, the brand needs a funnel. In Nask AI, open the brand, go to the Growth tab, and find "2. Funnels and stages" in the "Pixel and funnel" section.

Sending runs through the Conversions API, Meta's route for a business to report conversions from its server instead of a visitor's browser. The setup of that connection is covered in the guide on Meta Conversions API setup for lead generation; here Nask AI is the server that does the sending.

## Step 1: Write your CRM stages next to their Meta names

Make a short list with the stage as your CRM shows it, the name you want in Nask AI, and the Meta event it counts as. For example:

- "New lead" becomes Lead, which counts as Lead.
- "Qualified" becomes Qualified, a custom stage that counts in reports as CompleteRegistration.
- "Call held" becomes CallHeld, a custom stage that counts in reports as CompleteRegistration.
- "Closed won" becomes Purchase, which counts as Purchase.

Meta has standard event names, and Nask AI uses seven of them as its standard stages: Lead, CompleteRegistration, Schedule, StartTrial, InitiateCheckout, Purchase and Subscribe. Anything else is a custom stage with a name you choose. A custom stage also picks the standard name it **Counts in reports as**, and the editor says it "reaches Meta under its own name, so you can optimize for it as a custom conversion."

Two rules save you a debugging session. The CRM stage title must be typed exactly as your CRM shows it, because Nask AI compares that text. And a stage name starts with a letter, then letters, digits, spaces, underscores or dashes. In the name Meta receives, spaces and dashes become underscores, so CallHeld is cleaner than "Call Held".

## Step 2: Add each stage to your funnel in Nask AI

In the "Pixel and funnel" section of the brand's Growth tab, click **Add a stage**. Nask AI suggests the next stage too, such as CallHeld after a booking and Purchase after CallHeld.

In the stage editor, fill in the fields in this order:

1. **Stage.** Pick a standard stage from the list, or **Custom name** for Qualified and CallHeld. With a custom name, fill in **Name** and **Counts in reports as**.
2. **Detected by.** For a CRM stage in Attio, choose **CRM stage (Attio)**, once Nask AI has connected your Attio workspace (see below). For any other CRM, choose **Webhook**; the editor says "Sent by the server, no page code needed."
3. **Attio stage title.** Once Attio is connected, type the title exactly as Attio shows it, for example "Call held". The editor adds a note: "Attio changes arrive as offline stages, accepted up to 62 days after the click." The 62 days count from when the stage happened, not from the click. Offline means the stage happened away from your website.
4. **Value** and **Predicted LTV.** A value is the money this stage is worth in your brand currency. Predicted LTV is what you expect a customer to be worth over a lifetime. On Purchase the value is not optional: a Purchase with no value at all is stored and reported but never sent, because Meta rejects it.
5. **Send to Meta.** On by default. Switch it off for a stage you want in your reports and not in Meta.

Click **Save stage**. Saving also creates the matching row in the Events and values card, so the name is known to the Conversions API.

> **Figure (animated on the web version):** Two rows, each a three-hop track. Row one: the Attio stage title Call held becomes the Nask AI stage CallHeld, which counts as CompleteRegistration, and reaches Meta as CallHeld. Row two: Closed won becomes the stage Purchase, detected by CRM stage (Attio) or Webhook, and reaches Meta as Purchase. A purple marker runs along each track.
>
> Each CRM stage becomes a named stage in Nask AI, and that name is what Meta sees. **Type the CRM stage title exactly as your CRM shows it.**

On the Attio side, Attio tells Nask AI when a deal moves. Nask AI then reads the deal's current stage and the people attached to it, compares the stage title with the stages you saved, and ingests one offline event with the time the deal entered that stage. A stage title you did not map is acknowledged and ignored. Attio's own guide explains [how its webhooks are delivered and signed](https://docs.attio.com/rest-api/guides/webhooks). The Attio route is not self-serve yet: it works once Nask AI has connected your Attio workspace to the brand, so ask us before you map Attio stages. Until then, send the same stages through Step 3 from Attio's own automations.

## Step 3: Send stages from any other CRM with the Conversions API

A CRM that is not Attio sends its stages with one web request per event. In Nask AI, open the brand's Growth tab and find the Conversions API section. The **Endpoint and secret** card shows the **Endpoint (POST)**. Click **Create secret** (or **Rotate secret** if the brand already has one) and copy the secret. It is shown once, and rotating it makes the old one stop working at once.

Then have your CRM post this when a deal moves to a mapped stage:

```bash
curl -X POST "YOUR_ENDPOINT_URL" \
  -H "Authorization: Bearer YOUR_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "event_id": "deal_4471_callheld",
    "event_name": "CallHeld",
    "occurred_at": "2026-11-10T14:03:00Z",
    "email": "lead@example.com",
    "source": "my-crm"
  }'
```

- **event_id** is your own unique id for this event. Use something your CRM produces again for the same event, such as the deal id plus the stage, never a random value. Send the same id twice and it is stored once and sent at most once, so a retry can never double count.
- **event_name** is a standard name in any capitalization, or the custom name you saved in Step 2.
- **occurred_at** is when the stage happened, not when you sent it. Use ISO 8601 starting with the year, with a time zone. A date like 09/10/2026 is refused because the month and the day could be either way round.
- **email** is the person's email. You can add `phone`, `external_id` for your CRM contact id, `fbc`, `fbp` or `fbclid` if your CRM stored them.

For a stage that happens away from your site, such as a won deal a few weeks after the click, also send `"action_source": "offline"`, which is the route Meta accepts for older events (accepted by the endpoint, though the API reference does not list it yet; Nask AI then allows up to 62 days). The endpoint answers `202` with one line per event, and a rejected one says why.

> **Figure (animated on the web version):** A terminal window. A request is typed line by line: POST to your endpoint, an Authorization header with your secret, then a JSON body with an event_id, the event name CallHeld, a time and an email. The reply appears in green: 202, ok true, mode dry_run, accepted 1.
>
> Any CRM that can send a web request can send a stage. **One request, one event name, one email, and a 202 means it was stored.**

Make and Zapier work the same way: post the JSON with the `Authorization` header from the HTTP module in Make or the Webhooks POST action in Zapier, with every mapped value inside quotes and decimals given a dot. For the Won stage, a payment can be a better source than the CRM. There is no built-in Stripe receiver: [Stripe sends an event to an endpoint you register](https://docs.stripe.com/webhooks) when a payment succeeds, so point that at Make or Zapier and post it to the Step 3 endpoint as Purchase with the paid value. In the stage editor you label it **Stripe payment**.

If your site's pixel already reports leads to Meta, send the CRM's copy of the lead with `"send_to_meta": false`. It still becomes a lead record in Nask AI, which is what later stages match against, and Meta does not hear about the same lead twice.

## Step 4: Let Nask AI match each stage to its lead

A stage that arrives from the CRM is only an email and a name. The click that brought the person, the browser and the ad live on the lead. Matching joins them. Nask AI tries these keys in order, strictest first, and stops at the first one that points to a lead of the same brand:

1. The exact email.
2. The same email written differently, such as a Gmail address with dots or a plus tag.
3. The phone number, completed with the brand's default country when it has no country code.
4. Your own customer id, sent as `external_id`.
5. The visitor id from the pixel.
6. A company email domain together with the full name.
7. A full name that only one lead in the brand has.

Two rules outrank every key. The lead has to be older than the event, so a payment cannot borrow a click from someone who arrived after it. And anything weak or ambiguous is held: if two leads share an email but name different people, or only one name part matches at a shared company, Nask AI holds the match rather than credit the wrong person.

> **Figure (animated on the web version):** A list of seven matching tiers from strictest to loosest: exact email, same email written differently, phone, your customer id, visitor id, company email domain and full name, and a full name only one lead has. Two outcomes sit below: Matched, which takes the lead's click id, browser id and UTMs, and Held, which is sent with the event's own details only.
>
> Nask AI tries the strictest key first and stops at the first one that points to one lead. **When two people fit, it holds the match instead of guessing.**

A matched stage inherits the lead's details, so an event that carries only an email goes to Meta with the click id and browser id the lead arrived with, and your reports credit the ad from the lead's UTMs.

Held and unmatched are not dead ends. After a 10 minute wait, in case the lead is posted right after the sale, Nask AI sends the event to Meta with only what you sent, nothing borrowed from any lead, so it cannot land on the wrong person. Only an event with nothing Meta can match on stays home, with the reason `no_identity`.

## Step 5: Stay in Dry run, then go live

Every brand starts in Dry run, and the **Sending to Meta** card in the Conversions API section says so with a badge. Dry run stops only the server copy: Nask AI matches every conversion, builds the exact event and does not send it. Your site's own browser pixel keeps firing. That makes it the safe place to send your first stages and see what would have happened.

Above the card, the "Last 30 days" activity card counts what arrived: Received, Matched, Held, No lead, Would send (or Sent once you are live) and Not sent (this tile becomes Failed if Meta refused any event). Not sent covers stages that are switched off, too old, without anything to identify the person, or Cancel and Refund. Below the counts, a list names each held event or event with no lead, with the reason.

Go live when your test stages appear under Matched, the Held and No lead lists hold nothing unexpected, and Would send shows the stages you meant. Click **Go live**, then confirm with **Send to Meta**. The card changes to say "Matched conversions go to Meta within a minute of arriving, each one once." **Stay in dry run** cancels, and **Back to dry run** turns it off again later.

Only the workspace owner can switch a brand to live. And going live sends new conversions only, so events handled during the dry run stay unsent: the dry run is your test window, not a backlog that gets released.

> **Figure (animated on the web version):** A card titled Sending to Meta with a Dry run badge and a Would send counter that climbs to 12. A Go live button is pressed. A confirmation row appears with a Send to Meta button, which is pressed. The badge changes to Live and a Sent counter shows 0, with the note Going live sends new conversions only.
>
> Dry run builds the exact server event and does not send it. **Going live sends only the conversions that arrive afterwards.**

## Step 6: Test one stage from end to end

A stage that has never passed a test is a guess. For stages the page catches, the stage row has a **Test** button. A CRM stage has none, because there is nothing on the page to catch, so you test it by moving a record.

Create a test person whose email you own, for example your own address with a plus tag, such as you+crmtest@example.com. Submitting your form with it fires the browser Lead, so expect one Lead in Meta from the test person. The form also creates the lead. Move a test deal to the mapped stage in your CRM. For a stage you post yourself, use an `event_id` that starts with `test_` and send `"send_to_meta": false`. It is stored and shown in reports like any event and never sent.

Then read the activity card. Received should go up by one, and the event should land under Matched. If it lands under Held or No lead, the reason in the list tells you which key failed.

Retest when anything in the chain changes. A renamed stage in the CRM silently stops matching your saved stage title, which is how a working setup goes quiet.

## Why does a CRM stage not reach Meta?

When a stage you expected is missing from Meta, work down this list. Each item matches a reason Nask AI records.

- **The Send to Meta switch is off** for that stage, or `send_to_meta` was false on the event.
- **The Attio stage title does not match.** "Call held (done)" is a different stage from "Call held".
- **The event is too old.** Website-style events must be under 7 days old when they come up for sending, and offline stages under 62 days.
- **A Purchase has no value.** Set a value on the stage or send one with the event.
- **There is nothing to identify the person.** An event with no email, phone, external id, click id, browser id, or IP with user agent stays home.
- **It is Cancel or Refund.** Never sent.
- **The brand is still in Dry run.** The activity card shows the event as Would send.
- **The event was rejected.** A `422` or a `rejected` line says which field to fix.

For the offline windows in full, see the guide on Facebook offline conversions for booked calls.

## When not to send a CRM stage

Do not send a stage your team fills in inconsistently: if half your reps move a deal to Qualified when they remember to, Meta learns a pattern unrelated to the lead.

Do not send a stage that happens a handful of times a month. Meta needs steady volume to optimize on an event, so send an earlier stage that predicts it.

Last, an email tied to a click is personal data under rules such as the [EU data protection rules](https://commission.europa.eu/law/law-topic/data-protection_en) when your visitors are in the EU, so say in your privacy notice what you send and where, and ask for consent where the law requires it.

## Frequently Asked Questions

### Which CRM stages should I send to Meta?

Send the stages that move a lead toward a payment: the lead, the qualified lead, the call that was held, and the deal that was won. Add a stage only if it changes which ads you would keep. Cancel and Refund are never sent to Meta by Nask AI, because they only adjust your own reports.

### Can I send stages from a CRM that is not Attio?

Yes. Every CRM can use the Webhook detection or post to the Conversions API endpoint of the brand, and the CRM stage detection reads Attio only once Nask AI has connected your workspace. Anything that can send a web request with a secret, an event name, a time and an email can send a stage, including Make and Zapier.

### Why does my CRM stage show as Held or No lead?

Held means more than one person fits the event or the match is weak, and No lead means no lead of that brand fits. Both are still sent with only the details the event carried, after a 10 minute wait for a late lead, as long as the event has an email, phone, click id or similar. Without any of those it stays home.

### Will a dry run send anything to Meta?

No server event is sent in Dry run: Nask AI matches every conversion, builds the exact event and does not send it. Your site's own browser pixel keeps firing, though. The activity card counts server events as Would send. Switching to Live sends new conversions only, so events handled during the dry run stay unsent.

### How old can a CRM stage be and still reach Meta?

A stage detected through Attio can be under 62 days old, because Nask AI sends it as an offline event. Other server events must be under 7 days old when they come up for sending, or they are stored and reported but not sent. A stage you post yourself can use the offline route by setting its action source to offline.

## Send your CRM stages with Nask AI

Nask AI holds the whole chain: nsk.js catches the lead on your site, your CRM and your payments bring in the stages after it, each one is matched to the lead and the ad, and you choose which stages go to Meta. Once those stages flow, the next question is [how many ads each ad set needs](https://nask.ai/how-many-ads-per-ad-set-on-meta) to give Meta something to optimize.

Map your CRM stages, run them in Dry run, and go live when the numbers match. Then Meta learns from the deals you actually close.

- [Book a demo](https://cal.com/rodrigo.nask/60min)
