Bitrix24 Reports Setup for Managers – Custom KPI Dashboards

A manager opens Bitrix24, goes to CRM analytics, and sees charts that don't answer his questions. He can't see how many deals each manager closed, the average deal duration, or how many leads went stale without processing. Standard reports show aggregate numbers but don't provide management answers. Configuring Bitrix24 reports for managers is not about pretty graphs—it's about precise data for decisions. For example, a client company was losing 30% of leads due to lack of analytics; after report setup, conversion increased by 15%. In 70% of our projects, we identify suboptimal funnel stages, yielding an additional 10–20% conversion lift.

Our team has set up reporting for 55 companies, reducing weekly report preparation time by an average of 8 hours. Each report is validated against the data: we double‑check queries and groupings. The manager's time savings after implementation reach 200,000 ₽ per year. Contact us for an assessment of your data—we'll show which metrics you should track.

What built‑in CRM analytics provides

Bitrix24 offers several analytics tools. The choice depends on the required depth of detail and flexibility.

CRM analytics — built‑in reports: sales funnel, deal dynamics, sales plan, manager efficiency. Filterable by period, responsible person, and funnel. Limitations: no custom fields, cannot change grouping, no cross‑tabulation. Typical case: a company with 500 deals per month can't see distribution by manager—after funnel setup, analysis time is cut by 3x.

BI constructor — available on Professional and higher plans. Access via CRM → Analytics → BI constructor. Bitrix24 generates an OData endpoint, which connects to external BI tools: Google Looker Studio, Power BI, Yandex DataLens. This is the most flexible path for non‑trivial reports. We use it in 85% of projects that require custom analytics. Detailed documentation can be found at Bitrix24 Helpdesk.

Lists and smart processes are not reports in the usual sense, but they are sortable and filterable lists with Excel export. They cover some tasks with minimal effort.

Configuring built‑in reports for your KPIs

Before building a custom solution, check the built‑in reports after proper configuration. Often the problem is not the tool but the semantics of the data.

Sales funnel: Shows conversion between stages. Works correctly only with proper stage semantics (STAGE_SEMANTIC_ID). If all stages are "In progress," the funnel shows a single bar. Check: CRM → Settings → Dictionaries → Deal stages. Stages with semantics "Success" (S) and "Failed" (F) form funnel exits. Configuration takes 30 minutes.

Manager efficiency: Calculates the count and amount of closed deals. Filters by period and direction. Useful for weekly meetings. Limitation: it does not consider custom fields—if KPIs depend on a custom field like "Service type," this report is useless. Solution: move to the BI constructor.

Sales plan: Set up in CRM → Analytics → Plan. A monthly target amount for each manager. Bitrix automatically calculates the percentage of completion based on successful deals. Simple, but only tracks the deal amount (OPPORTUNITY). Not suitable for multi‑currency or product‑based KPIs.

What to do when standard reports aren't enough?

For managers who need non‑trivial reports, the BI constructor is the most flexible tool. Compared to built‑in reports, it offers 10 times more data fields and 5 times faster report generation. Let's look at connecting to Google Looker Studio.

1. CRM → Analytics → BI constructor → create an access key
2. Copy the OData endpoint, e.g., https://your-portal.bitrix24.ru/rest/{user_id}/{key}/bi.dataset.data.json
3. In Looker Studio: Add data source → JSON connector → paste the URL
4. Configure the dataset: fields are mapped automatically

Available data includes: deals, leads, contacts, companies, product positions, activities (calls, emails, meetings). Custom fields (UF_CRM_*) are included in the export.

Comparison of reporting approaches

The choice depends on KPI complexity and budget. For quick solutions, built‑in reports suffice; for deep analytics, the BI constructor; for unique scenarios, custom development, which is 2 times more flexible but costs 5 times more. However, built‑in reports are 3 times faster to set up than the BI constructor, making them ideal for initial needs.

Five reports every manager needs

Automatic report distribution

A manager shouldn't have to log into Bitrix24 every morning. Looker Studio and DataLens have a scheduled send feature—a PDF report arrives on email on Monday morning. Bitrix24 itself has no automatic CRM report distribution—only manual export. We set up distribution for any schedule.

What's included in turnkey report setup?

• Audit of current reports and manager needs
• Configuration of built‑in CRM analytics (funnel, efficiency, plan)
• Connection of BI constructor and integration with Looker Studio / Power BI / DataLens
• Creation of custom dashboards with the required metrics
• Employee training on using reports
• Documentation and instructions
• Automatic scheduled report distribution

We guarantee that every report answers a management question. Request a consultation—we'll tell you which reports will benefit your business and offer a pilot project on your data.

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.