1C-Bitrix Integration with End-to-End Analytics Services

1C-Bitrix Integration with End-to-End Analytics Services

Your ad budget is spent, but marketers don't see which channels drive actual sales. Yandex.Metrica shows site conversions, CRM stores deals, 1C records payments — data is fragmented, and connecting them into a unified picture fails. We configure end-to-end analytics on Bitrix to close the loop: ad click → lead → deal → payment. Without this, you don't see real ROI and can't optimize ad spending. Our team handles the integration turnkey — from tracker installation to data transfer from 1C to the dashboard. We'll assess your project in one day, just contact us.

How to Transfer Visit ID from Tracker to Bitrix Order

End-to-end analytics relies on user identification at all funnel stages. The key element is the visit ID assigned by the tracker (e.g., roistat_visit). This ID must end up in the Bitrix order, otherwise offline conversions can't be attributed to ads. Two working options:

• Order property. Create a string property with code ROISTAT_VISIT. On the frontend, a JS script reads the cookie and injects the value into a hidden form field. On the backend, an OnSaleOrderBeforeSaved handler duplicates the value into the property.
• UTM properties. Bitrix can save UTM labels via the sale module. The visit ID is passed as an additional UTM tag.

The first option is more reliable — data isn't lost when templates change. We use it in all projects.

Integration with Bitrix24 CRM

If CRM is Bitrix24, lead and deal data are transferred via REST API. Analytics services (Roistat, Calltouch) have ready-made connectors: in settings you specify the portal URL and token. The service pulls leads/deals via crm.lead.list / crm.deal.list, matches by phone or email, and retrieves statuses for stage-based conversion calculations. For on-premise Bitrix (not B24), ready-made integrations don't exist — we write a custom handler that sends data to the service API.

Why Are Offline Conversions from 1C Lost?

Payment in 1C is the final funnel point. If payment data doesn't return to the analytics service, ROI is calculated incorrectly. Typical loss scenario: Bitrix order contains the visit ID, but during exchange with 1C via CommerceML this ID isn't transferred, so no feedback after payment. Solution: add the visit ID as a document attribute in CommerceML or REST mapping, and on payment completion send a POST request to the service API. For Roistat it's POST https://cloud.roistat.com/api/v1/project/add-orders, for Calltouch — POST /api/calls-service/RestAPI/orders/upload. An alternative is an intermediate webhook on the OnSalePayOrder event, which requests payment status from 1C and sends it to analytics.

Comparison of End-to-End Analytics Services for Bitrix

All services support call tracking and offline conversion transfer, but configuration on Bitrix has nuances, especially with composite cache.

What's Included in the Work

• Audit of current setup: check what data is collected, where it's lost, which systems are involved.
• Tracker installation and configuration of visit ID transfer to order (order property or UTM).
• CRM integration: configure ready-made connector for Bitrix24 or develop custom handler for on-premise version.
• Configuration of offline conversion transfer from 1C via CommerceML, REST API, or webhook.
• End-to-end testing from ad click to payment reflection in dashboard.
• Documentation and training: scheme description, instructions for marketers, access handover.
• Initial support: bug fixes, fine-tuning for one month.

Timeline

Cost is calculated individually based on audit results. Contact us — we'll assess your project for free and offer the best solution.