Anu Agency
PlaybookWork with Anu
07.05 Connect Meta lead forms and test them without spending

07.05

Connect Meta lead forms and test them without spending

Map every lead form question to a CRM field and push a free test lead through before any ad goes live.

35 minNeeds verificationChecked 2026-10-20

Video walkthrough

Coming soonYour Meta lead form, mapped and tested for $0
It will cover
  1. Where this fits: the campaign itself is built in Part 06
  2. The field map: every question gets a home in the CRM
  3. HighLevel: Facebook form field mapping and the Lead Form Submitted trigger
  4. Meta's Lead Ads Testing Tool: create, track, delete, repeat
  5. What a passed test looks like in the CRM
This chapter is complete without it. Every step is written out on this page.

What you're building

A Meta (Facebook and Instagram) lead form whose every answer lands in a named CRM field, a workflow that starts the moment the lead arrives, and a passed test using Meta's free Lead Ads Testing Tool. Campaign setup, audiences and Special Ad Category rules are in Part 06; this chapter only covers the connection.

Why it matters

An unmapped question is lost data, and with some integrations an unmapped form means the lead does not enter the workflow at all. Testing with Meta's tool costs nothing and catches this before you pay for real leads that go nowhere.

What you need

  • A published lead form on your Facebook Page (built in Part 06)
  • A Page role of Advertiser or higher on that Page
  • HighLevel with the Facebook integration connected, or Follow Up Boss with a connector that receives Meta leads
  • Your field map (template below)

Time and cost

Time
35 minutes
Cost
$0

Test leads are organic and not tied to any ad, so they cost nothing.

Step by step

  1. Write the field map before you connect anything

    List every question on the lead form and the CRM field it goes to. Create any custom fields you need first (for example Timeline, Price range, Pre-approved). Use the template below.

    Check: Every form question has a CRM field written next to it, and each custom field exists in the CRM.

  2. HighLevel: map the form fields

    Select the form and map each Meta question to its HighLevel field. Use supported custom field types (text, large text, numerical, phone, monetary, single options, date, single-select dropdown). Avoid renaming questions in Meta afterwards; renaming can break the mapping.

    Check: The mapping screen shows every question mapped, with no prompt asking you to map this form.

  3. HighLevel: start a workflow on Facebook Lead Form Submitted

    Add a filter for the specific form, so this workflow fires only for that form. Then add the same steps as your website workflow: tag, Assign to User, Internal Notification. Publish it.

    Check: The workflow shows Published and is filtered to one form.

  4. Follow Up Boss: choose a connector and set the source

    Follow Up Boss receives Meta leads through a connector (for example Zapier's Facebook Lead Ads trigger with a Follow Up Boss "create event" action, or another integration listed in your account). Whatever you use, it should create an event (type General Inquiry or Seller Inquiry), not a bare person, and set a source such as Meta - Buyer lead form so Lead Flow can route it.

    Check: Admin > Lead Flow lists the Meta source with an agent or group after the first test lead.

  5. Send a test lead with Meta's Lead Ads Testing Tool

    1. Open the tool and choose your Page (it lists Pages where you have advertiser access), then the form.
    2. Click Create Lead. It fills dummy data; use Preview Form to type your own test values if available.
    3. Click Track Status until the status changes from pending. Success shows the payload; failure shows an error code.
    4. To test again, click Delete Lead first. Only one test lead can exist per form.

    Check: Track Status shows success, and the test lead appears in your CRM with every mapped field filled.

What success looks like

  • A Meta test lead appears in the CRM within minutes with every answer in its field.
  • It is assigned and the agent is alerted, exactly like a website lead.
  • The lead source reads the form name you chose, so Part 08 can report cost per lead by form.

Copyable templates

csvLead form field map
Meta form question,Meta field type,CRM field,CRM field type,Required
Full name,Prefill,First Name + Last Name,Standard,Yes
Email,Prefill,Email,Standard,Yes
Phone number,Prefill,Phone,Standard,Yes
When are you hoping to move?,Multiple choice,Timeline,Single options,Yes
Which area are you looking in?,Short answer,Area of interest,Text,No
Are you working with a lender yet?,Multiple choice,Pre-approved,Single options,No
Text consent (custom disclaimer checkbox),Checkbox,SMS consent,Single options,No

Try it

Lead Ads Testing ToolCreate Lead
Your published formon your Page
Integrationnative or connector
CRM contactall fields mapped
Workflow / Lead Flowassign + alert
  • Lead Ads Testing TooltoYour published form
  • Your published formtoIntegrationleadgen event
  • IntegrationtoCRM contact
  • CRM contacttoWorkflow / Lead Flow
Testing the Meta connection with no ad spend

How to test it

Run the testing tool once per form. In the CRM, open the new contact and compare each field against the field map. Then confirm assignment and the agent alert. Delete the test lead in the tool and tag the CRM contact test-lead.

Troubleshooting

Track Status stays pending.

Delivery can take a few seconds; click Track Status again. If it never changes, the integration is not subscribed to your Page's leads. Reconnect the Facebook integration with a user who has full Page access.

The lead arrives but some answers are empty.

Those questions are unmapped or mapped to an unsupported custom field type (for example a radio field). Remap to a supported type.

Create Lead is greyed out or errors.

You need an Advertiser role or above on the Page, the form must be published, and an existing test lead must be deleted first.

HighLevel: the workflow fires for the wrong form.

The Facebook Lead Form Submitted trigger has no form filter, so it fires for every form. Add the form filter.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsHow Meta delivers leads

Meta sends a real-time update to a webhook subscribed to the Page's leadgen field. The receiving app must be installed on the Page through its subscribed_apps edge, using a Page access token from someone who can advertise on the Page. The update contains the lead ID; the integration then retrieves the lead's answers. Leads cannot be retrieved by an app in Development mode except those submitted by app role holders.

Test leads can also be created by API with POST /{FORM_ID}/test_leads (Advertiser role or above, Page access token). If you plan to send lead quality back to Meta through the Conversions API later, map the Meta Lead ID to a CRM field now.

Sources

Written from the best available information. One or more steps could not be confirmed; see the notes in the chapter. Last checked 2026-10-20.