Bitrix24 Conversion Leads

Connect Bitrix24 CRM to Meta Conversion Leads through SignalSight — enter your CRM URL, authenticate, map lead fields, and stream funnel events back to Meta.

In This Page

SignalSight Conversion Lead streams lead-stage updates from Bitrix24 CRM to Meta in real time. When a lead moves through your pipeline — unassigned, in progress, meeting, or processed — those events flow back to Meta so campaigns optimize toward meaningful outcomes instead of raw form submissions.

Before you start

You need a SignalSight account and a Meta CRM Pixel set up in Events Manager. For Pixel ID and access token steps, see Meta (Facebook) CAPI Setup. New users can start with Account Creation.

Get Started

Use your Bitrix24 lead records in SignalSight's Conversion Lead solution to target the right audience and improve ROI. Your Bitrix24 panel should have active leads moving through pipeline stages before you begin setup.

Bitrix24 CRM leads dashboard in Kanban view

Open the Tracker Creation Wizard under Signal in the left menu and follow the steps below.

Create a Tracker

Step 1 — Bitrix24 Source

  1. Select Bitrix24 from the source list and give the source a name.
  2. Enter your Bitrix24 URL from your panel (e.g. https://your-company.bitrix24.com).
  3. Click Connect with Bitrix24 and sign in to grant the required permissions.
Bitrix24 source creation — CRM URL and Connect with Bitrix24 button

On the mapping screen, configure the Event Name Prefix and field mappings. With CRMLeads as the prefix, a Qualified stage becomes CRMLeads-Qualified and a Junk stage becomes CRMLeads-Junk. You can leave the prefix blank or enter a custom value.

Bitrix24 CRM field mapping — Leadgen ID, Lead Status, and Date

Map Leadgen ID, Lead Status, and Date to the corresponding Bitrix24 fields. Correct Leadgen ID mapping is required for Conversion Leads — this is the Meta lead identifier used to match CRM events back to Facebook-generated leads.

Click Save and Next to continue to destination setup.

Step 2 — Meta CAPI Destination

Create a Meta Conversions API destination. Enter your CRM Pixel ID and access token manually, or use Connect Facebook CAPI to sign in and select the Pixel from your account.

Meta Conversions API destination setup with Connect Facebook CAPI option

Note

The Pixel must be a CRM Pixel — not your website Pixel. In Events Manager, click Connect Data Sources, select CRM, then Connect. Create a new dedicated Pixel (recommended) so CRM events stay separate from your web Pixel.

Step 3 — Name and Complete

Name your tracker, review the selected source and destination summary, and click Complete to finish the wizard.

Tracker creation summary — Bitrix24 source and Meta destinations

Manage Your Source

Open your tracker at any time to update field mapping or review sent event history. Use Edit Mapping on the Bitrix24 source to adjust field mappings and the event name prefix that precedes your event names.

What Happens Next

Once CRM events start flowing, complete the funnel setup in Meta Events Manager. The three guides below cover everything after tracker creation:

Frequently Asked Questions

Where do I find my Bitrix24 URL?

Your Bitrix24 URL is the address you use to log in to your Bitrix24 panel — typically in the format https://your-company.bitrix24.com or https://your-company.bitrix24.com.tr for regional instances. Copy it from your browser's address bar.

What is the Event Name Prefix?

It prepends a label to every event sent to Meta. With the CRMLeads prefix, a Qualified stage becomes CRMLeads-Qualified. You can customize or clear the prefix during source setup or later via Edit Mapping.

Can I use my website Pixel for Conversion Leads?

No. You need a dedicated CRM Pixel configured in Events Manager. Using a web Pixel will cause validation errors.