Flocktory 1C-Bitrix Integration: Tracker, Orders, Referral

Imagine: a customer places an order, lands on the "Thank You" page, and leaves without any additional offers. On one of our projects, an electronics online store increased its average order value by 25% after integrating Flocktory, thanks to post-purchase upsell. The platform analyzes the order composition and shows a relevant partner offer — the customer gets a discount on accessories, you get a commission. Flocktory works 3 times more effectively than standard popups due to viral reach and personalization based on real purchase data. According to Flocktory, clients save up to 40% on their advertising budget.

The basic integration includes connecting the tracker on all pages, transferring order data (ID, total, composition, customer email), and setting up push-user for authorized users. Additionally, you can implement the Shaker referral program with promo codes.

Stages of Flocktory Integration with 1C-Bitrix

1. Audit of the current implementation and access — we check templates, event handlers, and data output methods.
2. Connecting the Flocktory tracker on all pages — inserting the code into footer.php or via addExternalJs.
3. Configuring the order data block on the confirmation page — correct JSON with order composition.
4. Integrating push-user for authorized users — passing the email on every page.
5. Implementing the referral program (promo codes) — receiving and handling referral codes in the cart.
6. Testing and debugging (including debugging via ?flocktory_debug=1) — checking real orders.
7. Integration documentation and training for your managers.
8. Warranty of correct operation after deployment: we fix bugs at our expense.

How to Connect the Flocktory Tracker in 1C-Bitrix?

The tracker is connected once on all pages of the site. In the Bitrix template — in footer.php or via addExternalJs:

<!-- Flocktory tracker -->
<div class="i-flocktory" data-fl-action="track" data-fl-site-id="YOUR_SITE_ID"></div>
<script type="text/javascript">
(function(w,d,n,s,t) {
    w[n] = w[n] || [];
    w[n].push(function() { t = d.createElement(s);
        t.type = 'text/javascript'; t.async = true;
        t.src = '//api.flocktory.com/v2/loader.js?site_id=<?= FLOCKTORY_SITE_ID ?>';
        var sn = d.getElementsByTagName(s)[0];
        sn.parentNode.insertBefore(t, sn);
    });
    w.addEventListener('load', w[n][0]);
})(window, document, '_flocktory_callbacks', 'script');
</script>

FLOCKTORY_SITE_ID is a numeric identifier from the Flocktory dashboard. We recommend defining it as a constant via define in bitrix/php_interface/dbconn.php or in a settings module.

What Is Needed for Correct Order Data Transfer?

The key integration point is the "Thank You for Your Order" page. Flocktory shows the post-purchase popup only if it receives correct order data. Insert a block with data on the order success page:

<?php
// In the order confirmation page template
// Data is taken from the sale.order.checkout component or directly from ORDER_ID
$orderId = (int)$_GET['ORDER_ID'];
$order   = \Bitrix\Sale\Order::load($orderId);

if ($order && $order->getUserId() === $USER->GetID()) {
    $user = CUser::GetByID($order->getUserId())->Fetch();

    $items = [];
    foreach ($order->getBasket()->getOrderableItems() as $item) {
        $items[] = [
            'id'    => (string)$item->getProductId(),
            'title' => $item->getField('NAME'),
            'price' => (float)$item->getPrice(),
            'count' => (float)$item->getQuantity(),
        ];
    }

    $flData = [
        'order' => [
            'id'       => (string)$orderId,
            'price'    => (float)$order->getPrice(),
            'currency' => $order->getCurrency(),
        ],
        'customer' => [
            'name'  => trim($user['NAME'] . ' ' . $user['LAST_NAME']),
            'email' => $user['EMAIL'],
        ],
        'items' => $items,
    ];
?>
    <div class="i-flocktory"
         data-fl-action="purchase"
         data-fl-site-id="<?= FLOCKTORY_SITE_ID ?>"
         data-fl-user-name="<?= htmlspecialchars($flData['customer']['name']) ?>"
         data-fl-user-email="<?= htmlspecialchars($flData['customer']['email']) ?>"
         data-fl-transaction-id="<?= $flData['order']['id'] ?>"
         data-fl-total-price="<?= $flData['order']['price'] ?>"
         data-fl-items='<?= json_encode($flData['items'], JSON_UNESCAPED_UNICODE) ?>'>
    </div>
<?php
}
?>

The data-fl-items attribute must contain valid JSON. Flocktory uses this data to target the post-purchase offer: for example, if a customer bought an item from the "Electronics" category, a partner can show an offer for warranty or accessories.

Authorized User Data on All Pages

For personalization, Flocktory needs to know the email of the authorized user on any page:

<?php
// In footer.php, after connecting the main tracker
if ($USER->IsAuthorized()) {
    $currentUser = CUser::GetByID($USER->GetID())->Fetch();
?>
    <div class="i-flocktory"
         data-fl-action="push-user"
         data-fl-site-id="<?= FLOCKTORY_SITE_ID ?>"
         data-fl-user-email="<?= htmlspecialchars($currentUser['EMAIL']) ?>"
         data-fl-user-name="<?= htmlspecialchars($currentUser['NAME']) ?>">
    </div>
<?php
}
?>

Integration via Bitrix Events (Alternative Approach)

Instead of HTML blocks, you can pass data via a JavaScript object after receiving confirmation from the server. The OnSaleOrderSaved event handler saves data to the session, which is then read on the "Thank You" page:

AddEventHandler('sale', 'OnSaleOrderSaved', function(\Bitrix\Main\Event $event) {
    $order = $event->getParameter('ENTITY');
    $isNew = $event->getParameter('IS_NEW');
    if (!$isNew) return;

    $_SESSION['FLOCKTORY_ORDER'] = [
        'id'    => $order->getId(),
        'price' => $order->getPrice(),
    ];
});

This method is convenient if you need to avoid changes in templates. More about the OnSaleOrderSaved event — 1C-Bitrix documentation.

Why Might Flocktory Not Show the Popup?

Budget savings on customer acquisition with Flocktory can reach 40%. The integration pays for itself in an average of 3 months.

What Is Included in the Work

• Full audit of the current implementation and site access.
• Connecting the Flocktory tracker on all pages.
• Configuring order data transfer on the confirmation page.
• Integrating push-user for authorized users.
• Implementing a referral program with promo codes (optional).
• Testing and debugging all mechanics.
• Integration documentation and training for your managers.
• Warranty of correct operation after deployment.

Implementation Timelines

Get a consultation from an engineer — contact us to clarify the details of your project and estimate the cost of turnkey integration. Order on-site setup or remote assistance.

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.