Web Analytics on 1C-Bitrix: GTM, GA4, Yandex Metrica Turnkey
After a standard Bitrix installation, analytics counters are not connected—the developer must manually place the Google Analytics and Yandex Metrica codes. A typical mistake is inserting the code directly into the template without considering caching: the counter ends up in the cache and is delivered incorrectly, especially with the active cache module. As a result, data on traffic, conversions, and user behavior is distorted, and business decisions are made based on unreliable statistics. For online stores on Bitrix, data loss means incorrect assessment of advertising effectiveness and missed profit. We solve this problem in 1–2 days, guaranteeing correct counter operation on all pages: from the homepage to product cards with dynamic parameters.
How to Avoid Conflict with Counter Caching?
Bitrix caches HTML blocks, and if the counter code falls inside a cached area (e.g., inside $APPLICATION->StartResultCache()), it is served identically to all users—unique parameters cid and gclid are not passed. In GA4, this leads to a loss of 30–50% of sessions. According to the documentation at dev.1c-bitrix.ru, counter caching requires placement outside cached areas. We move counters to footer.php or use tagged caching with dynamic exceptions.
What Problems Does Web Analytics Setup on Bitrix Solve?
Lack of end-to-end analytics. Many stores on Bitrix are integrated with 1C, CRM, and payment gateways (YuKassa, Sber, ATOL Online). Without end-to-end analytics, it's impossible to track the customer journey from click to payment. We configure Google E-commerce Enhanced transmission via Google Tag Manager and synchronize data with b_sale_basket and b_sale_order.
Incorrect traffic filtering. By default, reports include administrators, distorting metrics. We set up filtering by IP and cookie—exclude internal users. For online stores, this can reduce the "clean" conversion rate by 15–25%, but the data becomes real.
Why Google Tag Manager Is Better Than Direct Code?
We use Google Tag Manager as a single container for all scripts: GA4, Yandex Metrica, VK pixel, Facebook Pixel. This allows you to update codes without editing the template and without recaching. The principle scheme:
- In the
header.php file, we add two GTM calls: in <head> and immediately after <body>.
- We wrap them in a check
(!defined("B_PROLOG_INCLUDED") || B_PROLOG_INCLUDED !== true) die(); — this is mandatory for security.
- We place the code outside cached blocks: after the closing
<?$APPLICATION->ShowHead()?>.
- For each page type (homepage, catalog, detail, cart), we create triggers in GTM that pass parameters via Data Layer.
Example of minimal GTM installation in footer.php:
<?php
if (!defined("B_PROLOG_INCLUDED") || B_PROLOG_INCLUDED !== true) die();
?>
<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-XXXX" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->
Comparison of methods: direct code placement (GA4, Metrica) vs GTM
| Parameter |
Direct Code in Template |
Google Tag Manager (GTM) |
| Setup speed |
1–2 hours |
2–3 hours (with trigger setup) |
| Changes without developer |
No |
Yes, through GTM interface |
| Cache conflict |
High risk |
Low (proper setup) |
| Support for GA4 + Metrica + retargeting |
Only via multiple code snippets |
Single container |
| Error probability |
Medium |
Low (validation in GTM) |
GTM speeds up change implementation by 3 times: no need to edit the template, recache, or test via dev environment. All changes are made through the GTM interface and published in 1 minute.
Work Process
-
Analytics: audit current counters, identify cache issues, verify goals.
-
Design: Data Layer schema, triggers for events (add to cart, checkout, registration).
-
Implementation: install GTM, configure GA4 and Metrica, filter internal traffic, create initial set of goals.
-
Testing: verify on catalog pages, product cards, cart. Use Google Tag Assistant and Network requests.
-
Deploy: transfer settings to the live site, monitor for the first 48 hours.
Estimated Timelines
- Basic setup (GTM, GA4, Metrica, 5 goals) — 2 to 4 days.
- Extended (end-to-end analytics, 1C integration, conversion funnel, A/B tests) — 5 to 8 days.
Pricing is calculated individually—depends on catalog complexity, number of integrations, and required reports. Request a preliminary assessment—we will analyze your project in 1-2 days.
What Is Included in the Work
The work includes setting up the GTM container and placing codes for GA4, Yandex Metrica, and social media pixels; developing end-to-end analytics with data transmission via Data Layer; filtering internal traffic and excluding admin IPs. We also provide documentation on GTM triggers and variables, access to the container for self-management, and training for your employee. After deployment, we offer post-support for two weeks.
Typical Errors and Their Solutions
| Error |
Cause |
Solution |
| Counter missing on internal pages |
Code inserted only in the main template |
Place GTM in all template types via footer.php |
| Data loss with caching enabled |
Code inside a cached block |
Move code outside StartResultCache() or use dynamic exceptions |
| Incorrect Measurement ID |
Copied from an example |
Verify ID in GA4 settings |
| Inflated metrics |
Bots not filtered |
Set up bot filtering in Metrica and GA4 |
| Transactions not transmitted |
Data Layer not initialized |
Override dataLayer.push() on cart and order pages |
Guarantees and Experience
We have configured analytics on over 200 projects, 70% of which are online stores on Bitrix with integration of 1C and payment systems. We use the official documentation at dev.1c-bitrix.ru. We guarantee correct counter operation on all pages and conversion events.
Errors in counters lead to incorrect business decisions: you waste budget on ineffective channels, you don't see real customer drop-off points. Our guarantee—data you can trust.
Get a consultation on your project. Contact us—we'll tell you which metrics are critical for your business and how to set them up without data loss.
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
| Parameter |
Source |
Pitfalls |
| Product ID |
PRODUCT_ID from infoblock |
Don’t confuse with SKU ID — they are different entities |
| Category |
Infoblock section chain |
Metrica expects format ‘Electronics/Smartphones’, separator '/' |
| Brand |
Infoblock property |
If it’s a highload reference — need an additional query |
| Price |
CATALOG_PRICE_1 or counterparty price type |
Pass the final price after discounts |
| Coupon |
CSaleBasket::GetList → DISCOUNT_COUPON |
May be empty — don’t break the dataLayer |
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.
What is the Enhanced E-commerce specification and why does it matter?
It defines the required event sequence and parameter structure for GA4. Deviations cause silent data loss. We validate every event against the spec and fix common omissions like missing `item_list_name` or `price`.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
- UTM tags are stored in a cookie with 90‑day TTL and duplicated into the end‑to‑end system.
- When a lead is created in Bitrix24, we write UTM into custom deal fields.
- Call tracking replaces the number and links the call to the visit.
- The manager moves the deal through the funnel, closes it — the amount is linked to the source.
- The service aggregates expenses via ad account APIs.
- ROI = (revenue — expenses) / expenses for each campaign.
Tools Comparison
| Platform |
Strength |
Weakness |
| Roistat |
Multi‑channel attribution, call tracking, Bitrix24 integration (3x faster integration than Calltouch) |
Monthly cost |
| Calltouch |
Best call tracking on the market |
End‑to‑end analytics weaker than Roistat |
| CoMagic (UIS) |
Integration of calls + chat + analytics |
Outdated interface |
| Bitrix24 CRM Analytics |
Free, inside CRM |
Doesn’t calculate ad spend, no call tracking |
Where Exactly Is the Hole in Your Funnel?
Typical Bitrix store funnel:
| Stage |
What We Look At |
Where the Problem Usually Is |
| Catalog → Product page |
CTR by product |
Poor photos, no price in listing |
| Product page → Cart |
Add‑to‑cart rate |
No ‘Buy’ button on the first screen |
| Cart → Checkout |
Checkout initiation |
Unexpected shipping cost |
| Checkout → Order |
Completion rate |
Mandatory registration, sale.order.ajax failure |
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.
| Task |
Duration |
Deliverable |
| Yandex.Metrica + eCommerce (with correct dataLayer) |
3–5 days |
Event map + live counter |
| GA4 + Enhanced E‑commerce |
3–5 days |
Validated data stream |
| End‑to‑end analytics (Roistat/Calltouch + CRM) |
2–4 weeks |
Full attribution setup |
| Dashboards in DataLens / Looker Studio |
1–2 weeks |
Custom KPIs per channel |
| Comprehensive system |
4–8 weeks |
All of the above + audit report |
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.
