Meta Conversions API on your landing pages
If you buy Facebook and Instagram traffic, Meta's delivery decides who sees your next ad, and it decides from the conversions it can see. A pixel that misses a share of your leads hands it a smaller, skewed sample: ad sets look worse than they are, cost per lead in Ads Manager runs above what your CRM says, and the algorithm keeps finding the wrong people.
LanderLab connects to Meta from both sides with one Pixel ID. The Meta Pixel reports from the visitor's browser, and Meta CAPI sends events from LanderLab's server. Both are saved to your LanderLab account once, so every new landing page and quiz picks them from a list instead of starting over.
It's built for media buyers whose budget runs through Meta: lead gen on insurance, solar and debt relief quizzes, ecom offers sold through an advertorial, agencies running a pixel per client. Every lead your page collects becomes a signal Meta can learn from, not just the ones a browser let through.
Meta Conversions API and Pixel on one page
The Pixel and CAPI aren't an either-or. LanderLab runs the Meta Pixel from the browser and the Conversions API from its own server, on the variants you choose. Conversion events then go to Meta from LanderLab's server, where an ad blocker or a cookie setting in the visitor's browser can't stop them.
Run the Pixel with the same ID and Meta hears from both the browser and the server, two sources it can match against each other.
Leads Meta can optimize on
Meta's delivery learns from the conversions it sees. When a pixel fire is blocked, the lead still reaches your CRM but not Meta. Sent from the server, the event reaches Meta whatever the browser allows.
That gap matters most when you're testing. A new ad set with twenty real leads and fourteen reported ones gets cut on the wrong number. Close the gap and the ad sets you kill are the ones that actually lost.
Optimize Meta on qualified leads, not every form fill
A cheap lead from a renter on a roofing quiz is still a conversion to Meta, and Meta will happily find you more renters. LanderLab's Workflows (beta) can sit between the lead and Meta: a Lead trigger on the page, a Filter or an If on the answers that make a lead sellable, and a Meta CAPI action only on the branch that passes.
Meta then optimizes toward the leads your buyer pays for. Every other lead still lands in your Leads tab, your CRM and your sheet as usual, and the Runs view shows which path each one took.
Quiz funnels: count the finish, not the first tap
On a five-step quiz, the moment that matters is the final submit, and that's when the quiz can send Meta its Lead: a short listener in the quiz's JS Code tab fires it, so the event counts people who finished, not people who tapped the first answer.
Visitors who drop out halfway are still useful to you: on Scale and up, LanderLab keeps what they entered as Partial leads in its Leads tab. They just don't become Meta conversions, so your ad sets aren't trained on people who quit at question two.
