Facebook Lead Ads Testing Tool: How to Create a Test Lead (Step by Step)

You built the lead form, connected your CRM, and now there is one question left: will a real lead actually arrive? The only honest way to know is to send one. Meta has a free tool built for exactly this, the Facebook Lead Ads Testing Tool, and it is one of the most useful and least explained pages Meta has.

This guide shows you where the tool is, how to create a test lead in about two minutes, what the test lead really contains, how to read Track Status, and how to fix every common reason a Facebook test lead never shows up in your CRM.

What is the Facebook Lead Ads Testing Tool?

The Lead Ads Testing Tool is a page inside Meta for Developers that submits a test lead through one of your real Instant Forms. It does not need an ad, a campaign or a budget. The test lead is created on your Page exactly as if someone had filled in the form, so Meta sends it to every app connected to that Page: your CRM, Zapier, Make, LeadSender, or your own webhook.

That is what makes it useful. A preview in Ads Manager shows you what the form looks like. The testing tool shows you whether the form actually works, all the way from Facebook to wherever your leads need to end up. Everything that can break between those two points (permissions, a disconnected integration, a wrong field mapping) shows up in a test lead before it can cost you a real one.

What you need before you start

Most “the tool does not work” problems are really one of these four things missing. Check them first and the rest takes two minutes.

• A published Instant Form. The form has to exist on the Page. Draft forms and forms from a different Page will not appear in the drop-down.
• Advertiser access or higher on the Page. Meta's own documentation lists this as the requirement. If you can see the Page but not create leads, your role is the first thing to check.
• Lead access, if your business uses Lead Access Manager. In Business Settings, under Integrations, Lead Access, a business can restrict who and which apps can see leads. Both you and your CRM app need access there.
• Your CRM already connected to the Page. The tool only proves delivery to apps that are already connected. Connect your CRM, Zapier or LeadSender first, then test.

How to create a test lead with the Lead Ads Testing Tool

Here is the full walkthrough, from opening the tool to seeing the lead in your CRM.

① Select your Page② Select your form

Once you click Create Lead, Meta confirms it at the top of the tool: “Your test lead has been sent. To create a new lead, please delete this one.” That message means Meta created the lead and started delivering it to every app connected to your Page.

✓ Test lead sent

Try our FREE Meta Lead Ads Testing Tool

Prefer not to use Meta's developer site? We built a free version of the same tool. It creates the same official Meta test lead, but in four plain steps, and it emails the test lead to you so you can see every answer without opening your CRM.

Create Lead or Preview Form: which should you use?

Both buttons create the same kind of test lead. The difference is what is inside it.

Our advice: use Create Lead once to confirm the connection, then use Preview Form with your own name, email and phone number for the real test. Placeholder values are exactly what trips up a lot of CRMs, and a dummy email address will never show you whether your welcome email actually sends.

What a Facebook test lead actually contains

This is the part most guides skip, and it explains half of the “my test lead looks broken” questions. A test lead made with Create Lead fills each field with a placeholder in this style:

Three things follow from this, and each one explains a common surprise:

• A CRM that validates fields can reject it. A phone field that expects digits (the placeholder phone is text, not a number), or a name field with a character limit, may refuse the placeholder text. The lead then looks “lost” when it was actually rejected. Preview Form with realistic values avoids this.
• Custom questions show up by their key. The placeholder names the question's internal key, not the friendly label, which tells you exactly what key your integration has to map.
• There is no ad or campaign name. If your CRM shows the campaign as blank, or your automation only runs for a specific campaign, a test lead will look incomplete or skip that automation entirely. That is expected, not a bug.

What your webhook receives

If you are a developer, or you want to see what your CRM actually gets, Meta sends the test lead to each connected app as a leadgen webhook, the same as a real lead. The notification carries IDs, not the answers themselves. It looks like this:

{
  "object": "page",
  "entry": [{
    "id": "PAGE_ID",
    "time": 1727520000,
    "changes": [{
      "field": "leadgen",
      "value": {
        "leadgen_id": "LEAD_ID",
        "page_id": "PAGE_ID",
        "form_id": "FORM_ID",
        "created_time": 1727520000
      }
    }]
  }]
}

The receiving app then uses the leadgen_id to fetch the actual answers from the Graph API. A real lead from an ad usually also carries the ad and ad group IDs; a test lead does not, which is how you can tell them apart in your own logs.

How to read Track Status

Track Status is the most useful button on the page, because it tells you which side a problem is on. Each app connected to your Page gets its own row:

Seeing an app you do not recognize in that list is worth a second look too. Every app there receives every lead from the Page. Old integrations you stopped using can be removed in Business Settings, under Integrations, Lead Access.

Deleting a test lead and sending another

Meta allows one test lead per form for each person at a time. Try to create a second and the tool refuses until the first is gone. To test again:

1. Select the same Page and form.
2. Click Delete Lead.
3. Click Create Lead or Preview Form again.

Deleting only removes the test lead from Facebook. Anything it already created in your CRM, sheet or inbox stays there. See cleaning up test leads below.

Other ways to test a Facebook lead form

The testing tool is the right choice most of the time, but it is not the only way to run a Facebook lead form test. Here is how the options compare:

Submitting the form yourself

Filling in your own live ad on your phone is the most realistic test, because it covers the ad, the form, and delivery in one go. The catch: it creates a real lead that counts in your results and your cost per lead. Do it once before launch, not as a routine check.

The Graph API test_leads endpoint

Developers can create the same kind of test lead without the website, by sending a POST to /{form_id}/test_leads with a Page access token, optionally with your own field_data. The same one test lead per form rule applies, and DELETE on the same edge removes it. Meta documents this on its lead ads testing and troubleshooting page.

Your delivery tool's own test

Most lead delivery tools have a test button of their own. In LeadSender, Send a test lead takes the most recent real lead from your form, runs it through the field mapping you set up, sends it to your destination and shows you exactly what arrived. That tests the part the Meta tool cannot: whether real answers, not placeholders, land in the right fields.

Test lead vs real lead: what is different?

When the test lead does not arrive

Start with Track Status. It tells you whether the problem is between Facebook and your app, or inside your app. Then find your symptom here:

A CRM testing checklist

Run through this once for every new form and every new integration, before any money goes into ads:

1. Create Lead once to confirm the connection. Track Status should show success for your CRM's app.
2. Delete it, then use Preview Form with your own name, email and phone number.
3. Find the lead in your CRM and check name, email and phone are in their proper fields, not lumped into a note.
4. Check every custom question landed in the field you mapped it to.
5. Check the follow up: did your welcome email, text or task actually fire, and did it reach your inbox and phone?
6. Check the notification: did the person who should call the lead actually hear about it?
7. Clean up the test records, then launch.

If you want the email and SMS part of that list handled for you, LeadSender can send every lead to Email, SMS, Google Sheets or CRMs like HubSpot, GoHighLevel and Salesforce within seconds, and this guide covers lead alerts in detail.

Cleaning up test leads afterwards

Deleting the test lead in Meta's tool does not reach into your other systems. Before launch, remove:

• The test contact or lead in your CRM, including any deals or tasks it created.
• Any rows it added to a Google Sheet.
• Anyone it enrolled in an email or SMS sequence, so reporting starts clean.

One habit makes this painless: when you use Preview Form, put “Test” in the last name field. Every test record then turns up in one search, and nobody on your sales team mistakes it for a real person.

Facebook Lead Ads Testing Tool: FAQs

Before you launch

A two minute test with the Lead Ads Testing Tool is the cheapest insurance in Facebook advertising. It is far better to find a broken connection with a test lead than with a real person who filled in your form and never heard back. If you are still building the campaign itself, our guide on how to create Facebook lead ads walks through the whole setup, and if you ever need your leads as a file, here is how to download them. Once your test lead lands where it should, the only thing left is making sure every real one does too, in seconds, every time.