Skip to content

Matching Facebook form questions to CRM fields

Every Facebook lead form asks its own questions. A course enquiry and a consultation request might share a phone number and little else. So each form is mapped on its own: for every question you choose which CRM field the answer goes into.

Before you start

  • You need the tenant.integrations.manage permission.
  • To create a new custom field from this screen you also need tenant.custom_fields.manage.
  • Meta Lead Ads must be connected. See Connecting Facebook and Instagram lead ads.

Steps

  1. Go to Integrations → Lead sources → Meta Lead Ads.
  2. Under 3. Lead forms and their fields, find the form. If a new form is missing, click Refresh forms.
  3. Click Map fields.
  4. For each question, choose where its answer goes under Goes into:
    • Lead details: Name, Phone, Email, City, State, Requirement (notes), or Do not import.
    • Your custom fields: any active lead custom field.
    • + Create a new custom field…: enter a field name and choose a type. For a question with options, a dropdown or "choose several" field gets Facebook's options.
  5. Check the Preview on the right. It shows the latest lead from this form, or a sample, filled in through the mapping.
  6. Click Save mapping for this form.

Name, phone, email, city and state are filled in automatically even before you map anything.

The form's status

Status What it means
Not configured Nobody has saved a mapping and no leads have arrived from it yet
Mapping required Leads are arriving, and their extra answers are going into the notes
Partially mapped Saved, but some questions have no field chosen
Fully mapped Every question has somewhere to go
Questions unavailable Facebook did not send this form's questions. See the table at the end

How answers are stored

  • An answer must fit its field. A number field only takes a number, a date field a date, and a dropdown one of its options. Options are matched by their label or value, ignoring capitals.
  • An answer that does not fit is never lost. It goes into the lead's notes as "Question: answer", and the rest of the lead is still created.
  • An unmapped question goes into the notes in the same way.
  • The original Facebook response is kept with every lead, whatever the mapping says.
  • Creating a field reuses an existing one. If an active field with the same name and type exists, it is used instead of making a duplicate.

Leads that arrived earlier

If leads came in before you saved the mapping, the Earlier leads card offers Reprocess earlier leads. Reprocessing:

  • creates any lead that could not be taken in before, and
  • fills in custom fields that a lead has no answer for yet.

It never changes an answer a lead already has, and it never creates a second lead for the same enquiry. You can run it as often as you like.

What this affects elsewhere

  • Mapped custom fields appear on the lead's page like any other custom field.
  • A field created here is an ordinary custom field. You manage it later in Custom fields.

What you cannot change later

A custom field's type freezes once any lead has an answer in it. Choose the type carefully when you create one here. See Custom fields.

If it does not work

What you see What it means What to do
Questions unavailable The token cannot read this form's questions Save a token with leads_retrieval and pages_manage_metadata, then Refresh from Facebook. Leads still arrive meanwhile, with extra answers in the notes
No + Create a new custom field… option You do not have tenant.custom_fields.manage Ask an Owner or Administrator, or choose an existing field
An answer keeps landing in the notes It does not fit the field's type or options Add the missing option to the field, or change the mapping to a text field
A new form is not listed The list was read before the form existed Click Refresh forms

Last checked against the product on 2026-11-07. Needs the tenant.integrations.manage permission.