Tracking is the most overlooked part of running Meta ads for funding, and the part the large shops care about most. The setup is standard — Meta pixel plus the Conversions API, any generic tutorial will do — and the part that matters is a single rule about what gets sent.
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.
- 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.
What the setup needs
- Meta pixel plus the Conversions API on the landing page. Any standard tutorial covers it, and it works for an MCA funnel unchanged.
- 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
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.
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.
Run both. The Conversions API is server-side and survives browser blocking; the standard pixel-plus-CAPI setup from any generic tutorial works for an MCA funnel without changes.
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.
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.