Instant Forms — builder guide

Page (Facebook page), form name, privacy policy URL and follow-up (website) URL — Meta rejects the create without them. The data-use description (the text above the contact fields) is also required and arrives prefilled with a house default.

The welcome screen (headline max 60 chars + description) is optional but strongly recommended — it holds the full job-ad or offer text people see before the questions.

Every question and answer automatically gets a clean, accent- and punctuation-free key derived from its full text plus a date suffix (e.g. machine_operator_experience_180726). The key becomes the CSV/CRM column name — you can override it by hand, the ↻ icon regenerates it, and the top “Refresh keys + date” button refreshes all of them at once.

The visible question/answer text can contain anything — the discipline applies to keys only.

In simple mode you add questions and answers field by field. In text mode one line per question: Question :: key :: Answer 1 | Answer 2 | Answer 3 (leave the key empty — it is auto-generated). A line without answers becomes a free-text question; choice questions need at least 2 answers.

Meta's hard cap: 15 questions total (prebuilt fields + custom questions combined) — the builder shows a live counter.

Any answer can be flagged Disqualifies (text mode: ! prefix). A lead picking that answer is automatically set to Disqualified: it still arrives, but is filtered from the default view and downstream routing. The CSV always includes it with a qualified column — false negatives can be overridden manually.

Sharing defaults to OPEN (anyone can submit a shared ad's form) — Meta's own default would be Restricted; AdsPilot sets it explicitly. Switch to Restricted with one toggle.

Tracking (utm) parameters are invisible to the person filling the form but attached to every lead — the *.* placeholders in campaign/content fields must be replaced, otherwise the builder blocks the create.

A published form cannot be modified even through the Meta API. The form viewer's “Edit as copy” button prefills the builder and names the new form vN+1 automatically (v2, v3, …) — versions stay traceable and the old form can be archived.