Integrate 1C-Bitrix with Calltouch for Full Call Tracking

Integrate 1C-Bitrix with Calltouch: Full End-to-End Call Analytics

Losing call attribution is a chronic pain for businesses where most conversions happen over the phone (auto, real estate, healthcare, B2B). Without end-to-end analytics, you can't see which channel brought the call, and reallocating your ad budget becomes guesswork. Integrating 1C-Bitrix with Calltouch solves this: every call is automatically tied to a source and passed to the CRM as a lead. Our team has 10+ years of experience with Bitrix and Calltouch, ensuring stable attribution even under peak loads of up to 1000 calls/sec. Ad budget savings reach 30%, and the average order value after integration is 5,000 RUB.

Calltouch is an end-to-end analytics platform focused on call tracking: dynamic number substitution, call recording, and call-to-ad-campaign attribution. The system handles up to 1000 calls per second—three times faster than manual entry. It saves sales teams up to 30 hours per month and achieves 98% attribution accuracy versus 60% with manual methods. According to Calltouch, companies typically reduce spending on non-targeted channels by 30% after integration.

How Calltouch Tracking Works

A JavaScript counter is placed on the website. On each visit, the script performs three steps:

1. Determines the visit source (UTM tags, referrer, direct entry).
2. Replaces the website phone number with a unique tracking number from the pool.
3. Records the call on that number with attribution to the source.

Concurrently, the session ID is saved in the ct_session_id cookie. When web forms are submitted, this value must be captured and passed to the CRM to link the request to the ad source. Without it, the call remains an "orphan"—you have the number but no channel.

How to Capture sessionId in Bitrix Forms

For forms on 1C-Bitrix (web 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 or order is processed, save the value in b_uts_user or the custom order field UF_CALLTOUCH_SID. This method works with any form—contact forms, callback requests, carts.

On one project (a construction materials online store), we found that 40% of calls came to a number in a static block that was not tracked. After installing the Calltouch script and passing sessionId through the order form, the client saw that 70% of leads came from contextual advertising, not SEO. This allowed them to reallocate the budget and increase ROI by 25%.

Why It's Important to Update Request Status in Calltouch

A request may become a deal or be rejected. We transmit the update via PATCH /requests/orders/{requestId}/update/ with the new status and amount. This builds the funnel in Calltouch: request → deal → revenue. Without it, the final conversion won't appear in reports, and ROI will be incorrectly calculated. From project experience, 20-30% of requests are rejected during qualification—their status is critical for analytics.

Calltouch API: Passing Conversion Data

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

Order confirmation. The user filled out a form—this is a conversion. We send the data:

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

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

Integration with Bitrix24 CRM

For Bitrix24, the scenario is more complex: a call via Calltouch should enter the CRM as a lead or activity. Calltouch supports passing calls via the official connector (available in the Bitrix24 marketplace) or via REST API.

An alternative route: a webhook from Calltouch when a call ends → creating a lead in Bitrix24 via crm.lead.add. In the lead we pass: caller number, ad source from Calltouch, call duration, and a link to the recording.

// 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 allows importing offline conversions via the API—for example, when a deal is closed through a meeting. From Bitrix24, when a deal status changes to "Won," we send conversion data to Calltouch with the sessionId linked to that lead. Method: POST /calls-service/RestAPI/{siteId}/requests/orders/register/ with parameter isOffline: true. This gives you a complete picture—from click to actual revenue.

How to Set Up Calltouch Integration with Bitrix

1. Install the Calltouch counter on all site pages.
2. Configure sessionId capture in forms (see code above).
3. Create a webhook in Calltouch for passing conversions.
4. Verify attribution in reports.

We complete the full cycle in a few days. Order the integration and get transparent attribution within a week.

What's Included

We provide a warranty on all work and support for 30 days after launch. Contact us for a project estimate—get a consultation and an exact cost calculation within one working day. Your ad budget will stop working blindly.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.