Bitrix24 integration

Every lead your ads bring in arrives in Bitrix24 as a CRM lead, with the UTMs already in Bitrix24's own UTM fields, through the inbound webhook your portal already has. Nothing to install.

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

Why connect it

Why Bitrix24 and LanderLab

  • UTMs in fields Bitrix24 already has

    Bitrix24 leads come with UTM source, medium, campaign, content and term fields. Hidden fields fill them from the ad's URL, so reports split by campaign out of the box.

  • Leads where the phone is

    Bitrix24 has telephony built in. A lead created on submit can be called from the CRM within minutes, with the answers on screen.

  • Source set to Website, every time

    Page leads arrive with their source and the landing page recorded, so they never mix with walk-ins or imports.

  • Nothing to install or pay for

    The inbound webhook is part of your portal. LanderLab posts to it directly, with no Zapier plan or third-party app.

  • The responsible person hears about it

    Bitrix24 can log the new lead as an event and notify the person responsible, so a fresh lead doesn't sit unseen.

Bitrix24 on your landing pages

Bitrix24 already has everything a sales team needs to work a lead, including the phone. What it doesn't have is your landing pages. Sending your LanderLab leads to Bitrix24 closes that gap: every portal can issue an inbound webhook, and LanderLab's webhook uses it to add a CRM lead on every submit, with no marketplace app or connector in between.

It suits teams that already sell from Bitrix24: movers and relocation firms booking surveys by phone, clinics and schools taking inquiries in several countries, service businesses whose reps call from Bitrix24's own telephony. The lead lands where the call button is, with the campaign it came from in fields Bitrix24 reports on.

Bitrix24 CRM leads from one inbound webhook

An inbound webhook in Bitrix24 is a private URL that accepts REST calls with the permissions of the user who created it. LanderLab's webhook calls its lead method on every submit, with the name, phone, email and answers as Bitrix24 expects them. Bitrix24 answers with the new lead's ID, and the lead is in your CRM.

There's no marketplace app to approve and nothing for your Bitrix24 admin to install: the inbound webhook is part of the portal you already pay for.

UTMs in Bitrix24's own UTM fields

Most CRMs make you invent attribution fields. Bitrix24 leads have UTM source, medium, campaign, content and term built in. Add hidden fields with the same names to your page, map them across, and your reps don't see a wall of parameters while your reports can split leads, and later deals, by campaign.

For anything Bitrix24 has no field for, like the A/B variant or the click ID, a custom lead field does the job.

Classic mode, simple mode and where the lead lands

Bitrix24's CRM runs in one of two modes. In classic mode each submit creates a lead for a rep to qualify and convert. In simple mode there are no leads: Bitrix24 turns each one into a deal straight away. Both work with your pages; it's worth knowing which one your portal uses so you know whether to look in Leads or in Deals.

Only the leads worth a call

If the sales team should only get qualified leads, put the rule in LanderLab Workflows (beta): a Filter on the quiz answer that matters, then an HTTP Request node that makes the same call to Bitrix24. The rest stay in LanderLab's Leads tab, filterable by date and variant.

Use cases

Ways to use Bitrix24 on paid traffic

  • 01

    Moving and relocation quotes

    A long-distance moving page on Google Ads sends move date and home size into the lead. The sales rep calls from Bitrix24's telephony with the details on screen, and books the survey on the first call.

  • 02

    The same offer in several geos

    Run one page per country and point each at the regional team's portal, or at one portal with the country in a custom field. The UTM fields keep the campaigns apart in Bitrix24's reports.

  • 03

    Clinics and schools taking inquiries

    A consultation or course inquiry page on Meta creates a lead with the service or program chosen. The admissions or front desk team works it in Bitrix24 next to their chats and tasks.

FAQ

Bitrix24 integration FAQ

Anything not here, ask us.

Bitrix24 and LanderLab

When is Bitrix24 worth connecting to my landing pages?

When your team sells from Bitrix24: leads arrive on submit with UTMs in Bitrix24's built-in fields, ready to call from the same screen.

Does LanderLab integrate with Bitrix24?

Yes, through the page's Webhook integration: it sends each lead to the inbound webhook your portal already provides, so there's no marketplace app to install.

Do I need Zapier to send leads to Bitrix24?

No. The page posts the lead to your portal's webhook directly, so there's no middle step to pay for or maintain.

Will Bitrix24 see my UTMs?

Yes. Hidden fields capture them from the ad's URL and they go into the UTM fields every Bitrix24 lead already has.

Why would a lead show up as a deal?

Your CRM is in simple mode, which has no leads. Bitrix24 converts each new lead into a deal as it arrives.

Which Bitrix24 plans work?

Inbound webhooks use Bitrix24's REST API, which isn't on every plan. Check that yours includes REST access; the trial does.

Other integrations

Plug in the rest of your stack.

Connect Bitrix24 and launch your next page.

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