Keitaro integration

Keitaro's flows split traffic between landing pages and filter it by country and device. LanderLab posts each lead back with Keitaro's subid, so you know which landing page wins for which audience, not just which one gets clicks.

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

Why connect it

Why Keitaro and LanderLab

  • Flows judged on leads

    Each lead comes back with Keitaro's subid, so every flow, filter and landing page split in a campaign shows its own leads next to its clicks and costs.

  • Revenue on hold the moment they submit

    A form fill posted as a lead shows up as revenue on hold in Keitaro straight away, before the buyer or network confirms it as a sale.

  • Rejected leads leave the numbers

    When the buyer rejects a lead, a rejected status cancels its payout in Keitaro, so the flow that sent junk doesn't keep looking profitable.

  • Resells counted apart

    Keitaro records a separate conversion when the transaction ID is new, so a lead sold twice, or a lead and its upsell, don't overwrite each other.

  • Conversion data on your own server

    Keitaro runs on your server, and the conversions LanderLab posts to it are stored there, with your offers and margins.

Keitaro on your landing pages

Keitaro routes each click through a campaign and its flows, then sends it to a landing page. When that landing page is a LanderLab page, the subid comes along on the URL, and the page hands it back when the visitor converts: a hidden field saves the subid, and on submit the page's Webhook integration sends it to the postback URL of the Keitaro on your server, attached to the right campaign and flow.

Keitaro reads statuses as money. A lead is revenue on hold, a sale is confirmed, rejected is canceled. Posting leads from the page fills the hold column the moment the form is sent, and the buyer's or the network's postback moves each one along later. You stop guessing which flows produce leads that get paid.

Keitaro postbacks with the subid

Keitaro sends the visitor to your LanderLab page with its click ID, the subid, on the URL. Pass Through URL Params keeps the subid on every link, and when the form is sent, the conversion is posted back to the Keitaro on your server with that subid, so it lands on the right campaign and flow.

Split test pages inside a Keitaro flow

A Keitaro flow can hold several landing pages and split traffic between them by percentage. Put two LanderLab pages in one flow, add country or device filters to send each audience to its own flow, and the leads posted back show which page converts for each audience.

Move the traffic share to the winner in the flow, with nothing to change on the pages. Keitaro's weight-based rotation between flows works the same way one level up, so you can test a whole approach (a quiz against a long-form page) as well as two headlines.

Lead, sale and rejected, in Keitaro's terms

Keitaro has its conversion statuses built in: lead for revenue on hold, sale for confirmed, rejected for canceled, plus registration, deposit and trash. The form fill from your LanderLab page arrives as a lead. When the network or buyer reports back, the same subid moves to sale or rejected, and Keitaro's revenue columns tell you what each flow really earned.

For lead gen buyers who get paid per accepted lead, that's the report that matters: a flow with a great conversion rate and a high rejection rate is a flow to fix, and Keitaro shows it without a spreadsheet.

Click data that stays useful after the click

Keitaro can update a click's sub ID fields from a postback, which lets a lead's context become a report column: the state, the debt band, the coverage type. LanderLab keeps every answer on the lead in its Leads tab too, filterable by date and variant, so a question about lead quality can be answered from either side.

Use cases

Ways to use Keitaro on paid traffic

  • 01

    HVAC replacement in two countries

    One Keitaro campaign, a US flow and a Canada flow, each with two LanderLab quizzes split 50/50. Leads post back per flow, and the share moves to the quiz that wins in each country.

  • 02

    Debt relief sold per accepted lead

    Leads arrive in Keitaro as revenue on hold, and the buyer's postback turns them into sales or rejections. Flows that send leads the buyer returns show up in the rejected column within a day.

  • 03

    A quiz against a long-form page

    Two flows weighted 50/50 on Facebook traffic: a five-step solar quiz and a long-form article with a form. The posted leads settle which approach to scale before you spend on new creatives.

FAQ

Keitaro integration FAQ

Anything not here, ask us.

Keitaro and LanderLab

Is Keitaro worth connecting to my landing pages?

If Keitaro runs your campaigns, yes. Its flows, filters and splits are only as good as the conversions behind them, and the postback from the form supplies them.

Does it work with Keitaro on my own server?

Yes. The postback goes to your Keitaro's own domain, so it works wherever your Keitaro is hosted: your own server or one from Keitaro's hosting partners.

Do I need Zapier to send leads to Keitaro?

No. The page's webhook calls your Keitaro's postback URL on every submit, so the conversion never passes through a third service on its way to your server.

Will Keitaro see my click ID and UTMs?

Yes. The subid comes in on the page URL and returns to Keitaro with the lead. Hidden fields can save your UTMs on the lead, and Pass Through URL Params forwards both to the next page.

Can I split test LanderLab pages in Keitaro?

Yes. Put the pages in one flow and split by percentage, or give each audience its own flow with filters. The leads posted back show the winner for each.

Other integrations

Plug in the rest of your stack.

Connect Keitaro and launch your next page.

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