BeMob integration

BeMob tracks your push, pop and native campaigns in the cloud, but a lead filled on your landing page is invisible until someone reports it. LanderLab posts each lead back with BeMob's click ID, the moment the form is sent.

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

Why connect it

Why BeMob and LanderLab

  • No tracker server to run

    BeMob is cloud-hosted and LanderLab hosts your pages, so the whole funnel runs without a VPS, updates or uptime checks.

  • Leads on the right path and landing page

    Each lead is posted back with BeMob's click ID, so weights between landing pages and offers can be set on leads rather than click-through rate.

  • Approved and declined, counted apart

    BeMob's conversion statuses separate new, approved, declined and chargeback, so a lead your buyer rejects doesn't keep a placement looking good.

  • Costs from your traffic sources

    BeMob pulls cost from integrated sources like PropellerAds, MGID and Revcontent, so cost per lead appears next to the leads without a manual import.

  • Custom conversions for each stage

    BeMob's custom conversions track up to 20 event types, so a lead and a later sale or approval each get their own column.

BeMob on your landing pages

BeMob gives you a tracker without a server to babysit: campaigns, paths with weighted landing pages and offers, cost pulled from the traffic sources it's connected to. What it needs from you is the conversion. When the lead form is on a LanderLab page, LanderLab supplies it: the visit arrives with BeMob's click ID on the URL, a hidden field keeps it, and on submit the page's Webhook integration sends it to BeMob's postback URL, so the lead lands on the path, landing page and offer that produced it.

It's a fit for buyers starting out on push and native, and for teams that want lead gen tracking without hosting anything. LanderLab hosts the pages, BeMob hosts the tracking, and the postback connects the two.

BeMob postbacks from the form, not the thank-you page

A thank-you page pixel depends on the visitor's browser loading it. A postback doesn't. When the form on your LanderLab page is sent, LanderLab posts the conversion straight to BeMob with the click ID from the visit, so the lead is counted even when the visitor closes the tab right after the submit.

For lead gen on push and pop, where visitors bounce fast and browsers block a lot, that's the difference between the leads you got and the leads your tracker heard about.

Landing page weights set on leads

BeMob paths take several landing pages and offers, each with a weight. Put two or three LanderLab variants of the same lead page in one path, let the leads come back, and move the weight to the page with the better cost per lead. BeMob's Smart Rotations can keep a returning visitor on the same path or landing page, so repeat visitors don't muddy the test.

Statuses that match how lead buyers pay

Most lead buyers don't pay for every lead. BeMob lets a postback carry a status, mapped to new, approved, declined or chargeback, and records each status for a click as its own conversion. Your form posts the lead as new, the buyer's postback marks it approved or declined, and BeMob's reports show which sources send leads that get paid.

Pre-landers that keep the click

When a LanderLab page is a pre-lander rather than a lead page, Pass Through URL Params forwards BeMob's click ID and your tokens to every link, including BeMob's own click URLs to the offer. The network's postback then finds its way back to the right campaign.

Use cases

Ways to use BeMob on paid traffic

  • 01

    Auto insurance on push

    A short quote form on PropellerAds push, tracked in BeMob with costs pulled from the source. Leads post back per zone, and zones with spend but no leads come off the campaign.

  • 02

    Solar quotes on MGID native

    Two solar landing pages split 50/50 in one BeMob path. The leads that come back settle the split, and the losing page's weight drops to zero.

  • 03

    Debt relief leads sold per approval

    Leads arrive as new in BeMob, and the buyer's postback approves or declines each one. Sources whose leads get declined show up in the declined column, not in your profit.

FAQ

BeMob integration FAQ

Anything not here, ask us.

BeMob and LanderLab

Is BeMob worth connecting to my landing pages?

If BeMob tracks your campaigns, yes. Without the postback it sees clicks and costs, but not the leads your pages produce.

Do I need a server for BeMob or for my pages?

No. BeMob is cloud-hosted and LanderLab hosts your pages, so there's nothing to install.

Do I need Zapier to send leads to BeMob?

No. Each submit goes from the page's webhook straight to BeMob's postback URL, so a BeMob account and LanderLab are all the stack needs.

Will BeMob see my click ID and tokens?

Yes. BeMob's click ID arrives on the page URL and goes back with the conversion, and Pass Through URL Params keeps it on every link out of the page.

Can I keep quiz answers with the lead?

Yes. BeMob receives the conversion; the answers stay on the lead in LanderLab, ready to go on to a CRM or buyer, or out as a CSV on Grow and up.

Other integrations

Plug in the rest of your stack.

Connect BeMob and launch your next page.

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