Kasar
KasarMeta Lead Ads

Meta Lead Ads in your CRM: the lead arrives, the workflow decides

Someone fills in your Facebook or Instagram form, and Kasar receives the lead with the identifiers of its campaign. It does not create the record by itself: a workflow creates it, schedules the call back and starts the follow-up. The connection is built, but opening it to every account waits for Meta to approve Kasar’s app, hence the “Coming soon” label.

Coming soon

01

The lead triggers, your workflow decides

Kasar receives the lead through a signed webhook, reads it with your Page token and publishes the “Ad lead received” event. At that moment nothing exists in the CRM yet: the workflow chooses what to do with it. When you connect a Page, a checkbox, ticked by default, publishes the ready-made workflow “Ad lead → company, contact, deal and task”. It recognizes the contact with your workspace’s identity rule without overwriting a known record, creates the company if the form gives one and the contact is new, opens a deal (or reuses the contact’s deal that is already open), notes the form answers and creates the “Call back” task. If two records match the same lead, it changes neither and leaves you a “Duplicate to settle” task.

02

Your Pages, a catch-up net, a journal

When you connect, a screen lists the Pages Meta gave access to: you tick the ones that feed the workspace, and you import the leads of the last 90 days or only the new ones. Each Page has a status card, with the cause when something is wrong (missing leads access, withdrawn permission, lost subscription), and admins are notified. A lead starts one run, whether it arrives through the webhook or through the catch-up. According to Meta, an undelivered notification is retried for 36 hours and then dropped: Kasar therefore re-reads recent leads at regular intervals: every six hours on a healthy Page, every hour as long as a pass finds a missed lead or an error. The “Lead journal” shows every lead of the last 90 days with its status and its origin (real time, catch-up, replay), and an admin can replay a lead or a period.

03

The campaign travels with the lead

The lead carries the identifiers of its campaign, ad set, ad and form, and their names and the platform when Meta provides them. The contact keeps its first campaign in the “Ad source” column, set once and never overwritten, and the deal keeps the lead and the campaign that produced it. With “Link a Meta form”, you put the answer to each question in the field of your choice; an unlinked answer stays in the lead’s recap, which the default template writes in a note. From the card, “Advertising performance” sets spend, entered by hand, imported from a CSV file or imported every day from an ad account you have linked, against leads and deals: cost per lead, cost per opportunity, return on won deals. Coming soon: linking the ad account through the Meta connection itself, without pasting a token, which waits for the ads read permission.

When it helps

Call back fast, and do not let the call back sleep

The “Ad lead → fast callback and escalation” template creates today’s “Call back” task and alerts the team right away. Four hours later, if the task is not done, a notification and an escalation task go out. Speed comes from the alert: a task’s due date is a day, not an hour.

Welcome with an email, follow up if silence lasts

The “Ad lead → welcome email and follow-up” template sends a first email to the new contact, waits three business days, then creates a follow-up task only if they have not replied. Without an address, it creates a call task. It sends without approval to the address in the form: publish it only if the form collects agreement to be contacted.

Spread leads across your sales reps

The “Ad lead → owner assigned (random without campaign, rotation with one)” template spreads each new contact across active members: randomly without a campaign, in rotation with one. It does not route by campaign as it stands: for one rep per offer, add one case per campaign to the “Switch” and a pool to each “Distribute / assign”.

Have Leo qualify the lead

The “Ad lead → qualification by Leo” template assigns the contact, then Leo sorts the lead from its answers (hot, warm, off target) and sums it up in a note. A hot lead opens a priority task. A decline email never goes out without the approval of the assigned rep.

Setting it up, step by step

  1. 1

    An admin opens the workspace settings, Integrations tab, “Advertising” section, and clicks “Connect” on the “Meta Lead Ads” card.

  2. 2

    Sign in to Facebook with an account that has the “Leads” task on the Page, and leave every permission ticked.

  3. 3

    In “Pages to connect”, tick the Pages, choose to import the last 90 days of history or only new leads, and leave the box that publishes the ready-made workflow ticked (untick it to build your own).

  4. 4

    Check the card: one line per Page with its status, and the “Lead journal” to follow each lead’s arrival.

  5. 5

    In “Automations”, adapt the workflow from the “Ad lead received” trigger: limit it to some forms with “Forms”, link your form questions with “Link a Meta form”, add a follow-up template (the fast callback recreates the “Call back” task and the alert of the default template: unpublish that one first).

What Kasar captures, and where it goes

  • The name, email and phone typed in the form, set on the contact. The company, when the form asks for it, creates the company record of a new contact. The city and country, when the form asks for them, appear in the answers recap and can be used as variables in the workflow: no template writes them on a record.

  • The answers to the other questions, in the lead’s note (with the default template, or a “Create a note” block that reuses the recap), or in the field you linked to the question.

  • The identifiers of the campaign, ad set, ad and form, plus their names and the platform (Facebook or Instagram) when Meta provides them.

  • The consent boxes that were ticked, when Meta provides them, kept with the lead.

  • Each lead only once: received by the webhook, re-read by the catch-up or arrived twice, it starts a single run.

Automations that go with it

Ad lead received

What the workflow does
The “Ad lead → company, contact, deal and task” template: “Create or update” the contact, “Create a record” for the deal, “Create a note” with the answers, “Create a task” to call back, “Alert the workspace”.

Ad lead received

What the workflow does
The fast callback template: “Create a task”, “Alert the workspace”, “Wait” four hours, then an escalation task if the first one is not done.

Ad lead received

What the workflow does
The welcome email template: “Send an email”, “Wait” three business days, “If they replied” to decide whether to create the follow-up task.

Ad lead received

What the workflow does
The assignment template: “Switch” between a lead without a campaign and a lead with one, then “Distribute / assign” and “Alert the workspace”.

Triggers and blocks carry their exact names from the Kasar automation editor.

Frequently asked questions

No. The lead publishes the “Ad lead received” event and nothing else. The record is born when a workflow creates it, for example the one the connection publishes by default. With no workflow published, the lead is set aside without creating anything, and it goes out as soon as a workflow is published, as long as it is under 85 days old.

According to Meta, an undelivered notification is retried for 36 hours, then dropped. Kasar therefore re-reads the recent leads of your forms at regular intervals, and those it had not received start their run. The “Lead journal” says what each lead became, and an admin can replay a lead or a period.

No. Kasar keeps track of every lead received. Whether it arrives through the webhook, through the catch-up or twice in a row, it starts a single run.

Yes, with the default template: all answers are gathered in the lead’s note. The other templates do not write that note: add a “Create a note” block that reuses the answers recap. With “Link a Meta form”, you also choose the field that receives the answer to each question, and Kasar flags a link that has become obsolete when the form changes.

Not yet. It is built, but while Kasar’s app is in development mode, Meta only delivers the leads of people who have a role on the app (Meta, Lead Ads). Opening it to everyone depends on Meta approving the app, with no promised date: that is why the card carries the “Coming soon” label.

Sources

Connect your tools, keep your habits

Connect your mailbox and calendar in two minutes, the history flows in on its own.

Start for free