Tracking is the most overlooked part of running Meta ads for funding, and the part the large shops care about most. The components are standard — Meta pixel plus the Conversions API, and there is a ten-step build for putting them on a funding page — and the part that matters is a single rule about what gets sent.
The fourth video puts the consequence plainly: a pixel firing on every submission is an instruction to find more people who submit forms, so Meta finds the cheapest possible way to get them. The leads that produces are startups, $5K-a-month businesses, merchants who are over-leveraged into third and fourth positions, merchants who have defaulted before, and spam. None of that is Meta failing. It is Meta doing exactly what it was asked.
The rule
- A submission that clears every gate fires the lead event. Meta reads it as “this is good, find more”.
- A submission that fails a gate is redirected to a separate page — an alternative offer is fine — where no lead event fires. You paid for that click, so the record can still be worked, or sold on where the form’s consent language covers it.
- That data never touches Meta. Not as a lead, not as a lesser event, not at all.
The reason is not subtle. Meta optimises for whatever it is told counts. Send it the $8K-a-month merchant as a conversion and it will find you more $8K merchants, cheaply and at volume, and the cost per lead will look excellent while the funded rate goes to nothing. The drift in lead quality that brokers blame on the platform is very often a pixel firing on a thank-you page that every submission reaches.
The third video puts the reason in one line: the pixel is not there to track your numbers, it is there to tell Meta which leads were good so it knows who to find next. That is also why a pixel seasoned on qualified merchants is the most valuable asset in the account, and why it is what eventually lets simple creative work.
What the setup needs
- Meta pixel plus the Conversions API on the landing page, both firing the same event with the same event ID so Meta keeps one copy rather than two.
- Qualification enforced on the page — revenue and amount bands, time in business, the one-time passcode — so “qualified” is a fact about the submission, not a judgement made later.
- Two destinations after submit: the qualified page, which fires the event, and the disqualified page, which does not.
- Immediate delivery to the CRM by API or webhook, so a qualified lead is called inside sixty seconds.
Own the data end to end. The shops that do well on this channel are the ones that can say, for a given ad, how many submissions it produced, how many qualified, and how many funded — and that starts with the pixel telling the truth about which is which.
Questions brokers ask
Should the Meta pixel fire on every form submission?
No. It fires only when the submission has cleared qualification. Every event is an instruction to find more of that person, so a disqualified submission sent back teaches the campaign to find unfundable merchants.
Where do disqualified applicants go?
To a separate page where no lead event fires — an alternative offer, or a plain thank-you. The point is that the page the pixel watches is only ever reached by qualified submissions.
Do I need the Conversions API or is the pixel enough?
Run both. The browser pixel is blocked by iOS settings, ad blockers and slow pages, so a share of your leads never reaches Meta; the Conversions API sends the same event from your server, where nothing can block it, and carries the hashed contact details that let Meta match it to a click.
Why does lead quality drift on Meta?
Usually because the pixel fires for everyone. Meta finds cheaper form-fillers, cost per lead falls, and funded rate follows it down a month later. Qualified-only events are the fix.
How fast should a qualified lead reach the CRM?
Immediately, by API or webhook, so it is called inside sixty seconds. Speed to lead is a delivery problem, and the delivery is part of the tracking setup.
Alex Makowski
Founder, Infinite Bookings
Runs the lead generation operation behind Infinite Bookings — paid traffic, the funding application, and the delivery pipeline that puts records into brokers’ CRMs.
Reachable directly at alex@infinitebookings.com or 732-609-7182.