Meta's current lead-ads guidance describes an instant form add-on for eligible campaigns using the Leads objective and Website conversion location. The add-on can give a person another way to submit information inside Meta's browser experience, but it does not repair a slow page, broken event, vague offer, or neglected follow-up. This lesson treats the website and instant form as two deliberate completion paths with one acceptance standard.

VISUAL LESSON

What you will learn

  1. 01Verify the current eligible setup.
  2. 02Align website and instant-form fields.
  3. 03Route and compare the two paths honestly.
A website lead path branches into an instant form fallback and rejoins a measured routing pipeline
A browser form add-on should preserve the offer and routing logic while giving eligible visitors another completion path.

ILLUSTRATIVE WORKED EXAMPLE

Compare completion paths without combining them

Website startsIllustrative sessions that began the site path
120
Website submitsMeasured site-form completions
42
Add-on opensEligible browser-form openings
58
Add-on submitsKept as its own source
24
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Configure, preview, and route the add-on

Ad set01Confirm Website conversion

Use the approved objective, Website conversion location, event, budget, audience, and placements; verify current add-on eligibility.

Ad02Open Browser add-ons

Choose the instant form option when available, select or build the approved form, and inspect every preview.

Handoff03Preserve the source

Send website and instant-form records into distinct source values before deduplication, qualification, and response.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Website promise → two completion paths → source-aware handoff

PromiseOne offer and next step
PathsWebsite plus eligible add-on
EvidenceSeparate source and quality

THE LEAD ATLAS METHOD

Lead Atlas Data can research a done-for-you business-contact list for the exact categories, locations, market, and campaign behind the Facebook offer, creating a separately measured prospecting lane.See how custom list research works ↗
01

Define what the add-on must solve

Write the campaign objective, website event, offer, required information, response owner, response window, and qualified-lead rule. Use the add-on to reduce a genuine completion barrier, not to hide a weak page or collect extra data without purpose.

Choose one success hierarchy: accepted lead, booked consultation, qualified request, or another owned outcome. Form submissions are an input to that outcome, not automatic proof of quality.

02

Verify the live eligible configuration

In the current Ads Manager flow, select the approved Leads campaign and Website conversion location. Confirm the destination URL, conversion dataset and event, attribution setting, audience, budget, schedule, and placements before looking for Browser add-ons at the ad level.

If the instant form add-on is absent, do not invent a workaround. Eligibility, controls, and labels can vary. Capture the account, campaign, date, and screen state, then use the supported website path or another approved lead experience.

03

Make both paths agree

Repeat the same core offer, company identity, qualification logic, privacy notice, response expectation, and confirmation step. Ask only fields needed to route or qualify the request, and explain any sensitive question before asking it.

Map each instant-form field to the receiving CRM field. Test required values, country formats, consent language where applicable, hidden campaign identifiers, thank-you action, website link, and what happens when the same person submits twice.

04

Test the full handoff

Submit a clearly labeled test through the website and another through the add-on. Verify timestamps, source and campaign values, field mapping, notifications, owner assignment, duplicate behavior, suppression checks, response tasks, and the conversion event used for optimization.

Preview every selected placement on a phone and inspect the site inside an in-app browser. Keep a fallback export and lead-retrieval procedure if the primary integration pauses, and define who checks for missed records.

05

Measure path and downstream quality

Report opens, starts, submissions, cost, response, acceptance, qualification, booking, sale, duplicates, invalid records, and time to first action by completion path. Compare cohorts only after enough time to mature and keep attribution limitations visible.

Deliverable: campaign brief, eligibility capture, website and instant-form field map, privacy and confirmation copy, placement previews, two test records, routing proof, duplicate rule, response owner, source-separated scorecard, and an evidence-based keep, repair, or remove decision.

THE TAKEAWAY

Keep the website primary, use the add-on only when eligible and purposeful, make both paths promise the same next step, and preserve source through qualification and sales.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.