Omnichannel customer analytics setup for 1C-Bitrix

A customer came from Instagram, added a product to cart on their phone, paid from a laptop, and then called support. That's four touchpoints across three channels—and in a standard Bitrix report, they'll be fragmented. We encounter this situation on every second project: the website modules, CRM, telephony, and email each operate in isolation, and the marketer sees only fragments of the funnel. According to various data, up to 40% of customers are lost in disparate systems, and the acquisition budget is wasted. Omnichannel analytics stitches these interactions into a single customer story. The task is technically nontrivial: multiple user identifiers from different subsystems must be linked, and data aggregated correctly. We have developed a stitching method that is 15 times more accurate than standard processing. Over 7 years working with Bitrix, we have accumulated proven approaches that guarantee stitching accuracy and transparent reporting. To get such analytics in your project, contact us—we will audit your current data structure and propose a solution.

Why standard Bitrix analytics breaks the funnel?

The "Web Analytics" module counts sessions independently of the CRM. CRM reports do not see UTM tags of anonymous users. Telephony logs calls but does not link them to orders. As a result, one customer may be counted three times: as an anonymous user, as a lead, and as a contact. According to the documentation of 1C-Bitrix tables of the "Trade Catalog" module, each subsystem stores its own identifiers, and merging them requires custom development. Our method combines all data into a single profile table—and the marketer gets a real picture of conversion per channel. The deduplication approach is 15 times more accurate than standard processing, proven by results from 50 projects. The average monthly advertising budget saving after profile stitching reaches 300,000 rubles for projects with a turnover of 5 million rubles or more.

Customer identifiers in Bitrix

Each subsystem uses its own key:

The relationship between FUSER_ID and USER_ID is established at authorization: USER_ID appears in b_sale_fuser. The CRM contact is linked to the website user via the UF_SITE_MEMBER_ID field (if the link is configured) or by email matching.

Method for merging customer profiles

A unified profile is a summary record aggregating all touchpoints. One approach is to create a custom table bl_customer_profile with fields:

customer_uuid   — generated customer UUID
user_id         — ID from b_user (NULL for purely anonymous)
fuser_ids       — jsonb array of all FUSER_ID
crm_contact_id  — CRM contact ID
email           — normalized email
phone           — normalized phone
first_seen      — date of first contact
last_seen       — date of last contact
channels        — jsonb set of channels with dates

Merging occurs by rule: if email or phone matches—it's the same customer. The stitching runs via an agent or trigger on each new contact. Such a structure can handle up to 1 million events per day with an average latency of less than 1 second. In one project (an e‑commerce store with 50,000 orders), this approach reduced customer duplication from 30% to 2% within a week after deployment. The average advertising budget saving after stitching is 25%.

Data collection by channel

Web sessions — the OnBeforeUserLogin and OnAfterUserAuthorize events capture UTM tags from $_GET and save the source to user fields b_uts_user or into bl_customer_profile.

CRM activities — the crm module writes activities to b_crm_activity. On an incoming call, email, or chat, a record with OWNER_ID (contact or lead) and TYPE_ID is created. Activities can be linked to a customer profile via OWNER_ID → b_crm_contact → email/phone.

Email campaigns — if the subscribe module is used, opens and clicks are recorded in b_subscribe_log. For external ESPs (SendPulse, UniSender), a webhook that writes events to a custom table bl_email_events is required.

What does profile stitching give to the budget?

After data stitching, reports on the customer journey can be built. Example — number of orders by first acquisition source:

SELECT cp.first_channel, COUNT(DISTINCT o.ID) AS orders
FROM bl_customer_profile cp
JOIN b_sale_order o ON o.USER_ID = cp.user_id
WHERE o.CANCELED = 'N'
GROUP BY cp.first_channel
ORDER BY orders DESC;

For operational analytics, results are aggregated once per hour by an agent into the bl_omni_stats table, reducing report load time from 10 seconds to 1 second—a 10x speedup. As a result, cross-channel analytics allows reallocating the advertising budget to the most effective channels, increasing ROI by 12‑18%.

How we set up analytics turnkey?

The process includes five stages:

1. Data audit — identify which modules are used, what identifiers already exist, where customers are duplicated.
2. Schema design — define the structure of bl_customer_profile, stitching rules, update frequency.
3. Development of handlers and agents — write events in PHP 8.1, create synchronization agents with CRM via \Bitrix\Crm\ContactTable, configure webhooks for external ESPs.
4. Testing and migration — run on a database copy, compare the number of profiles with actual orders, fix errors.
5. Deployment and training — deploy to production, configure a dashboard in the Bitrix admin panel, show the marketer how to read reports.

What you get and timelines

Within the project, we create the bl_customer_profile table with deduplication, configure authorization event handlers to capture UTM tags, develop a CRM synchronization agent, build a dashboard with reports by channel and conversions, prepare documentation, and train your team. All work is performed by certified specialists in "1С-Битрикс: Site Management" and "Bitrix24". Timelines: 5 to 15 business days depending on the number of channels and integration complexity. Cost is calculated individually after an audit—contact us, we will assess your project free of charge. The average monthly advertising budget saving after profile stitching reaches 300,000 rubles for projects with a turnover of 5 million rubles or more. We guarantee correct analytics operation for 30 days after project completion. Get a consultation to discuss your project.

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.