Meta Ads: Verify Instant Form Delivery

Introduction

A useful handoff ends with a salesperson who can find and act on the right record. A form preview, a connector success message and a CRM contact each tell you something different. This checklist is for a team that already chose an Instant Form and wants to verify the receiving path before sending campaign traffic through it. If a meta ad agency is taking over an existing form, run the check against the version it will actually use.

Use this checklist alongside the broader imagineInk Meta Ads optimization service , which covers campaign and creative decisions. If the open question is whether you should use an Instant Form at all, start with the comparison of lead ads and landing page campaigns . This guide starts after that choice.

Agree the prerequisites with your Meta Ads agency

Write down the Page, exact form name and identifier, connector, destination system and receiving queue. Give each checkpoint a person who can open the right view and confirm the result. Ask the sales owner to name the fields they need for follow-up and any value that sends the record down a different route. Record what should happen if an optional answer is blank. Keep this sheet beside the launch brief so both teams use the same expectations.

Before creating a test lead, agree which approved test values you will send and how you will keep the record out of real customer outreach. Use a controlled destination when available. If you must test a real workflow, arrange a safe test recipient and agree how the team will label and close the record. The guide to designing lead form fields helps if the sales team cannot explain why a field is needed.

Run the test in order and save evidence at each step

Start with one distinct test marker and log the submission time with its time zone. Compare the same record throughout. A screenshot of a random contact with similar details cannot confirm delivery. Capture the smallest evidence needed for your reviewer to trace the test without exposing customer data.

• 1. Create a sample on the exact form. Verify the Page and form before submission and preserve the identifier visible to the tester. Zapier's sample lead guide shows how to create a lead for a selected Page and form and check it in the Zap trigger test.
• 2. Check the connector input. Match the record and inspect the submitted values before interpreting a downstream error. Make's Lead Ads documentation lists a New Lead trigger and a separate Get Lead Details module. If your workflow uses both, keep evidence from both steps. Another connector may expose different checkpoints.
• 3. Read back the CRM record. Match the test marker and compare the actual fields with the agreed mapping. Check whether the connector created a record or updated an existing one, and whether that was the intended behavior. HubSpot documents that leads made with the Facebook testing tool have a source drill-down value of Facebook organic lead in HubSpot. That label alone should not disqualify an otherwise correctly matched test record.
• 4. Verify assignment and notification. Ask the designated recipient to open the record from their own queue or approved test alert and confirm the fields they need. If your launch depends on a branch such as a region assignment or a fallback queue, test that branch separately. Keep the resulting evidence tied to its own test submission.

Fix the first checkpoint that failed

If there is a form submission but no connector input, inspect the selected Page, form identifier, connection and lead access before changing the campaign. For Make, the connector troubleshooting guide recommends checking whether the Make app is subscribed to the Page. If the connector already has the right values but the CRM record is blank, trace the mapping and the destination's validation response. Work from the last confirmed checkpoint rather than changing several settings together.

For example, suppose a sample lands with the right enquiry details but the wrong owner. The capture step worked for that sample. Compare the agreed queue rule with the assigned owner, then have the routing owner investigate the mismatch. Before any retest, keep the failed evidence and check that the next test will not update an earlier sample unexpectedly. Escalate a permissions or data-handling issue to the person who controls that part of the workflow.

Use a pass, hold or unverified handoff record

Record the expected result, observed result, timestamp, evidence reference and responsible person for each step. Mark pass when the same sample reached the intended record, fields and queue and the recipient confirmed the required notification. Mark hold if an observed result disagrees with the requirement. Mark unverified if the evidence is missing or the required branch was outside the test. Keep the decision tied to the exact form and workflow version. For the handoff, write the release decision beside the first missing checkpoint. A record marked hold should name the owner of the fix and the evidence they must return before changing its status.

If the check passes, agree who will verify the first real enquiry under the normal sales process and who owns any exception. Repeat the relevant check after replacing the form or changing a field, connection or assignment rule. Close the test record according to your team's handling procedure and preserve only the evidence the reviewer needs. A successful test can support a launch decision for that route; it does not establish actual lead quality, conversion rates or future delivery.

Sources and how to use them

These sources explain the behavior of specific connectors and the CRM in the examples. Use the documentation for the integration you actually run before treating a field name, source label or permission check as universal. The pass and hold criteria above are a suggested handoff method, not a provider guarantee.

• Zapier: Create sample leads covers form selection and trigger testing.
• Make: Facebook Lead Ads modules describes separate lead trigger and retrieval steps.
• HubSpot: Facebook lead ads FAQ explains the source label on testing-tool leads.
• Make: Facebook Lead Ads troubleshooting covers Page subscription and access checks.