Ad review, policies and account issues

What do Meta's lead generation ads terms require from advertisers?

A data notice above the contact fields, a privacy policy page, no question that the profile can answer, and written clearance for sensitive data.

Published

Meta’s terms for lead generation ads are short, and almost all of them are about the data inside the form. The advertiser has to explain why the contact details are collected and who else will see them, link a privacy policy, stop asking for anything the profile already holds, and obtain written clearance before any sensitive question. Consent and legal responsibility come on top.

1. A notice that names the purpose and the recipients

The notice is not optional. Meta requires advertisers to say, above the contact fields, why the information is being collected and how it will be used or shared, as part of the Lead Ads Terms. Everything the data is later used for has to fit inside that statement.

Meta’s own sample promises quotes by email or phone and adds a sentence about trusted partners who may call about financing. The second half of that sentence is where agencies slip. If a lead travels to a dealer, a broker, a franchise or a referral partner, the notice must name the kind of recipient. Meta illustrates the rule with a car brand passing leads to its dealerships and an estate agency passing them to individual realtors.

Write the notice before the form, because it decides who can receive the lead and what the follow-up may say. Keep one approved wording, and check that the form, the CRM and the ad copy agree with it.

2. Written permission before a sensitive question

The Lead Ads section of the Advertising Standards states that certain information may not be requested through lead ads questions unless Meta has given written permission first. In practice the list covers:

  • Money and credit: card and bank numbers, credit score, income, net worth, debt, bankruptcy.
  • Identity documents: Social Security, passport or driving licence numbers.
  • Health: a condition, a treatment, a disability, whether physical or mental.
  • Insurance: a policy number, the insurer, or simply whether the person holds cover.
  • Background: whether someone has been charged with or convicted of a crime.
  • Belonging and beliefs: ethnicity, religion or philosophical view, union membership, sexual orientation or history.
  • Access details: a username, a password, a log-in created inside the form.
  • Accounts: frequent flyer, loyalty card, cable or telephone account numbers.

Political affiliation appears on the same list and needs no permission because it is banned outright. Meta’s Help Center version adds a child’s date of birth, and warns that a form carrying a prohibited question does not run at all.

Insurance deserves a second look. Meta’s own examples of good questions suggest asking whether the applicant currently holds a policy of a given type, while the Standards place that same question behind written permission. The Standards win.

The pattern that works for regulated offers is to move the sensitive question to the phone call. A form with a name and a number clears review; the qualification happens where a person can explain why the detail is needed.

3. Never ask what the profile can answer

Prefill takes its answers from the Facebook or Instagram profile: contact details, name, demographic fields such as date of birth or marital status, and work details such as job title. Every prefilled answer stays editable except the date of birth.

The Standards forbid requesting information that is the same, or substantially the same, as something a prefill question could supply, and they name the date of birth prefill as the sanctioned way to learn age. Custom questions therefore belong to what Meta cannot know: the timeline, the service required, the location.

The commercial logic runs the same way. Every box a person has to type costs submissions, and the profile already holds most of what a lead gen form asks.

4. A policy page, not a file

Meta’s setup guide treats the privacy policy link as optional. Its overview of instant forms says a policy is required for the form to run. Take the strict reading: the link costs nothing and removes the argument.

Your existing site policy is enough, provided the link opens a page. A policy delivered as a PDF, an image or a download breaks the flow and invites a rejection.

A marketing checkbox comes from a custom disclaimer. It cannot be attached to a form that is already running, so the method is to duplicate the form, build the copy with the disclaimer, and move traffic to it.

Under GDPR, Meta states that it and the advertiser are both data controllers for lead ads. The lawful basis is the advertiser’s decision, and the notice is where that decision becomes public: any use beyond the stated purpose is a problem created by a form you approved.

That has a consequence lead buyers tend to miss. Data received from a partner carries the partner’s notice, not yours, so the purposes written there set the ceiling on what you may do with it.

Rules that arrive alongside the terms

  • Special ad categories. Housing, employment and financial services offers aimed at the US or Canada face extra restrictions on age, gender, marital status and location fields.
  • The promise in the intro. An intro that says two hours, followed by a call the next afternoon, is a different kind of failure, but the same principle applies: the form commits you to what it says. The conventions are in Facebook lead ads best practices.
  • The bid strategy, indirectly. A cost per result goal set below your break-even CPL buys volume that the notice never described, so the target and the terms are best read together in cost cap vs bid cap.
  • The account structure. One form per offer is easier to keep compliant than a shared form with a partner name hidden in a field, as Facebook ads account structure sets out.

A checklist before the form goes live

  1. The notice sits above the contact fields and names both the purpose and any partner who receives the lead.
  2. The privacy policy is linked as a page.
  3. Prefill covers what the profile holds, with custom questions only for the rest.
  4. Nothing from the permission list appears in the form without written clearance.
  5. The marketing checkbox exists before the form starts running, not after.
  6. Meta’s lead ID and the ad ID are stored with every lead, so any record can be traced to the ad behind it.

The last item is not a Meta demand, and it is what makes the other five auditable. The questions on ad review, policies and account issues cover what happens when a form or an ad is turned down on these grounds, and Meta Pixel setup covers the tracking half of the same problem.

Questions on this topic

All questions on this topic →

FAQ

Is the privacy policy link required on an Instant Form?+

Meta's own documentation disagrees with itself. The setup guide treats the link as optional, the instant forms overview says a policy is needed for the form to run. Take the strict version, and link a page rather than a PDF or an image.

Can I ask about health or finances on a lead form?+

Only with Meta's prior written permission. The Lead Ads section of the Advertising Standards puts health, money, insurance, identity documents, criminal history and several other categories behind that requirement.

Who carries the legal responsibility under GDPR?+

Both sides. Meta describes itself and the advertiser as data controllers for lead ads, so the lawful basis, and the limit on what you may do with the data, remain yours to define. The notice is where that choice becomes visible.

Can a consent checkbox be added to a live form?+

No. A custom disclaimer cannot be attached to a form that is already running, so the working method is to duplicate the form, add the checkbox to the copy, and move traffic to it.

Ready to find out what
converts, for real?

Free to start.

Start free →