Chalk does not pull leads out of Facebook by itself. You send them in through the Lead ingest connector (with Zapier, Make or your own code), including Meta's lead id. Then the Meta Conversions connector tells Meta which of those leads booked an estimate, approved a quote and paid, so Meta can aim your lead ads at people who become customers. It is off until the owner or an admin sets it up under Settings > Connectors.
Step 1: Get Facebook leads into Chalk
- Set up Lead ingest under Settings > Connectors. See Send leads in and out with Zapier or a webhook.
- In Zapier or Make, start from a new lead on your Facebook lead form, and post it to Chalk with the usual fields (
first_name, plus a phone or email). - Add
meta_lead_id: Meta's lead id, 15 to 17 digits, sent as text (in quotes). Without it, Chalk cannot tell Meta about the lead. - If you have them, add
meta_form_id,meta_ad_idandmeta_lead_created_at(a date and time, or unix seconds), and asourcesuch as "Facebook Lead Ad".
If one of these Meta fields is wrong, the lead is still saved without it, and the answer lists a warning saying which field and why. Chalk also spots a lead id written in the lead's details as "Lead ID" followed by the digits. A developer can send the same fields when adding a lead with a Chalk API key.
Step 2: Turn on Meta Conversions
- In Meta Events Manager, press Connect data sources, choose CRM, and create a new dataset for this. Keep it apart from your website pixel.
- Open that dataset's Settings. Under Conversions API, press Generate access token and copy it. Meta shows it once.
- Copy the Dataset ID from the same page.
- In Chalk, go to Settings > Connectors and open Meta Conversions (under Ads). Paste the Dataset ID and Access token, then press Save and turn on. Saving sends nothing.
- To check it works, copy the code from Meta's Test events tab into Test event code, press Save, then More > Send test event. Clear the code afterwards.
- For Facebook leads already in Chalk, press More > Send the last 7 days of leads.
- In Meta, share the dataset with the ad account that runs your lead ads.
What Chalk sends to Meta
Only leads that carry a Meta lead id are ever sent. Each one is sent once per step:
| Meta sees | When |
|---|---|
| CRMLead | The Facebook lead comes into Chalk |
| Estimate Scheduled | Its estimate visit is booked |
| Quote Approved | Its quote is approved |
| Job Paid | An invoice for it is paid in full, with the amount |
With each one goes Meta's lead id, the time, the CRM name (ChalkCRM unless you change CRM name Meta sees), and the customer's email, phone, first and last name, city, state and zip. Those are scrambled (hashed) inside Chalk before anything leaves.
A quote, job or invoice counts for the lead it is tied to. If it is tied to no lead, the customer's most recent Facebook lead from the last 180 days stands in. A lead from your website or a referral is never sent, even if the same customer once came from Facebook.
Good to know
- Only the owner and admins can set this up. It is free: Meta does not charge for it, and neither does Chalk.
- Meta only takes events from the last 7 days. Older ones are marked Too old and never sent, and Send the last 7 days of leads does at most 200 leads per press.
- What Meta has been told lists the last 50 updates with the step, the time and Sent, Waiting, Failed, Too old or Not sent. It shows only the last 4 digits of the lead id.
- The Send lead updates to Meta switch stops sending when you turn it off, and updates still waiting are dropped. Disconnect is under More.
- The access token is stored on the server and never shown back. If Meta turns it down, a red notice asks for a new one, and updates wait up to 7 days for it.
- Send test event only works once at least one real Facebook lead is in Chalk.
- Give it time: Meta needs a few weeks of these updates, and about 200 leads a month, before it can aim ads with them.