Send lead stage changes to Meta with Conversions API

The Meta Conversions API connection sends your lead stage changes back to Meta, so Facebook and Instagram can learn which leads became customers. Leadnote delivers the events to a Meta CRM dataset that you choose. Account Owners and Managers can set it up.

What you need

• A Meta CRM dataset. Find its ID in Events Manager under Data Sources, your CRM dataset, Settings. The ID is a number of 8 to 20 digits.
• A Conversions API access token for that dataset.
• Lead stages set up in Leadnote. See lead stages.

Open the integrations hub and choose the Meta Conversions API card. The page has tabs for Connection, Stage events, Delivery log, Setup guide and Activity log, and a progress list: Connect Meta, Test connection, Map lead stages and Enable delivery.

Step 1: Connect Meta

There are two ways.

Meta Business login. Choose Connect with Meta, finish the login in the window that opens, then pick a Business Portfolio and a CRM dataset. This path needs Meta to have approved the Leadnote app for the business and dataset lists. The page marks it Requires Meta App Review. If your browser blocks the login window, use the link on the page.

Advanced: connect manually. This works without any Meta app review.

1. Choose Advanced: connect manually.
2. Enter the Dataset ID.
3. Paste the Conversions API access token. It is write-only: Leadnote encrypts it, checks the dataset with Meta before saving and never shows it again.
4. Choose Save connection.

If the page says it is using the Leadnote platform credentials, your dataset has no token of its own. Add your own token under Advanced to send with your account. Choose Disconnect Meta to stop delivery and remove the saved dataset and token. Events already sent stay with Meta, and events still waiting in the outbox are no longer delivered.

Step 2: Test the connection

1. In Meta Events Manager open Test Events for the dataset, choose the Offline channel and copy the Test Event Code.
2. In Leadnote, paste only the generated code, for example TEST12345, into Test Event Code. A leading "Test event code:" is removed for you.
3. Choose Send test event. Leadnote sends one test event built from your most recent lead.

The test code is used for this one test and is not stored, so live events never go to the Test Events tab. The page shows whether Meta accepted the event, how many events Meta received and a trace id. You can choose Skip test, but turning delivery on will still ask you to confirm until a test has passed.

Step 3: Map lead stages

Open Stage events. Each lead stage is a row.

Choose Use the suggested stages for suggested event names. Choose Save stage events when you are done.

Step 4: Enable delivery

1. Set the Lead event source. It is sent to Meta as the source of every event.
2. Switch on Send CRM events to Meta.
3. If no test has passed, confirm Send live events.

From then on, a lead moving to an enabled stage creates an event. Events wait in an outbox and go to Meta in batches. Switch delivery off to pause: leads are unaffected and events already waiting stay in the outbox.

Watch delivery

The Delivery log lists events with their event name, status (Pending, Processing, Sent or Failed), attempts, response and any error. Filter by event or status. It never shows raw lead data, because events carry hashed contact details.

If events fail, choose Retry failed events. This puts events from the last 7 days back in the queue.

The page also shows delivery health and CRM verification readiness. Meta verifies a CRM dataset for Conversion Leads after events on 7 days, at least 60% lead coverage and 2 or more funnel stages. Keep delivery on and keep updating lead stages. Whether Meta verifies the dataset is Meta's decision.

If Meta rejects a token, the page shows Reconnect needed. Leadnote also sends an integration.needs_reconnect webhook event if you use webhooks.