CONNECTIONS / Bitrix24
Bitrix24 + Datahash: get funnel activity to ad platforms.
Bitrix24 runs leads, deals, and multiple sales funnels inside one workspace, while ad platforms optimize on the original form fill. Signals reads deal and lead activity across your funnels and syncs the stages that matter back to Meta, Google, TikTok, and Snap.
- ● bitrix24 :: signals live
- > read deals funnel=sales stage=won rows=5,530
- > read leads status=converted
- hash sha256(email,phone) scope=crm.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 80%
The signal Bitrix24 yields, and receives.
Every kind of signal that moves between Bitrix24 and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A deal moving into a won stage in any of your Bitrix24 funnels posts as a conversion event, so campaigns learn from pipeline outcomes instead of the opening click alone.
- Lead conversions
- A lead converting to a deal reaches the ad platform as a signal without waiting on a manual export from the CRM.
- Custom audiences
- Customer lists leave Bitrix24 hashed and become scheduled audiences that stay current as the underlying list changes.
- Lead generation inbound
- Click IDs stored on the lead or deal record travel with the event, so a closed deal ties back to the exact click that started it.
Pick your platform. Every use case for it, in one place.
Every way Bitrix24 data moves, grouped by platform and ranked by how many use cases Bitrix24 supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Authorize
Scoped Bitrix24 REST app auth, reversible any time.
-
Map funnels
Stage-to-event mapping per funnel in the visual mapper.
-
Hash and consent
Hashing and consent applied at sync.
-
Deliver
Delivery with per-stage match reporting.
Bitrix24 questions, answered.
Do you support Bitrix24 accounts with multiple sales funnels?
Yes. Bitrix24 lets a business run several funnels for different products or teams, and the mapper handles each one separately, so a stage called "won" in one funnel and a differently named final stage in another can both map to the same conversion event, or to different ones if that fits your setup.
How fast do Bitrix24 stage changes deliver?
Delivery is near real time where Bitrix24's webhooks cover the object being read, and scheduled on a set cadence where they do not. A stage change is read, hashed, and routed to each connected platform on that cadence, with per-destination match feedback in the debugger so you can confirm delivery.
Can we run Bitrix24 alongside another CRM during a migration?
Yes. Signals can read Bitrix24 and a second CRM at the same time and deduplicate matching records on external ID, so a migration in progress does not double-count conversions or split an audience across two sources. Once the migration finishes, you remove the old connection on your own timeline.
NEXT STEP
See your Bitrix24 data working in every ad platform.
Ready to enable a use case, or still mapping what Bitrix24 data could do? Our team helps you find the right place to start.
