Binom integration

Binom can break a campaign down by source, path and placement, but only on the conversions it gets. LanderLab posts every lead to your Binom with its click ID, so each placement shows leads, not just clicks.

  • Webhook
  • Landing pages, Quiz funnels, Workflows (beta, by HTTP Request)

Why connect it

Why Binom and LanderLab

  • Leads per placement, not clicks per placement

    With leads posted back, Binom's token reports show which zones, sites and widgets fill the form, so you blacklist the ones that only burn budget.

  • Your data stays on your server

    Run Binom self-hosted and the conversions from your pages land next to the clicks and costs you already keep there, not on a tracking vendor's servers.

  • Statuses that follow the lead

    Binom's conversion status is free text, and its status schemes can turn a later reject into a rejected lead, so placement reports reflect leads your buyer kept.

  • Landing page rotation with a lead count behind it

    Put several LanderLab pages in one path, weight them or let Smart Rotation decide, and each landing page's leads come back on the same report.

  • Tracking kept on the way to the offer

    Pass Through URL Params forwards Binom's click ID and your tokens to every link on the page, so the offer step keeps the tracking too.

Binom on your landing pages

Binom redirects the click to your LanderLab page with its click ID on the URL and logs everything it knows about the visit: the source, the campaign, the tokens your traffic source passes. The form is where the value shows up, and the page sends it back: a hidden field keeps Binom's click ID, and on submit the page's Webhook integration calls your Binom postback URL with it, so the lead joins the click already on record.

It fits push, pop and native buyers who run Binom on their own server, or on Binom's cloud plans, and want lead data to live where their clicks and costs already are. LanderLab builds and hosts the pages, Binom decides who sees which one, and every lead closes the loop.

Binom postbacks from your LanderLab form

Binom redirects the click to your LanderLab page with its click ID on the URL, and Pass Through URL Params keeps that ID on every link out of the page. When the visitor sends the form, the conversion is posted back to your own Binom with the click ID, server to server, and matched to the click Binom already logged.

Tracking data on a server you run

Host Binom yourself and the conversions from your pages land on your server, next to the clicks and costs you already keep there. What each offer and source earns stays with you, not on a tracking vendor's servers. If you'd rather not run a server, Binom's cloud plans work the same way from LanderLab's side: the postback goes to your Binom domain either way.

Cut the placements that only send clicks

Binom groups reports several levels deep, by source, campaign and the placement tokens your traffic source passes. With leads posted back, you see which placements fill the form and which only send clicks, and can cut the second group at the source before it spends more.

On push and pop, where one campaign can touch thousands of zones in a day, that's the difference between a campaign you scale and one you kill on a hunch.

Rotate landing pages on leads, then move the weight

Binom's paths take several landing pages with weights, and its rules split traffic by country, OS or device before it gets there. Build two or three LanderLab variants of the same offer, run them through one path, and the leads posted back tell you which page wins for which audience. Shift the weight in Binom and nothing on the pages has to change.

Use cases

Ways to use Binom on paid traffic

  • 01

    Debt relief on push traffic

    A two-step debt quiz on push, tracked in self-hosted Binom. Leads post back per zone, and the zones with clicks but no leads go on the blacklist the same day.

  • 02

    Solar quotes on native placements

    Two solar landing pages in one Binom path on native. Binom splits by device, the leads come back per landing page and per site, and the weight moves to the page that turns readers into quote requests.

  • 03

    A team sharing one Binom

    Several buyers run their own campaigns into LanderLab pages, all reporting to the team's Binom. Every lead lands on the buyer's campaign and the placement tokens behind it, so the reviews are about the same numbers.

FAQ

Binom integration FAQ

Anything not here, ask us.

Binom and LanderLab

Should I connect Binom to my landing pages?

Yes, if Binom is where you judge placements. Without leads posted back, its reports show clicks and cost per zone but not which zones produce leads.

Does it work with a self-hosted Binom?

Yes. The postback goes to your own Binom domain, so it works the same whether Binom runs on your server or on Binom's cloud.

Do I need Zapier to send leads to Binom?

No. The page's webhook calls your Binom postback URL directly when the visitor submits, with no third service holding your conversion data.

Will Binom see my UTMs and tokens?

Binom already has the tokens from the click. On the LanderLab side, Pass Through URL Params keeps them and the click ID on every link, and hidden fields save them with the lead.

Can I keep quiz answers with the lead?

Yes. Binom gets the conversion on its click, and every answer stays on the lead in LanderLab's Leads tab, next to the page and variant (CSV export on Grow and up).

Other integrations

Plug in the rest of your stack.

Connect Binom and launch your next page.

Build the page, switch Binom 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