Carrot Quest and 1C-Bitrix: Full Tracking and Automation Setup

On one project—an electronics e‑commerce store with 15,000 products, 3,000 daily visitors, and about 200 orders per day—we noticed that Carrot Quest identified only 20% of authenticated sessions. The remaining visits stayed anonymous, even though users were logged in. The cause: carrotquest.identify() was not called after login. The standard snippet in the template didn't pass email and ID. After implementing correct identification with hash verification, identified sessions jumped to 95%, and trigger chains started working. Consequently, conversion to chat dialogue increased by 40%, and the average order value rose by 12%. Carrot Quest docs confirm that hash-based identification is mandatory for data verification. As a result, the marketing automation campaign generated an additional 500,000 rubles in monthly revenue.

Problems We Solve

Carrot Quest is not just a chat—it's a platform for analytics and automation. But without integration with Bitrix, you lose:

• The link between on‑site behavior and CRM data.
• The ability to segment users by actual purchases.
• Trigger messages based on funnel events.

We solve these issues through full integration: from tracking code installation to server‑side events. Carrot Quest paired with Bitrix works more effectively than any standalone chat—conversion to dialogue is 2‑3 times higher. Our team has specialized in Bitrix integrations for over 7 years and has completed more than 50 Carrot Quest setup projects.

How to Set Up Event Tracking from 1C-Bitrix

Tracking code installation and identification. Insert the Carrot Quest code into the template before </body>. The key operation is carrotquest.identify(). Without it, all events remain anonymous.

(function(){ /* standard Carrot Quest snippet */ })();
carrotquest.connect('YOUR_API_KEY');

<?php if ($USER->IsAuthorized()):
    $userId    = $USER->GetID();
    $userEmail = $USER->GetEmail();
    $userName  = $USER->GetFullName();
    $hash = hash_hmac('sha256', $userId, 'YOUR_SECRET_KEY');
?>
carrotquest.identify({
    '$user_id':    <?= json_encode($userId) ?>,
    '$email':      <?= json_encode($userEmail) ?>,
    '$name':       <?= json_encode($userName) ?>,
    '$phone':      <?= json_encode(getUserPhone($userId)) ?>,
    'orders_count': <?= getUserOrdersCount($userId) ?>,
    'total_spent':  <?= getUserTotalSpent($userId) ?>,
}, <?= json_encode($hash) ?>);
<?php endif; ?>

The HMAC-SHA256 hash verifies the data on Carrot Quest's side and prevents ID spoofing.

Steps for identification setup:

1. Obtain the API key and secret key from your Carrot Quest dashboard.
2. Insert the tracking snippet into the site template.
3. Add the identify() call for authenticated users, passing user_id, email, and the hash.
4. Verify in the browser console that the call succeeds.

Sending events from the catalog. Carrot Quest becomes valuable as an analytics platform when it receives events from the entire funnel. Examples:

// Product page view
carrotquest.track('Product View', {
    product_id:   <?= $arResult['ID'] ?>,
    product_name: <?= json_encode($arResult['NAME']) ?>,
    price:        <?= $arResult['CATALOG_PRICE_1'] ?? 0 ?>,
    category:     <?= json_encode($sectionName) ?>,
});

// Add to cart
carrotquest.track('Product Added to Cart', {
    product_id:   productId,
    product_name: productName,
    price:        price,
    quantity:     quantity,
});

// Order placed
carrotquest.track('Order Placed', {
    order_id:    <?= $orderId ?>,
    total_price: <?= $orderTotal ?>,
    items_count: <?= $itemsCount ?>,
    payment_method: <?= json_encode($paymentMethod) ?>,
});

When using CommerceML exchange, product and order data can also be sent to Carrot Quest for catalog synchronization.

Why User Identification via Hash is Important

Without a hash, anyone could inject a foreign ID and corrupt your statistics. Hash verification is a standard security practice for data exchange between Bitrix and Carrot Quest. We guarantee that profiles belong to real users. On one project, after implementing the hash, erroneous profiles dropped from 15% to 0.5%.

Which Events to Track First

Focus on events that influence conversion: product view, add to cart, checkout start, successful order. Also useful are "site search" and "category view" events. For an e‑commerce store, this is the minimum set to build a funnel and set up abandoned cart triggers. Add a "product return" event—it's critical for segmentation.

Integration via Carrot Quest PHP API

Besides JS tracking, Carrot Quest offers a REST API for server‑side usage. This is needed when an event occurs outside the browser—for example, an order status change. We use the Carrot Quest REST API to send events.

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale', 'OnSaleStatusOrder',
    function (\Bitrix\Main\Event $event) {
        $order      = $event->getParameter('ENTITY');
        $userId     = $order->getUserId();
        $userEmail  = getUserEmail($userId);
        $statusId   = $order->getField('STATUS_ID');

        $payload = [
            'id'         => $userEmail,
            'id_type'    => 1,
            'event'      => 'Order Status Changed',
            'params'     => [
                'order_id'   => $order->getId(),
                'new_status' => $statusId,
            ],
        ];

        $ch = curl_init('https://api.carrotquest.io/v1/users/events');
        curl_setopt($ch, CURLOPT_HTTPHEADER, ['Authorization: Token YOUR_API_KEY', 'Content-Type: application/json']);
        curl_setopt($ch, CURLOPT_POST, true);
        curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($payload));
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
        curl_exec($ch);
        curl_close($ch);
    }
);

Comparison of JS vs. server‑side tracking:

Segmentation and Trigger Chains

After identification, you can update attributes on each visit: last_visit, cart_value, loyalty_level. This allows building segments for trigger messages. Create chains in the Carrot Quest interface without code:

• User viewed a product → didn't add to cart within 30 minutes → chat message.
• Order delivered → after 7 days email requesting a review.
• User hasn't visited in 60 days → discount coupon.

Debugging Tracking

In the browser console, carrotquest.track() and carrotquest.identify() output confirmation in development mode. In the Carrot Quest admin panel, go to Analytics → Events to see real‑time data.

Common integration mistakes:

• Forgetting to call carrotquest.identify() on pages where users log in via AJAX.
• Not passing the hash—events are sent, but identification is considered unverified.
• Using one API key for multiple sites—data mixes.
• Not checking the console for 404 errors on the Carrot Quest script.

Integration Steps

What’s Included

• Installation and verification of tracking code.
• User identification with hash verification.
• Event tracking (view, cart, order).
• Server API for events outside the browser.
• Segmentation by attributes.
• Documentation for all added events.
• Testing and error fixing.

Timelines and Cost

Timelines range from 5 to 10 days, depending on the number of events. Cost is calculated individually after analyzing your site structure. Contact us for a cost estimate—we'll tailor the work package.

We guarantee correct data transfer and zero console errors. Get a consultation through the form on our website—we'll propose a solution that pays off through increased conversion.

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.