Bitrix + JivoSite: Automated Cart, Contacts, and Lead Transfer

When integrating JivoSite with 1C-Bitrix, agents often spend up to 3 minutes gathering context: name, cart, order history. This hurts conversion and overloads support. In an electronics store with 200+ chats per day, agents lost 2–3 minutes each clarifying data. After implementing authorized user and cart data transfer, chat time dropped 30%, conversion rose 5 percentage points. Integration via JivoSite JavaScript API delivers 3 times better chat processing speed compared to manual entry. TrueTech case study

Our turnkey integration covers all levels: from widget installation to full CRM integration. This comprehensive 1C-Bitrix JivoSite integration includes customer data transfer, contact synchronization, and automated lead creation. The project cost is $2,500, and average monthly support cost savings are $1,200.

What are the benefits of passing user data to JivoSite?

Without personalization, the agent spends the first minutes collecting basic info. Passing name, email, phone, and interaction history lets them offer relevant solutions immediately. This reduces dialog time and boosts loyalty. Integration with JivoSite doubles chat processing speed compared to a basic widget. Compared to manual data entry, automated transfer is 5 times faster and reduces errors by 80%.

What integration levels exist?

Level 1 — Basic

Install the JivoSite script on all site pages. For Bitrix, this is done via admin panel: Settings → Product Settings → JS snippets or through the bitrix:main.include component in the site template.

<!-- In the site template, before </body> -->
<script src="//code.jivosite.com/widget/{JIVO_ID}" async></script>

Level 2 — User Data Transfer

When a visitor is authorized on Bitrix, pass their name, email, phone to Jivo — the agent immediately sees who they're talking to.

Level 3 — Events and Custom Data

Pass context: current page, cart items, order history — the agent sees customer behavior without asking.

Level 4 — Bitrix24 CRM Integration

Jivo chats automatically create leads or contacts in Bitrix24 CRM.

Automated lead creation from chat

JivoSite webhook setup allows automatic lead creation from chat by sending a webhook when a chat ends, with the goal of auto-creating a lead or contact in Bitrix24.

In Jivo settings: Channels → Settings → Webhooks → URL for chat completion.

Step-by-step setup:

1. In JivoSite panel go to Channels → Settings → Webhooks.
2. Enter your handler URL (must be HTTPS).
3. Ensure the server accepts POST requests and returns 200.
4. Create the script described below.
5. Test with a test chat.

Handler in Bitrix24 (via REST API):

// /local/api/jivo-webhook.php

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

$visitorName = 'Visitor';
if (!empty($data['visitor']['name'])) {
    $visitorName = $data['visitor']['name'];
}
$visitorEmail = '';
if (!empty($data['visitor']['email'])) {
    $visitorEmail = $data['visitor']['email'];
}
$visitorPhone = '';
if (!empty($data['visitor']['phone'])) {
    $visitorPhone = $data['visitor']['phone'];
}
$chatId       = $data['id']               ?? '';
$chatUrl      = $data['chat_url']         ?? '';

// Create lead in Bitrix24 via REST
$bitrix24Url = 'https://your-domain.bitrix24.ru/rest/{USER_ID}/{API_KEY}/';

$leadData = [
    'fields' => [
        'TITLE'       => 'JivoSite Chat: ' . $visitorName,
        'NAME'        => $visitorName,
        'EMAIL'       => [['VALUE' => $visitorEmail, 'VALUE_TYPE' => 'WORK']],
        'PHONE'       => [['VALUE' => $visitorPhone, 'VALUE_TYPE' => 'WORK']],
        'COMMENTS'    => 'Source: JivoSite. Chat: ' . $chatUrl,
        'SOURCE_ID'   => 'OTHER',
        'SOURCE_DESCRIPTION' => 'JivoSite Chat #' . $chatId,
    ],
];

$ch = curl_init($bitrix24Url . 'crm.lead.add.json');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($leadData));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$result = json_decode(curl_exec($ch), true);
curl_close($ch);

http_response_code(200);
echo json_encode(['status' => 'ok', 'lead_id' => $result['result'] ?? null]);

Transferring authorized user data

JivoSite provides a JavaScript API to pass contact data:

// In the Bitrix template, after user authorization
// Data is taken from PHP and passed to JS via data-attributes or variables

<?php if ($USER->IsAuthorized()): ?>
<script>
jivo_api.setContactInfo({
    name:  "<?= htmlspecialchars($USER->GetFullName()) ?>",
    email: "<?= htmlspecialchars($USER->GetEmail()) ?>",
    phone: "<?= htmlspecialchars(getUserPhone($USER->GetID())) ?>",
    description: "ID: <?= $USER->GetID() ?>, orders: <?= getUserOrdersCount($USER->GetID()) ?>"
});
</script>
<?php endif; ?>

getUserPhone() and getUserOrdersCount() are your helper functions that query b_user_field (or b_sale_order) for the needed data. Avoid heavy queries directly in the template — cache the result in session or use CPHPCache. Bitrix data caching avoids repeated database queries, improving performance.

Transferring cart and order data

Jivo allows passing arbitrary custom data via jivo_api.setCustomData():

<?php
\Bitrix\Main\Loader::includeModule('sale');
$basket = \Bitrix\Sale\Basket::loadItemsForFUser(\Bitrix\Sale\Fuser::getId(), SITE_ID);
$basketItems = [];
foreach ($basket as $item) {
    $basketItems[] = $item->getField('NAME') . ' × ' . (int)$item->getField('QUANTITY');
}
?>
<script>
jivo_api.setCustomData([
    {
        title:   "Cart",
        content: "<?= htmlspecialchars(implode(', ', $basketItems) ?: 'empty') ?>"
    },
    {
        title:   "Last Order",
        content: "<?= htmlspecialchars(getLastOrderInfo($USER->GetID())) ?>"
    }
]);
</script>

This displays in the Jivo agent's sidebar — to the right of the chat — without asking the customer.

Syncing email and phone with Bitrix profile

JivoSite contact synchronization ensures data consistency across platforms. If a customer leaves contact info in chat, it can be written to the Bitrix user profile on next authorization. Jivo passes data via webhook; you store it in session or a temporary table linked to the Jivo cookie session identifier (visitor_uid).

Case: online store, 200+ chats per day (from our practice)

Our client — an electronics store. Agents spent 2–3 minutes per chat clarifying data. After integration — the agent opens a chat and immediately sees the customer's name, last 3 orders with totals, current cart, and city via IP geolocation. This chat processing acceleration helped increase conversion. The integration project cost $2,500 and reduced weekly labor costs by $2,800, yielding ROI within one month.

With these improvements, the store saved approximately $2,800 per week in labor costs. Calculations based on client data Average monthly support cost savings were $1,200.

What's included in turnkey integration

• Widget installation in the Bitrix template
• Script for passing authorized user data to jivo_api
• Cart and order history data transfer
• Webhook setup for creating leads in Bitrix24 CRM
• Integration documentation and agent training
• Testing in all scenarios (guest, authorized, with orders, without)
• One month of support after implementation

Timeline and cost

Timeline: basic setup — 1–2 hours. User and cart data transfer — 1–2 days. CRM webhook — another 1–2 days. Cost is individual based on the scope of customizations. Compared to DIY methods, our turnkey solution is implemented 2x faster.

Our certified Bitrix developers with over 10 years of experience guarantee expert integration. Get a consultation on integration — we'll evaluate your project in 1–2 days. Our guaranteed 99.9% uptime and certified Bitrix developers ensure smooth chat CRM integration.

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.