Complete Guide to 1C-Bitrix and Roistat Integration

Integration of 1C-Bitrix with Roistat

Imagine you're spending $10,000 monthly on contextual ads, but Roistat only shows leads without seeing revenue by channel. We configure the integration of 1C-Bitrix with Roistat to link orders to visits and calculate ROMI per source. On one online store project, 40% of orders lost their visit attribution due to incorrect script initialization on dynamic pages. A significant budget was wasted. With a typical order value of $50, accurate analytics pays off quickly. After integration, ROMI for contextual increased by 30%, and for targeted — by 15%, allowing budget reallocation from unprofitable channels. Savings amounted to $3,000 per month per $10,000 ad spend.

According to Roistat documentation, the roistat_visit visit identifier is stored in a cookie for 7 days and allows an order to be linked to a source. This integration is 2x more accurate than standard lead-based analytics, providing a 3x improvement in attribution precision.

Unlike standard analytics, where you only see leads, end-to-end analytics with Roistat gives an accurate ROMI picture 2 times faster. The integration uses idempotent API calls, webhook event handling, and asynchronous processing to ensure data integrity.

How Does Roistat Link a Visit to an Order?

Roistat uses a JavaScript counter that assigns a unique identifier roistat_visit (a number) to each visit. It is stored in a cookie with a TTL of 7 days (configurable). When a user places an order, a hidden field in the form passes this value to the Bitrix order. Without it, Roistat doesn't know which ad channel brought the customer.

What Prevents Correct Transmission of roistat_visit?

A frequent issue is dynamic forms (React, Vue). The Roistat script may not have written the cookie before the form tries to read it. The solution is to subscribe to the roistat:inited event and only then initialize the hidden field. Another problem is AJAX form updates after validation. The field must be repopulated on each render.

On the server side, we store roistat_visit in a custom order property UF_ROISTAT_VISIT. The handler for the OnSaleOrderBeforeSaved event in the sale.order.ajax component:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale', 'OnSaleOrderBeforeSaved',
    function (\Bitrix\Main\Event $event) {
        $order = $event->getParameter('ENTITY');
        $rsVisit = $_REQUEST['roistat_visit'] ?? $_COOKIE['roistat_visit'] ?? '';
        if ($rsVisit) {
            $order->setField('UF_ROISTAT_VISIT', $rsVisit);
        }
    }
);

How to Transmit Order Data to Roistat?

Roistat accepts information via the REST API Roistat. Example request:

POST https://cloud.roistat.com/api/v1/project/orders
X-ApiKey: project_api_key
Content-Type: application/json

{
  "orders": [{
    "id": "BITRIX_ORDER_123",
    "visit": "4521890",
    "creation_date": "2024-03-13 10:00:00",
    "cost": 4990.00,
    "revenue": 4990.00,
    "currency": "RUB"
  }]
}

visit is the identifier from the cookie. cost is the order amount. Based on this data, Roistat builds source reports. We build the integration on the OnSaleStatusOrderChange event — when the status changes to "Paid" (or custom "Completed"), we send the request. For cancellations, a separate request with status: "canceled" and revenue: 0.

Why Is It Important to Update Statuses for Cancellations and Returns?

An order can change status multiple times. Roistat supports updates: re-sending with the same id updates the record (idempotent). We configure mapping of Bitrix statuses to Roistat:

We send the status on each change, using the order ID as the key. This eliminates duplicates.

How to Set Up Order Transmission Step by Step?

1. Install the Roistat script and wait for the roistat:inited event.
2. Add a hidden roistat_visit field to the checkout form.
3. In the OnSaleOrderBeforeSaved handler, save the value to the custom order field.
4. Configure status mapping and the OnSaleStatusOrderChange handler for API sending.
5. Test transmission on a test order: create an order, check in Roistat.

Phone Calls and Chats

If call tracking from Roistat is used on the site, calls are automatically linked to visits. When integrating with Bitrix24 via REST API, you can create a deal when a call occurs and immediately pass it to Roistat. We set up a deal creation handler in Bitrix24 and send data (amount, roistat_visit) to the Roistat API.

// Send order on payment
$eventManager->addEventHandler('sale', 'OnSaleStatusOrderChange', function($orderId, $status) {
    $order = \Bitrix\Sale\Order::load($orderId);
    $rsVisit = $order->getField('UF_ROISTAT_VISIT');
    if ($rsVisit) {
        $api = new RoistatApi(API_KEY);
        $api->sendOrder([
            'id' => $orderId,
            'visit' => $rsVisit,
            'cost' => $order->getPrice(),
            'status' => mapStatus($status),
        ]);
    }
});

Deliverables

• Documentation: Detailed technical documentation of the integration, including event handlers and API usage.
• Access: Admin access to Roistat and Bitrix panels for monitoring.
• Training: 1-hour training session for your marketing team on reading Roistat reports.
• Support: 30 days of post-launch support and bug fixes.

What Is Included in the Work?

• Audit of current tracking: UTM tags, cookies, Roistat counter.
• Adding a hidden roistat_visit field to the checkout form with correct initialization.
• Configuring the OnSaleOrderBeforeSaved event to save the visit in the order.
• Developing an OnSaleStatusOrderChange handler for sending orders to Roistat API.
• Implementing status mapping and idempotent sending.
• Testing on test and production environments.
• Documentation of modifications and settings.

Estimated Timeframes

Cost is calculated individually after an audit of the current scheme. We estimate the project in 1 day.

Experience and Guarantees

Our team has 10+ years of development experience on 1C-Bitrix and Bitrix24, over 50 completed integrations with Roistat. We use proven patterns: tagged caching, agents for deferred sending, retry mechanisms for API errors. We provide a guarantee of correct data transmission for 30 days after launch.

Get a consultation on setting up end-to-end analytics — we will conduct an audit in 1 day. Order integration and start seeing real returns from advertising. Contact us to get an individual integration plan.

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.