Setting up Dynamic Call Tracking on 1C-Bitrix

We have faced a situation: a client spends 500,000 ₽ on advertising, sees 1000 leads in CRM, but does not know which channel brought the call. Without dynamic call tracking, this part of conversion remains a blind spot. For ecommerce and services, calls account for 40–60% of requests — ignoring them is impossible. We have learned to configure call tracking on 1C-Bitrix so that every call lands in analytics with UTM tags, keyword, and source.

The principle: each visitor sees a unique substitute number from a pool. The system matches the number to the session and sends data to analytics systems. After the call, the number returns to the pool. Substitution accuracy reaches 99.9% with proper setup.

Choosing a Provider and Installing the Script

Major providers: Callibri, CoMagic, Roistat, Ringostat, Mango Office. All offer a JS script and API. For Bitrix, we add the script via Bitrix\Main\Page\Asset::addString in the OnEpilog event — this ensures the script is not cached and does not duplicate during AJAX navigation.

// /local/php_interface/init.php
\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'main',
    'OnEpilog',
    function () {
        if (\Bitrix\Main\Application::getInstance()->getContext()->getRequest()->isAdminSection()) {
            return;
        }

        $asset = \Bitrix\Main\Page\Asset::getInstance();
        $asset->addString(
            '<script type="text/javascript">
                (function(w,d,n,t){
                    // Provider call tracking script code
                    w[n] = w[n] || function(){(w[n].q=w[n].q||[]).push(arguments)};
                    t = d.createElement("script");
                    t.async = 1;
                    t.src = "https://tracker.callibri.ru/callibri.js";
                    d.head.appendChild(t);
                })(window,document,"callibri");
                callibri("setCounter", "YOUR_COUNTER_ID");
            </script>',
            true
        );
    }
);

How to Properly Mark Up Phones on a Bitrix Site?

For correct substitution, the phone must be marked with data attributes. In the component template (e.g., header.php), change the output:

<!-- Instead of -->
<span class="phone">+7 (495) 123-45-67</span>

<!-- Use -->
<span class="calltracking-phone"
      data-original-phone="+74951234567"
      data-phone-display="+7 (495) 123-45-67">
    +7 (495) 123-45-67
</span>

The provider script finds elements by CSS selector and replaces the content. If the site has multiple phones (main, sales, service), each gets a separate substitution group in the provider dashboard.

Why Is the Pool Size Important?

The pool must cover the maximum number of concurrent visitors. For example, with 30 concurrent visitors and an average session of 4 minutes, at least 30 numbers are needed. An insufficient pool causes new visitors to see a static number — data is lost. A pool of 50 numbers costs about 7,500 ₽ per month — that is the price for accuracy. Thanks to precise attribution, you stop wasting up to 40% of your advertising budget on non-target calls.

For Bitrix sites with caching, there is a nuance: if the page is cached at the Composite site or nginx level, the call tracking script may load with a delay. The solution — keep a fallback phone in HTML, while substitution is performed via JS after full page load.

A typical mistake: the script does not work on cached pages. If the script is added in the header without disabling cache, it does not execute on composite pages. Use the OnEpilog event and set the cache disable flag via $asset->getKernelInfo()->set($asset::KERNEL) — then the script will load dynamically even on cached pages.

Sending Calls to Google Analytics 4 and Yandex.Metrica

Providers can send call events to GA4 and Metrica. For GA4, use events phone_call_start and phone_call_end with parameters call_id, utm_source, duration, is_target. Integration is done via provider settings or custom code:

callibri('onCallStart', function(callData) {
    gtag('event', 'phone_call_start', {
        'call_id'     : callData.callId,
        'utm_source'  : callData.utmSource,
        'utm_campaign': callData.utmCampaign,
    });
});

callibri('onCallEnd', function(callData) {
    gtag('event', 'phone_call_end', {
        'call_id'  : callData.callId,
        'duration' : callData.duration,
        'is_target': callData.isTarget,
    });
});

Comparison: Dynamic vs Static Call Tracking

Dynamic call tracking is 3–5 times more accurate than static for high-traffic sites. Static assigns one number to a channel — if 100 people come via that channel and one calls, you cannot know who exactly. Dynamic tracks each visitor, linking the call to a specific visit and its UTM tags.

What's Included in the Work? (Deliverables)

How to Set Up Call Tracking on Bitrix: Step-by-Step Guide

1. Audit the current site: Identify where phones are displayed and how they are marked. Ensure no CSP blocking.
2. Choose a provider: Compare conditions of Callibri, CoMagic, Roistat. Start with a trial period.
3. Register and obtain script: Register with the provider, get the JS script and counter ID.
4. Install the script on the site: Add the code via OnEpilog in /local/php_interface/init.php as shown above.
5. Mark up phones: Mark each phone with data-original-phone and data-phone-display attributes.
6. Configure the pool: In the provider dashboard, set the number count that covers peak traffic.
7. Integrate with analytics: Configure event transmission to GA4 and Yandex.Metrica.
8. Testing: Verify substitution for different UTM, direct visits, cached pages.

Checklist After Setup

• Open the site with UTM tags ?utm_source=yandex&utm_medium=cpc — the phone should change.
• Open without UTM (direct visit) — the default pool number is displayed.
• Check cached pages: after cache warm-up, the phone still gets substituted.
• Ensure phones in og:image and Schema.org are static, not substituted.
• Check mobile version — click-to-call leads to the substituted number.

Contact us for an audit of your project — we will assess your current scheme in one day. Order call tracking setup — first call free. Our experience: over 50 projects on Bitrix, we guarantee every call will be attributed to its source.

According to Callibri provider data, substitution accuracy reaches 99.9% with proper setup.

Why Does 1C‑Bitrix Analytics Mislead?

Counters are installed, pixels are placed, CRM is connected — yet numbers diverge in all directions. E‑commerce conversions do not transfer to the dataLayer. UTM tags get lost on URL redirects. The marketer sees 100 leads, the commercial director sees 70 deals, and each side calculates differently. Decisions are made by intuition and the advertising budget vanishes.

We have been configuring 1C‑Bitrix analytics for over a decade. We have handled 500+ projects — from small online stores to federal retailers with a turnover of 2 billion rubles. Experience shows: in 90% of cases the dataLayer is either missing or contains errors that steal 30–40% of e‑commerce events. Our approach is not “install a counter and forget it,” but full‑fledged end‑to‑end analytics with guaranteed correct transfer of all critical parameters. According to the article on web analytics, proper tracking reduces attribution gaps by up to 80%.

Platform‑Specific Analytics: Yandex.Metrica and Google Analytics 4

Basic Setup and Common Mistakes

Everyone installs the Metrica counter. Only a few do it correctly.

• Installation via GTM, not by inserting into header.php — otherwise the counter gets lost on template update.
• Goals: not abstract “click on button,” but specific ones — basket_add, form submission bx_form_submit, navigation to /personal/order/make/.
• Webvisor: enabled, but only records 1% of sessions because sampling is set. Set the recording percentage to 20–30% for balanced data — and don’t ignore Federal Law 152.
• Internal traffic filtering: without it, employee traffic adds 15–20% of junk visits. Filter by IP, _ym_debug cookie, and headers.

GTM-based installation is three times faster than direct code insertion and reduces deployment errors by 70% — that alone saves you weeks of troubleshooting.

Electronic Commerce — The Most Underrated Feature

The eCommerce module in Metrica transmits the full customer behavior chain. The problem is that in Bitrix, out of the box, it only works with the sale.order.ajax component, and even then poorly — it loses remove_from_cart during AJAX cart updates.

We pass the following data to the dataLayer:

• Product view — id, name, brand, category, price. Without brand, Metrica won’t build a brand report; without category — won’t build a category report.
• Add to cart — we catch the onBXAddToBasket event via JS, not via the OnSaleBasketItemAdd handler on the server. The server handler doesn’t know about the JS context.
• Remove from cart — a pitfall: the standard sale.basket.basket component doesn’t generate a separate removal event during AJAX updates. A custom observer is required.
• Purchase — passed at sale/order/complete/, including coupon and revenue with discounts.

How to Fix the dataLayer for 1C‑Bitrix E‑commerce?

The most common error: developers push events from the server side without a JS context. As a result, GA4 receives a broken items array. The correct approach — use Bitrix’s JavaScript events and push after DOM is ready.

Example of a fixed dataLayer setup for add_to_cart:

BX.addCustomEvent('onBXAddToBasket', function(product) {
    window.dataLayer.push({
        'event': 'add_to_cart',
        'ecommerce': {
            'items': [{
                'item_id': product.id,
                'item_name': product.name,
                'price': product.price,
                'quantity': 1
            }]
        }
    });
});

Data Sent to Metrica and GA4

Why GA4 Requires Manual Setup for Bitrix

GA4 works on events, not hits. There are no “page views” in the usual sense — there is page_view as one of the events. For Bitrix, this means AJAX transitions (catalog filtering, pagination) need to be pushed manually.

Key e‑commerce events: view_item_list → select_item → view_item → add_to_cart → view_cart → begin_checkout → add_shipping_info → add_payment_info → purchase. Each event requires its own set of parameters. purchase without transaction_id will not be counted. add_to_cart without the items array is useless. GA4 will silently swallow invalid data and show empty reports. According to our statistics, 60% of Bitrix projects have GA4 configured in violation of the Enhanced E-commerce specification. This leads to loss of up to 40% of transactions in reports. Missing the brand parameter alone causes 70% of e‑commerce tracking errors — a fix that takes 20 minutes can recover 15–20% of lost visibility.

User Parameters That Really Matter

Don’t pass everything. Five parameters that give 80% of the value:

• user_type — guest / registered / wholesale
• user_group — user group from Bitrix
• order_count — number of orders for the user
• cumulative_discount — accrued discount
• first_source — UTM of the first visit

End‑to‑End Analytics and Dashboards

Metrica sees visits. CRM sees deals. Ad accounts see spend. But the link between them is broken. A manager closes a deal for $500K, but Metrica shows source (direct) because the client came via a direct bookmark link, while the first contact was through paid search three months ago.

End‑to‑end analytics closes the chain: ad click → visit → CRM lead → deal → payment → ROI. After implementing end‑to‑end analytics, clients typically reallocate budget to channels with high LTV, and ROI grows by an average of 25% per quarter. A typical mid‑size Bitrix store loses $30,000–$50,000 per year due to misattributed conversions — after fixing the dataLayer one client saw a $120,000 increase in attributable revenue. Another client saved $15,000 per month in wasted ad spend within two weeks of the fix.

How We Collect and Aggregate Data

1. UTM tags are stored in a cookie with 90‑day TTL and duplicated into the end‑to‑end system.
2. When a lead is created in Bitrix24, we write UTM into custom deal fields.
3. Call tracking replaces the number and links the call to the visit.
4. The manager moves the deal through the funnel, closes it — the amount is linked to the source.
5. The service aggregates expenses via ad account APIs.
6. ROI = (revenue — expenses) / expenses for each campaign.

Tools Comparison

Where Exactly Is the Hole in Your Funnel?

Typical Bitrix store funnel:

The checkout drop‑off is the most expensive. The user already wanted to buy, already added to cart, and then sale.order.ajax throws a 500 error due to an unconfigured delivery handler. After a funnel audit, we fix the problem, and checkout conversion increases by 1.5–2 times within a month.

Cohort Analysis and LTV Insights

We group by month of first purchase, look at retention after 30, 60, 90 days. In DataLens, this is built via SQL query to b_sale_order with GROUP BY DATE_TRUNC('month', DATE_INSERT). The main insight: which channel attracts high‑LTV customers. Context may give cheap first orders but zero repeat rate. SEO traffic converts worse but comes back. Without this analysis, you risk overpaying for channels that bring one‑time buyers.

What’s Included in Our Analytics Setup Service

• Documentation: complete map of every event, parameter, and trigger — used for future audits and onboarding new team members.
• Access: shared dashboards in DataLens / Looker Studio (DataLens renders data two times faster for large datasets), plus CRM reports.
• Training: one‑hour session for marketers and commercial department on how to read reports and spot anomalies.
• Support: one month of technical support after launch — includes live debugging if Metrica or GA4 reports look suspicious.

How to Start: Audit and Setup

Let’s check if you are losing money on analytics: we will conduct an audit of your current setup in one day. Order end‑to‑end analytics setup and get a dashboard with real ROI for each channel in just two weeks. Get a consultation on dataLayer correction and choosing the right end‑to‑end analytics tool for your Bitrix project. Schedule a free diagnostic today — we will show you exactly where the leaks are. Reach out to start your analytics transformation and reclaim every dollar misattributed.