1C-Bitrix Integration with CoMagic

Calls disappear into nowhere, and managers keep asking for data again? CoMagic is one of the few call tracking platforms that stores not just the call source but the complete visitor touch chain. But without linking to 1C-Bitrix, this data remains in the CoMagic interface and doesn't affect business processes. We set up the integration so that every targeted call automatically creates a lead in CRM, and the card shows the entire history of website interactions.

Our experience with CoMagic-Bitrix integrations spans over 30 projects. A typical result is reducing lead processing time by 40% and lowering cost per lead by up to 30% due to precise attribution. We guarantee transparency and stable operation of the solution.

What Problems Does Integration Solve?

• Loss of call attribution. Without visitor_id, the manager doesn't see which channel the client came from. CoMagic Data API attaches all session data to the lead.
• Manual data entry. Calls don't automatically enter CRM — you have to enter them manually, taking up to 5 minutes per lead. Webhook reduces this process to seconds.
• Duplicate leads. The same number may call multiple times. We implement deduplication: if a lead with that number already exists, we update it instead of creating a copy.

How Does CoMagic Transfer Calls to CRM?

CoMagic uses two mechanisms: webhook and Data API. Webhook sends a POST request to your server when a call ends, and Data API lets you request complete session information by visitor_id at any time. We implement both — for instant lead creation and subsequent enrichment.

Webhook: Verification and Processing

CoMagic signs each webhook with HMAC-SHA256. We verify the signature and discard calls shorter than 10 seconds — they are almost always spam or misdials.

// /local/api/comagic-webhook.php
require_once($_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_before.php');

$data = json_decode(file_get_contents('php://input'), true);

$signature = $_SERVER['HTTP_X_COMAGIC_SIGNATURE'] ?? '';
$secret    = \Bitrix\Main\Config\Option::get('local.comagic', 'webhook_secret');
$expected  = hash_hmac('sha256', file_get_contents('php://input'), $secret);

if (!hash_equals($expected, $signature)) {
    http_response_code(403);
    exit;
}

$event = $data['event_type'] ?? '';

if ($event === 'call_session_completed') {
    $processor = new \Local\CoMagic\CallProcessor();
    $processor->handle($data['call_session']);
}

http_response_code(200);

Call Processor: Creating a Lead

If the call is deemed targeted, we create a lead with UTM tags and CoMagic ID. If a lead with this number already exists, we update it to avoid duplicates.

namespace Local\CoMagic;

class CallProcessor
{
    public function handle(array $session): void
    {
        if (($session['is_lost_call'] ?? false) && ($session['duration_total'] ?? 0) < 10) {
            return;
        }

        $phone = $this->normalizePhone($session['visitor_phone_number'] ?? '');
        if (!$phone) {
            return;
        }

        $existingLeadId = $this->findRecentLead($phone);

        $fields = [
            'TITLE'           => 'CoMagic Call: ' . $phone,
            'PHONE'           => [['VALUE' => $phone, 'VALUE_TYPE' => 'WORK']],
            'SOURCE_ID'       => 'CALL',
            'STATUS_ID'       => 'NEW',
            'UF_COMAGIC_ID'   => (string)($session['id'] ?? ''),
            'UF_UTM_SOURCE'   => $session['utm_source'] ?? '',
            'UF_UTM_MEDIUM'   => $session['utm_medium'] ?? '',
            'UF_UTM_CAMPAIGN' => $session['utm_campaign'] ?? '',
            'UF_UTM_CONTENT'  => $session['utm_content'] ?? '',
            'UF_UTM_TERM'     => $session['utm_term'] ?? '',
            'COMMENTS'        => $this->buildComment($session),
        ];

        $lead = new \CCrmLead(false);

        if ($existingLeadId) {
            $lead->Update($existingLeadId, $fields, true);
        } else {
            $lead->Add($fields, true);
        }
    }

    private function buildComment(array $session): string
    {
        return implode("\n", [
            'CoMagic Session ID: ' . ($session['id'] ?? ''),
            'Operator: ' . ($session['employee_full_name'] ?? '—'),
            'Duration: ' . ($session['duration_total'] ?? 0) . ' sec.',
            'Traffic source: ' . ($session['traffic_type'] ?? '—'),
            'Entry page: ' . ($session['site_domain_url'] ?? '—'),
            'Tags: ' . implode(', ', $session['tags'] ?? []),
        ]);
    }
}

What Does visitor_id Provide?

CoMagic writes a comagic_visitor cookie on the website. When a lead goes through the chain, we request the full session via Data API on the server and populate custom fields: number of sessions, first and last source. This allows the manager to see which channel the client came from, even if the call wasn't the first touch.

class VisitorEnricher
{
    private ApiClient $api;

    public function enrichLead(int $leadId, string $visitorId): void
    {
        try {
            $result = $this->api->call('visitors.get_visitor_info', [
                'visitor_id' => $visitorId,
                'date_from'  => date('Y-m-d', strtotime('-1 day')),
                'date_till'  => date('Y-m-d'),
            ]);

            $visitor = $result['data'][0] ?? null;
            if (!$visitor) {
                return;
            }

            $updateFields = [
                'UF_CM_VISITOR_ID'     => $visitorId,
                'UF_CM_SESSION_COUNT'  => (int)($visitor['sessions_count'] ?? 0),
                'UF_CM_FIRST_SOURCE'   => $visitor['first_session']['utm_source'] ?? '',
                'UF_CM_LAST_SOURCE'    => $visitor['last_session']['utm_source'] ?? '',
            ];

            $lead = new \CCrmLead(false);
            $lead->Update($leadId, $updateFields, true);

        } catch (\RuntimeException $e) {
            \CEventLog::Add([
                'SEVERITY'      => 'WARNING',
                'AUDIT_TYPE_ID' => 'COMAGIC_ENRICH_FAIL',
                'MODULE_ID'     => 'local.comagic',
                'DESCRIPTION'   => $e->getMessage(),
            ]);
        }
    }
}

Click-to-Call: Calling Directly from CRM

CoMagic SIP allows outbound calls via API. We add a "Call" button to the lead and deal cards. After clicking, the operator receives a call on their SIP line, and CoMagic connects them to the client.

public function initiateCall(int $leadId, string $operatorLogin): array
{
    $lead   = \CCrmLead::GetByID($leadId);
    $phones = \CCrmFieldMulti::GetList(
        [],
        ['ENTITY_ID' => 'LEAD', 'ELEMENT_ID' => $leadId, 'TYPE_ID' => 'PHONE']
    );

    $phoneRow = $phones->Fetch();
    if (!$phoneRow) {
        return ['success' => false, 'error' => 'No phone'];
    }

    $result = $this->api->call('calls.make_call', [
        'virtual_phone_number' => \Bitrix\Main\Config\Option::get('local.comagic', 'virtual_number'),
        'operator_login'       => $operatorLogin,
        'destination_number'   => $phoneRow['VALUE'],
    ]);

    return ['success' => true, 'call_id' => $result['data']['call_session_id'] ?? null];
}

CoMagic vs. Other Call Tracking Systems

CoMagic stands out from competitors with data depth. For example, Callibri considers a visit as one touch, while CoMagic breaks it into points (pages, channels) — providing multi-touch attribution "out of the box." Additionally, CoMagic API allows flexible call management: initiating calls, changing scripts, getting call recordings. According to CoMagic, implementing end-to-end analytics with their platform increases conversion to sale by up to 30%.

Custom Fields We Create

What's Included in the Integration?

• local.comagic module: API client, event processors, logger.
• Webhook endpoint with HMAC signature verification.
• Creating/updating leads in CRM from calls and chats.
• JS form interception to pass visitor_id.
• Server-side enrichment with session data via Data API.
• Optional: click-to-call from CRM card and "CoMagic" dashboard.
• Documentation, admin training, 2 weeks of post-launch support.

Technical Implementation Details

CoMagic authentication uses JSON-RPC 2.0. The base ApiClient class is already tailored for Bitrix — it's in a separate namespace and uses \Bitrix\Main\Config\Option to store credentials. All external calls are logged in CEventLog.

namespace Local\CoMagic;

class ApiClient
{
    private string $baseUrl = 'https://dataapi.comagic.ru/v2.0';
    private ?string $accessToken = null;
    private string $login;
    private string $password;

    public function __construct(string $login, string $password)
    {
        $this->login    = $login;
        $this->password = $password;
    }

    public function call(string $method, array $params = []): array
    {
        if (!$this->accessToken) {
            $this->authenticate();
        }

        $payload = [
            'jsonrpc' => '2.0',
            'id'      => uniqid('cm_', true),
            'method'  => $method,
            'params'  => array_merge(['access_token' => $this->accessToken], $params),
        ];

        $ch = curl_init($this->baseUrl);
        curl_setopt_array($ch, [
            CURLOPT_POST           => true,
            CURLOPT_POSTFIELDS     => json_encode($payload),
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_HTTPHEADER     => ['Content-Type: application/json'],
            CURLOPT_TIMEOUT        => 10,
        ]);

        $response = json_decode(curl_exec($ch), true);
        curl_close($ch);

        if (isset($response['error'])) {
            throw new \RuntimeException('CoMagic API error: ' . $response['error']['message']);
        }

        return $response['result'] ?? [];
    }

    private function authenticate(): void
    {
        $payload = [
            'jsonrpc' => '2.0',
            'id'      => 'auth',
            'method'  => 'login.user',
            'params'  => ['login' => $this->login, 'password' => $this->password],
        ];

        $ch = curl_init($this->baseUrl);
        curl_setopt_array($ch, [
            CURLOPT_POST           => true,
            CURLOPT_POSTFIELDS     => json_encode($payload),
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_HTTPHEADER     => ['Content-Type: application/json'],
        ]);

        $result = json_decode(curl_exec($ch), true);
        curl_close($ch);

        $this->accessToken = $result['result']['data']['access_token']
            ?? throw new \RuntimeException('CoMagic auth failed');
    }
}

Timeline and Pricing

Basic integration (webhook → lead + UTM) — 1–2 weeks. Full stitching with multi-touch attribution, click-to-call, and data showcase — 4–6 weeks. Pricing is calculated individually after auditing your CRM and traffic volumes. Contact us for an audit and project estimate within one business day.

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.