LeadConduit on your landing pages
LeadConduit is where lead buyers and sellers keep the logic: verify the consent certificate, append data, screen against suppression lists, accept or reject, and deliver to a CRM, a dialer or a buyer. LanderLab is where the lead is made. The page's webhook posts each submit to your flow's posting URL, under its own source, and the flow takes it from there.
That split keeps both sides simple. The page collects the lead and hands it over; the flow holds everything that changes week to week. It fits insurance and mortgage buyers taking leads from several sources, call centers that screen numbers before the dialer, and sellers whose buyer runs LeadConduit and sent them submission docs.
Leads into a LeadConduit flow
Every lead from your LanderLab page goes into a LeadConduit flow, posted by the page's webhook as it's submitted. From there the flow does what you set it up to do: add data to the lead, check it, accept or reject it, and deliver it to your CRM, a buyer or both.
Each source in a flow has its own posting URL, listed in its submission docs with the fields the flow accepts. That's how the flow knows a lead came from your landing pages and not from another vendor, and how its reports keep your numbers apart.
Change the rules without touching the page
The checks and destinations live in the flow, so the page has one job: collect the lead and hand it over. When a buyer tightens their criteria or you add a recipient, you edit the flow, and the page and the ads pointing at it stay as they are.
That also keeps split tests clean. You can test headlines and quiz steps on the page while the flow's acceptance rules stay fixed, and judge the variants on leads the flow accepted.
Screen leads against your lists
LeadConduit can check each lead against suppression lists, such as do-not-call numbers, known litigators or your past customers, and reject a match before it reaches the CRM. Your reps don't call someone who is already a customer, and a number on a do-not-call list never reaches the dialer.
Consent proof checked inside the flow
Turn on TrustedForm for the page and every lead carries a certificate URL that records what the consumer saw and when they submitted. Sent into the flow, it can be retained and verified by LeadConduit's TrustedForm add-on, and a lead whose certificate doesn't hold up never gets bought.
Retaining matters: a TrustedForm certificate that isn't claimed expires after 90 days, and a buyer facing a TCPA complaint months later needs one that didn't.
