Skip to content

Telling Meta which leads became sales

Facebook and Instagram ads learn from what you tell them. By default they only know who filled in a form. Ad conversions (Meta's Conversions API) tells Meta which of those leads were qualified and which became sales, so your campaigns learn to find more people like them.

It goes to your own Meta dataset with your own token.

Before you start

  • To connect, you need advertising.connect. Owners and Administrators have it.
  • To choose what is sent, you need advertising.configure. The Marketing role has this, as well as Owners and Administrators.
  • In Meta Events Manager you need a dataset (also called a Pixel).

Steps

1. Connect your dataset

  1. Go to Integrations → Ad conversions.
  2. Enter the Meta Dataset ID (older Meta screens call it the Pixel ID). In Events Manager, go to Data sources, choose your dataset, and copy the number under its name.
  3. Enter a Meta Conversions API access token. In Events Manager, open your dataset, then Settings → Conversions API → Generate access token. It is stored encrypted and never shown again; to replace it, paste a new one and save. Leave the box blank to keep the saved one.
  4. Optional: enter a Test event code from Events Manager → Test events. While a code is set, everything goes to the Test events tab and does not count for your ads.
  5. Click Connect. The CRM checks the dataset and token with Meta straight away. The Status panel shows whether it worked and when it was last verified; Verify connection checks again at any time.

2. Choose what to send

Under 2. Choose what to send, switch on the moments you want Meta to know about:

Moment When it is sent Suggested name in Meta
A new lead arrives Every new lead, from any source Lead
A lead moves forward in the pipeline The first time a lead moves to a stage that is neither won nor lost QualifiedLead
A sale is won A lead or a deal reaches a won stage. Its value is sent as the purchase value Purchase

Click Save.

3. Go live

Watch the first events arrive in Events Manager → Test events. Then clear the test event code and save.

What is sent

The moment's name and time, the value for a sale, and the person's email, phone, name, city and state. Each of these is hashed before it leaves the CRM, so Meta can match the person without receiving their details. For a lead from a Facebook lead form, Meta's own lead ID is included too.

Your privacy policy should tell customers that you share this with Meta for advertising. To be stricter, tick Only send for people whose marketing consent is recorded in the CRM on a moment.

Sending and retrying

  • If Meta is unreachable, the CRM keeps retrying the same event for about 80 minutes. Meta recognises a repeat, so a retry never counts twice.
  • An event Meta rejects as invalid is not retried.
  • Meta refuses events older than seven days.
  • Recent conversions shows each event and whether it was sent. If you have advertising.retry_events, you can resend a failed one with Send now.

What this affects elsewhere

The CRM's own source and campaign records are not the same as Meta's reporting. CRM attribution is not platform-confirmed attribution: Meta decides for itself which ad gets credit.

What you cannot change later

A won deal that has no lead is not sent, because there is no person for Meta to match. If you mark both a lead and its deal as won, Meta receives two purchases.

Not available yet. Sending conversions to Google Ads.

Last checked against the product on 2026-11-07. Needs the advertising.connect permission.