ClickFlare on your landing pages
ClickFlare already knows the click: the traffic source, the ad, the keyword and what it cost. What it can't see is the form on your landing page, and that's where a lead gen campaign makes or loses money. Pair the two and every submit on a LanderLab page or quiz goes back to ClickFlare as a server-to-server postback with the click ID ClickFlare sent, so the lead sits on the same row as the spend.
For a media buyer that means a cost per lead you can act on, by campaign, ad, keyword and landing page variant. Pause the ad sets that buy page views instead of leads, push budget to the ones that fill the form, and stop matching a tracker export against a lead export at the end of the day.
It's also the pairing LanderLab covers most closely: ClickFlare has its own setup guide in LanderLab's docs, its own Add to Tracker shortcut on every published page, and its own action in Workflows (beta).
A ClickFlare postback on every lead
ClickFlare sends the click to your LanderLab page with its click ID on the URL. When the visitor sends the form, LanderLab fires a server-to-server postback to your ClickFlare tracking domain with that ID, and the lead is counted against the campaign, ad and keyword that bought the click.
Send form fields in ClickFlare's param1 to param20 to see the lead's name, email and phone on the conversion, and mark it as a Lead with ClickFlare's conversion type, so form fills and the sales your offers post later sit in separate columns.
Match data ClickFlare can pass to Meta
With the email and phone on the conversion, ClickFlare can forward the lead to Meta through the Conversions API. Meta gets more to match the lead to a person, and more to optimize the campaign on. Your ad sets learn from people who filled the form, not from people who loaded the page.
Google Ads traffic without a redirect
With direct tracking on Google Ads, there is no redirect to put the click ID on the URL. Add the ClickFlare tracking script to the page and LanderLab reads the click ID from ClickFlare's cookie instead. The postback and the lead data stay the same, so search campaigns report cost per lead by keyword like your redirect campaigns do.
Landing page split tests judged on cost per lead
LanderLab sends the A/B variant the visitor saw with every lead. Put it in one of ClickFlare's params and each variant has its own leads and cost per lead next to the source and the ad, which is a better verdict than a form-fill rate in the page builder.
ClickFlare's AI Smart Traffic can then do the reweighting for you across landing pages, offers and paths, on EPV, CTR, conversion rate or ROI. It runs on redirect campaigns: direct tracking can't split traffic between landing pages.
From published page to live campaign, faster
Add to Tracker turns a published LanderLab page into a ClickFlare landing page without copying URLs or retyping tokens, and offers to put ClickFlare's script in the page's custom code for campaigns that run without a redirect. When only some leads should count, a workflow's ClickFlare action can post just the completed quizzes or just the US leads.
