LeadProsper integration

Every hour a solar or insurance lead sits unposted, it's worth less to the buyer. LanderLab posts each one into your LeadProsper campaign the second it's submitted, in the exact fields your Supplier API Specs ask for.

  • Built-in integration
  • Landing pages, Quiz funnels, Workflows (beta)

Why connect it

Why LeadProsper and LanderLab

  • Posted while the homeowner is still on the page

    Each submit goes to LeadProsper in real time. Installers and agencies get the lead while it's fresh, which is when they pay for it and keep it.

  • Bad leads rejected before a buyer sees them

    LeadProsper validates every field against the campaign: a 10-digit phone, a valid email. A lead that fails is rejected on arrival, so it never comes back to you as a return.

  • Certificates in LeadProsper's default fields

    LeadProsper has trustedform_cert_url and jornaya_leadid fields on every campaign. With TrustedForm or Jornaya on the page, the certificate fills them on every lead.

  • Ad-level attribution in lp_subid1 and lp_subid2

    Send the campaign and the ad set, captured from the URL by hidden fields, in LeadProsper's two predefined sub ID fields, and its reports show accepts and revenue by ad.

  • Test leads that cost nothing

    A supplier in test mode sends nothing to buyers and incurs no charges, so you confirm the page before the first paid click.

  • One quiz, many bidders

    With Ping-Post, buyers bid on the ping and the full lead goes only to the winner, so one solar quiz can sell into a whole exchange.

LeadProsper on your landing pages

LeadProsper decides where a lead goes and what it's worth. LanderLab builds the pages and quiz funnels that produce it. Connect the two and each submit becomes a supplier post into your LeadProsper campaign, by Direct Post or Ping-Post, without a developer, a posting script or a Zap between them.

It's for lead generators with owned-and-operated pages, affiliates supplying a buyer's LeadProsper campaign, and agencies running solar, home services or insurance traffic. What you get is faster delivery, attribution in LeadProsper's own sub ID fields, and a consent certificate on every lead for the buyers that require one.

Send leads to a LeadProsper campaign

LanderLab posts each submit into the campaign as one of its suppliers, every field under the name the campaign's Supplier API Specs use, alongside any static fields the campaign asks for.

Next to the form fields you can keep LanderLab's own: the page URL, IP address, user agent, submit time and variant ID. Buyers who check consent get the page and the IP, and you get the variant on every lead.

Bad leads stop at the door

LeadProsper checks each lead against the campaign's fields and formats: a phone number needs 10 digits, an email has to be valid. A lead that fails is rejected as it arrives, so it never reaches a buyer and never comes back to you as a return.

Sub IDs and certificates in LeadProsper's own fields

Every campaign has two predefined sub ID fields, lp_subid1 and lp_subid2. Send your utm_campaign in one and the ad set or creative in the other, and LeadProsper's reports show which ads produce leads that sell, not just leads.

For buyers that require proof of consent, LeadProsper has default trustedform_cert_url and jornaya_leadid fields. LanderLab's TrustedForm and Jornaya integrations fill them on every lead from the page.

Test before you pay for traffic

Keep your supplier in LeadProsper's test mode while you build the page. Test leads aren't sent to buyers and don't incur charges, so you can confirm every field is accepted before the first paid click lands.

Use cases

Ways to use LeadProsper on paid traffic

  • 01

    Solar quotes on Meta

    A homeowner quiz asks about the roof, the electric bill and ownership, then posts to a LeadProsper Ping-Post campaign. Installers bid on the ping, and the full lead goes only to the winner.

  • 02

    An owned site with several verticals

    A lead gen company runs separate pages for roofing, windows and HVAC, each posting to its own LeadProsper campaign, with the variant ID kept so lead quality can be compared per variant.

  • 03

    Supplying a buyer's campaign

    An affiliate supplying a buyer's LeadProsper campaign posts into it directly, with lp_subid1 carrying the campaign so both sides read the same numbers.

FAQ

LeadProsper integration FAQ

Anything not here, ask us.

LeadProsper and LanderLab

Is LeadProsper worth connecting to my landing pages?

If your leads sell through LeadProsper, yes. They arrive in real time, validated against the campaign, with sub IDs and certificates in LeadProsper's own fields.

Does LanderLab support Direct Post and Ping-Post?

Yes, both. Each page uses whichever the campaign is set up for.

Do I need Zapier to send leads to LeadProsper?

No. LanderLab posts each lead to LeadProsper itself when the form is sent.

Can I send quiz answers to LeadProsper?

Yes. Each quiz answer is a field, sent under the name the campaign's specs use.

How do I keep test leads away from buyers?

Use LeadProsper's supplier test mode while you build. Test leads aren't sent to buyers and don't incur charges.

Can LeadProsper see which ad the lead came from?

Yes. Hidden fields capture utm_campaign or a click ID from the URL, and they go to LeadProsper as lp_subid1 and lp_subid2.

Other integrations

Plug in the rest of your stack.

Connect LeadProsper and launch your next page.

Build the page, switch LeadProsper on and send your ads to it. Free to start, no card.

From one prompt to qualified leads

Watch one prompt become a live solar quote funnel, every lead routed to your buyer, and the leaks flagged before they eat your budget.

0:00
0:59