
Your form brings in enquiries and the cost per lead looks good. Then you get on a call and find that the budget or project doesn't fit. Some contacts never pick up.
If every enquiry triggers the same success event, Meta misses the distinction that matters to you. Build it into the form: answers that fit take the lead path, others get a different route.
Your form logic, tracking and campaign goal need to work together. The route depends on where you qualify the lead:
“Filled in the form” often isn't enough. Ask about what determines whether you can work with this person.
A fictional example: A contractor wants complete bathroom renovation projects. They set four criteria for this campaign:
| Criterion | Answer that fits |
|---|---|
| Project | Complete bathroom renovation |
| Location | Within the contractor's service area |
| Budget | At least €15,000 |
| Timing | Start within the next three months |
The values are made up, not an industry benchmark or pricing recommendation. Set your own limits based on your offer and capacity.
All four answers need to fit. Enough budget doesn't make up for the wrong location. A missing answer doesn't count as a yes either.
The form prequalifies the person. A conversation confirms whether the project and budget really fit.
Every question needs a consequence. If the answer doesn't change your next step, you probably don't need it for this filter.
You've set the criteria. Now decide what happens after each answer.
| Answers | Next step |
|---|---|
| All criteria met | Submit the enquiry and trigger the chosen lead signal |
| Project fits, start date is later | Offer a later follow-up or relevant information |
| Requested service isn't offered | End the path with a clear explanation |
| An important answer is missing | Ask for it or treat the enquiry as unresolved |
Someone who wants to start in a year could become a good customer later. They still meet different criteria for this campaign.
If you save those enquiries, give them their own CRM status and next step.
On your website, you control which event goes to Meta. For our example contractor, the route looks like this:
You can keep an enquiry with a later start date in your CRM. It doesn't get the selected Lead event.
Check three places:
You can record all enquiries separately and use another signal for matching ones. That signal must be available and selected as the optimization goal in your setup.
For the Pixel and Conversions API, apply the same rule to both routes. If the browser and server send the same action, it needs to be recognized as one event. See our server-side tracking and CAPI guide.
GTM needs the data for your filter. Answers sitting in your form or CRM aren't automatically available to Tag Manager.
The data layer is the handoff between your form and tracking. It carries an event and the values GTM uses to decide which tag fires. Google: Data layer.
You can check the criteria in two places:
lead_qualified: true. GTM doesn't need all the answers again.In our example, the form logic decides. It passes the result only after the enquiry has been saved successfully:
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: 'lead_form_success',
form_id: 'bathroom_renovation',
lead_qualified: true
});
The names are examples and must match in your form and GTM. true is a Boolean, not text. The snippet doesn't replace checking the answers or saving the enquiry.
Set up GTM like this:
form_id and lead_qualified.lead_form_success. It fires only for the correct form ID and lead_qualified: true.Lead event. Google: Custom Event trigger.For every other successfully saved enquiry, explicitly pass false. Put the event and values in the same push so an old true doesn't carry over to the next submission.
A data layer event isn't a Meta event yet. The tag sends the signal. The filter values don't have to go to Meta or GA4 as event parameters.
This example doesn't need names, email addresses or free-text answers. Your Meta tag's consent rules still apply.
An Instant Form doesn't pass through your website's data layer. Qualification feedback sent directly from your backend doesn't need a browser data layer push either.
The form stays on Facebook or Instagram. Use form logic to create a lead path and an ending without a lead submission. Meta describes lead filtering based on multiple-choice answers. Meta: Lead filtering.
For our example contractor:
An extra question alone doesn't filter anything. If every answer allows the same submission, you still get the same native leads.
Once the Instant Form is submitted, Meta knows about that lead. Filtering it out in your CRM later doesn't undo the submission.
If you want to collect contacts for later too, you can let them submit. You'll then need CRM feedback to tell Meta about the different outcomes. Meta Lead Generation Guide.
Perhaps the person misunderstood the budget or meant a different service. You find that out on the phone.
Create a clear CRM status, such as “Project and budget confirmed on the call.” The right integration sends it back to Meta through the Conversions API.
The status needs to be linked to the original lead. A Meta integration example shows this using the lead ID and status changes.
For Instant Forms, you also need the right performance goal for conversion leads or qualified leads, where available in your account and integration. Meta: CRM and lead quality.
A connector that only copies enquiries into your CRM doesn't handle this feedback.
Choose a stage that tells you something about quality and happens regularly. With few closed deals, an earlier qualification stage can be more useful. Check the available signals and how long feedback takes.
Send test enquiries through the form. Check the form, CRM and Events Manager, plus Preview with Tag Assistant if you use GTM.
false instead of the previous true.The Instant Form's non-lead path must prevent submission. For website forms, no second integration should bypass the filter. Your Meta tag still needs to respect consent conditions.
The cost per enquiry can rise when fewer people can submit. What matters is the cost of a confirmed suitable enquiry.
Fictional calculation, not results from a client account: Both versions get €1,000 in ad spend and use the same qualification rule.
In this calculation, the second version brings twice as many confirmed suitable contacts for the same ad spend.
That doesn't tell you the profit yet. Check which contacts become customers, which jobs you win and what's left after delivery and acquisition costs. Our CAC guide helps with the full cost.
Compare contacts that have had enough time for follow-up and qualification. Today's fresh enquiries aren't a useful comparison with fully processed contacts from last month.
Review your criteria and follow-up process too. A tight filter can exclude potential customers. A good filter doesn't help much if suitable enquiries don't get a call back.
It gives you an answer. For optimization, that answer needs to change the form path or the signal. If the outcome stays the same, you've only collected more information.
You can follow up with saved contacts separately, for example for a later start. They must not trigger the same qualification signal. An Instant Form can prevent submission in the first place.
Here, it means a separate event this campaign doesn't optimize for. The name doesn't create a special Meta setting. What matters is the selected goal in the ad set.
The signal directs delivery towards the selected action. Form answers are still self-reported. Keep checking contactability, actual needs and closed deals in your CRM.
Set your criteria and build the form paths. Once the event and campaign goal match, measure which enquiries become customers.
Want to set this up for your business? Let's talk. Tell us which customers you want to win and where things get stuck. We'll look at the campaign, form and steps through to the sale together.