CPV Lab Pro on your landing pages
CPV Lab Pro was built for funnels where the lead and the sale are different moments. Its lead capture campaigns count opt-ins in their own column, next to the conversions the offer reports later, and its campaign setup splits traffic between landing pages and offers by share. LanderLab supplies the page and the opt-in: the visit arrives with CPV Lab's click ID, a hidden field keeps it, and on submit the page's Webhook integration sends it to your CPV Lab's postback URL.
It suits buyers who host their own tracker for control over data and cost, and agencies running several clients on one install. LanderLab stores each lead with its page, variant and UTMs, CPV Lab stores the click, the cost and the revenue, and the postback ties them together.
The opt-in counted where it happens
In a lead capture funnel, the form on the landing page is the first win. When it lives on a LanderLab page, LanderLab posts it to CPV Lab with the click ID the visit arrived with, so the opt-in lands on the campaign, the landing page and the traffic source that produced it. The offer's later conversion comes back on the same click, and the gap between the two columns is your lead quality, by source.
Lead data on the conversion
CPV Lab's postback can carry a status, a transaction ID and up to five custom fields. Send a quiz answer like state or age band in a custom field and it becomes something you can filter conversions by in CPV Lab, while the full lead, every answer included, stays in LanderLab's Leads tab.
A tracker you own, pages you don't have to host
Running CPV Lab Pro on your own server keeps your click and revenue data with you. LanderLab keeps the pages off that server: they're published on your domain from LanderLab, built in an editor instead of uploaded as files, and changed with a republish. Your tracker stays a tracker.
