Leads

A lead is a person who left their details in a lead form on Meta, Google Ads or LinkedIn. This page is for the marketer. It covers three things: making a lead form, exporting new leads when you ask, and a lead feed that sends new leads to your own system without anyone asking.

Leads are people's contact details

A lead is a name, a phone number and an email address. Reading leads hands them to your AI client. Ask for them only when you mean to pass them to a system of your own, and name that system. Nothing of a lead is stored on the server.

What has to be on first

Reading leads is off on a new installation, for each platform separately. An administrator opens it:

Platform	Page	Switch
Meta	Meta app, under Meta Ads	Allow reading leads
Google Ads	Safety limits, under Google Ads limits	Let a call read the leads of Google lead forms
LinkedIn	LinkedIn app, under LinkedIn Ads	Leads: ask for r_marketing_leadgen_automation

You also need:

• Write access for your user. Reading leads changes nothing, but it is held to the people who may make changes. It still works while the whole server is read-only.
• The permission on your own connection. The Meta and LinkedIn switches each add a permission to the sign-in, so if you connected before the switch was opened, reconnect on Meta connection or LinkedIn connection. Google needs nothing new: leads come through the Google Ads connection that you already have.

When one of these is missing, the answer says which, and where it is changed. See Contact data for what the administrator should weigh before opening a switch.

Make a lead form

The form comes before the ad that opens it.

Show me the lead forms of our Facebook Page.

Create a lead form for the Acme demo campaign on LinkedIn that asks for first name, last name, work email and company.

What happens on each platform:

• Meta. A form belongs to a Facebook Page, so you name the Page. A form cannot be edited or deleted afterwards, only archived. The preview is the server's own check: Meta has not seen the form yet.
• LinkedIn. A form belongs to the ad account. It is always created as a draft, and publishing it is a separate step that you confirm. Once an ad uses a published form its questions are fixed, and LinkedIn has no delete for a form: it can be archived. Making and listing forms does not need the Leads: ask for r_marketing_leadgen_automation switch; reading the leads does.
• Google Ads. A lead form is an asset that is attached to a campaign. See Google Ads.

Like every change, a new form is previewed first and made only after you say so. See How it keeps you safe.

To use a form in an ad, see Meta Ads and LinkedIn Ads.

Export new leads

Ask your AI client for the new leads and say where they go.

Export the new leads from all platforms and add them to the "Leads" sheet.

Give me the new leads of the Facebook Page 100000000000000 only.

Export the LinkedIn leads since the first of October again.

Every lead comes back in one shape, whichever platform it came from:

Part	What it is
platform, lead_id	Where the lead came from and its id there. Together they identify the lead.
created_at	When the person submitted the form.
form_id, form_name	The form.
campaign_id, campaign_name, ad_id, ad_name	The campaign and ad that brought the lead, where the platform says.
fields	The usual answers under one name on every platform: email, work_email, phone, full_name, first_name, last_name, company, job_title, city, state, country, zip and a few more.
custom	Any other question the form asked, with the question and the answer.
click_id	For a Google lead, the id of the click. You need it to tell Google later that this lead became a customer.
test	True for a LinkedIn test lead.

Read, then mark

Exporting is two steps, so that a hand-over that fails loses nothing:

1. The AI client reads the new leads. This moves nothing.
2. Once your system has the leads, the AI client marks them as exported. Only then does the next export start after them.

Until the leads are marked, the next export returns the same leads again. So your CRM or sheet may be offered a lead twice: have it recognise a lead by platform and lead_id together.

The marks are your own. Another person's export does not move yours, and yours does not move theirs.

What one export reads

• With no platform named, all three are read.
• A platform named alone reads up to 10 of your Pages or ad accounts, and up to 25 forms for each. To read others, name the Page or account.
• One call returns up to 500 leads (100 unless you ask for more). When there are more, the answer says so and the AI client asks again for the rest before it marks.
• A platform that cannot be read is listed with its reason: switched off, not connected, a missing permission, or a platform that asked to slow down. The other platforms are still read. Your AI client should tell you what was skipped.

What it cannot do

• Google keeps a lead for 60 days. Export within that time. An account with more than 10,000 submissions in its 60 days is refused rather than read in part.
• LinkedIn leads belong to a version of the form. An export reads the latest version.
• The names of a LinkedIn campaign or ad are not looked up: you get their ids.

What is recorded

The activity log keeps where leads were read from (the Page or account, and the form) and how many. It never keeps an answer, a name or a phone number.

Lead feeds

An export needs someone to ask. A lead feed does not: for one Facebook Page, Google Ads account or LinkedIn ad account, the server looks for new leads every few minutes and sends them to your organisation's own system, such as its CRM.

WARNING

A lead feed sends people's contact details on with nobody asking at that moment. Set one up only when that is exactly what you want.

What has to be on

• An administrator has switched lead delivery on and set the one address that leads go to, on Lead delivery. You cannot choose or change that address, and neither can your AI client. See Lead delivery.
• Everything that reading that platform's leads needs: the switch, write access and the permission.

Add a feed

On the management page:

1. Open History and find Lead feeds.
2. Under Push the new leads of, choose Facebook Page, Google Ads account or LinkedIn ad account.
3. Type its id in the field below.
4. Press Push these leads, and confirm.

Or ask your AI client:

From now on, push the new leads of our Facebook Page 100000000000000 to the CRM.

The AI client shows a preview first: how many forms the feed would cover. Nothing is sent until you confirm.

How a feed behaves

• It starts when you add it. Leads from before that moment are not pushed. Export those.
• It covers every lead form of that Page or account.
• Nothing of a lead is kept. The server remembers only how far each form has been sent.
• Your system may get a lead twice. If the receiver does not answer, nothing is marked as sent, and the same leads are read and sent again later. The receiver tells them apart by each lead's key.
• Every check is made again at every look. If your write access, the platform's switch or your connection is taken away, the feed stops and you get a notification. It starts again by itself once the cause is gone.
• A feed and your own exports are separate. Neither moves the other's place.

Watch and stop a feed

Lead feeds on History lists each feed with Since, Last look and Leads delivered. A feed that cannot deliver is marked Failing, with the reason under it, and you get one notification for the outage. The server keeps trying, less often while it fails. No lead is skipped while the platform still holds it.

To stop a feed, press Stop pushing beside it, or ask your AI client. Nothing on the platform changes: the leads stay where they are.

When the heading says Switched off, an administrator has not switched lead delivery on, and nothing is read or sent for anyone.