Integration of 1C-Bitrix with Calltouch

1C-Bitrix Integration with Calltouch

Calltouch is an end-to-end analytics platform with a focus on call tracking: phone number substitution, call recording, and attribution of calls to advertising sources. For businesses where a significant share of conversions happens over the phone (automotive, real estate, healthcare, B2B), integrating Calltouch with 1C-Bitrix links the call to a subsequent order or deal.

How Calltouch Tracking Works

A Calltouch JavaScript counter is installed on the site. On each visit, the script:

1. Identifies the traffic source (UTM, referrer, direct visit)
2. Replaces the phone number on the site with a unique tracking number from the pool
3. When the user calls that number — records the call attributed to the source

In parallel, the script stores a session identifier in the ct_session_id cookie. When web forms are submitted, this value must be captured and passed to the CRM to link the lead to its advertising source.

Form and Order Integration

For forms on 1C-Bitrix (forms from the form module or custom forms), add a hidden field calltouch_session_id:

var ctSid = getCookie('ct_session_id') || localStorage.getItem('CALLTOUCH_SID');
if (ctSid) {
    document.querySelector('[name="calltouch_session_id"]').value = ctSid;
}

When the form is processed or the order is placed, save the value to b_uts_user or a custom order field UF_CALLTOUCH_SID.

Calltouch API: Passing Conversion Data

The Calltouch API allows passing conversion data from the site and linking it to sessions. This is needed for two scenarios:

Confirming a lead. A user submitted a form — that is a conversion. Send lead data to Calltouch:

POST https://api.calltouch.ru/calls-service/RestAPI/{siteId}/requests/orders/register/
{
  "sessionId": "ct_session_id_value",
  "requestNumber": "ORDER_123",
  "requestDate": "13/03/2026 10:00:00",
  "subject": "New order",
  "callbackPhone": "+79001234567",
  "value": 4990
}

The sessionId field is the cookie value. Calltouch uses it to find the corresponding visit and attribute the conversion to an advertising source.

Updating lead status. A lead may become a deal or be rejected. Send an update via PATCH /requests/orders/{requestId}/update/ with the new status and amount. This builds a funnel in Calltouch: lead → deal → revenue.

Integration with Bitrix24 CRM

For Bitrix24, the scenario is more involved: a Calltouch call must reach the CRM as a lead or call record. Calltouch supports sending calls to Bitrix24 via an official connector (available in the Bitrix24 marketplace) or via REST API.

An alternative approach: a webhook from Calltouch on call completion → create a lead in Bitrix24 via crm.lead.add. Pass to the lead: caller's phone number, advertising source from Calltouch, call duration, and recording link.

// Calltouch webhook handler
$calltouchData = json_decode(file_get_contents('php://input'), true);
$leadData = [
    'TITLE' => 'Call ' . $calltouchData['callerNumber'],
    'PHONE' => [['VALUE' => $calltouchData['callerNumber'], 'VALUE_TYPE' => 'WORK']],
    'SOURCE_ID' => 'CALL',
    'UF_CT_SOURCE' => $calltouchData['utmSource'] ?? '',
    'UF_CT_CALL_ID' => $calltouchData['callId'],
];
// Create lead via crm.lead.add

Offline Conversion Attribution

Calltouch supports importing offline conversions via API — for example, when a deal is closed through an in-person meeting. In this case, when a deal in Bitrix24 moves to "Won" status, send conversion data to Calltouch with the sessionId tied to that lead. Method: POST /calls-service/RestAPI/{siteId}/requests/orders/register/ with the parameter isOffline: true.

Estimated Timelines

Pricing is calculated individually after analyzing the current lead generation flow and Calltouch configuration.