Automating Report Generation in Bitrix: Agents and Cron Setup

The Problem with Manual Report Exports

A manager spends 1–2 hours every morning: log into the admin panel, select dates, download Excel, email it. Mistakes happen—wrong columns, forgot to attach. For an urgent request for last month's report, they dig through all documentation. This is typical for dozens of companies on Bitrix. Lost time: 40 hours per month, costing roughly $2,000 at $50/hour. Automating report generation solves the problem in a day of development—and saves 90% of that cost, equating to over $24,000 annually. This article covers automated report generation in Bitrix, including cron setup and agent configuration for reports. But without experience, common pitfalls occur: cron not configured, write permissions on /upload/reports not set, agents not logging errors. Our certified Bitrix engineers with 10+ years of experience guarantee stable agent operation in production.

Why Automation Outperforms Manual Work

Manual export requires human involvement. An automated agent runs at 3 a.m., with no server load. Time savings exceed 90%, and the automation is 240 times faster than manual. Compare:

Automation cuts overhead by over 90% while eliminating human error.

How We Configure Agents and Cron

Setting Up Cron and Creating an Agent

On a production server, you must use system cron instead of an HTTP trigger. Add the job to crontab:

# /etc/cron.d/bitrix
*/5 * * * * www-data /usr/bin/php /var/www/site/bitrix/modules/main/include/cron_events.php > /dev/null 2>&1

Without cron, agents run only on site visits, which is unreliable.

\CAgent::AddAgent(
    'GenerateDailyReports();',
    'local',
    'N',
    86400,
    '',
    'Y',
    date('d.m.Y H:i:s', mktime(8, 0, 0)),
    30
);

Agent Template and Email Sending

function GenerateDailyReports(): string
{
    $reports = [
        [
            'type'      => 'orders',
            'filename'  => 'orders_' . date('Y-m-d') . '.xlsx',
            'params'    => ['date_from' => date('Y-m-d', strtotime('-1 day')), 'status' => null],
            'recipient' => '[email protected]',
        ],
        [
            'type'      => 'low_stock',
            'filename'  => 'stock_' . date('Y-m-d') . '.xlsx',
            'params'    => ['threshold' => 5],
            'recipient' => '[email protected]',
        ],
    ];

    foreach ($reports as $reportConfig) {
        try {
            $generator = ReportGeneratorFactory::create($reportConfig['type']);
            $filePath  = $generator->generate($reportConfig['params']);

            $savedName = '/upload/reports/' . $reportConfig['filename'];
            rename($filePath, $_SERVER['DOCUMENT_ROOT'] . $savedName);

            sendReportEmail($reportConfig['recipient'], $savedName, $reportConfig['filename']);

            \Bitrix\Main\Diag\Debug::writeToFile(
                date('Y-m-d H:i:s') . ' Report generated: ' . $reportConfig['filename'],
                '',
                '/local/logs/reports.log'
            );
        } catch (\Throwable $e) {
            \Bitrix\Main\Diag\Debug::writeToFile(
                date('Y-m-d H:i:s') . ' ERROR: ' . $e->getMessage(),
                '',
                '/local/logs/reports_errors.log'
            );
        }
    }

    return 'GenerateDailyReports();';
}

Email Delivery

The report is sent via Bitrix mail event or directly through PHPMailer with an attachment.

function sendReportEmail(string $to, string $filePath, string $fileName): void
{
    $absolutePath = $_SERVER['DOCUMENT_ROOT'] . $filePath;

    $mail = new \PHPMailer\PHPMailer\PHPMailer(true);
    $mail->CharSet = 'UTF-8';
    $mail->setFrom('[email protected]', 'Report System');
    $mail->addAddress($to);
    $mail->Subject = 'Auto-report: ' . $fileName . ' from ' . date('d.m.Y');
    $mail->Body    = 'The report was generated automatically. File attached.';
    $mail->addAttachment($absolutePath, $fileName);
    $mail->send();
}

Storage and Archive Cleanup

Generated files are stored in /upload/reports/ with a 30-day history. Cleanup of old files is a separate agent:

function CleanOldReports(): string
{
    $dir = $_SERVER['DOCUMENT_ROOT'] . '/upload/reports/';
    foreach (glob($dir . '*.xlsx') as $file) {
        if (filemtime($file) < time() - 30 * 86400) {
            unlink($file);
        }
    }
    return 'CleanOldReports();';
}

Archive page in the manager's personal cabinet—list of files with date and download link, with permission checks.

Which Reports to Automate?

Any report that can be built via Bitrix ORM or infoblocks. We frequently automate:

• Daily/weekly/monthly sales (grouped by managers)
• Warehouse stock with threshold alerts
• Orders in "pending payment" status
• Competitor price dynamics (if scraping is in place)
• Reconciliation statements with contractors

Each report type gets its own class implementing ReportGeneratorInterface. This allows adding new reports without changing the core. In practice, one factory can serve 20 different reports: configuration is an array, logic is in separate methods. For large datasets, we use chunked queries (500 records per chunk) and streaming write to XLSX via PhpSpreadsheet Writer to avoid memory overflow with 100,000 rows.

Security Against Unauthorized Access

Store files in /upload/reports/ with permission checks via $USER. Configure .htaccess to deny direct web access. The download link must be generated via a script with rights verification. Log all downloads to a separate file.

Typical Mistakes and Recommendations

1. Agents run only on site hits—solve with cron.
2. Incorrect permissions on /upload/reports—write access for www-data.
3. Code errors without logging—enable Debug::writeToFile.
4. Execution timeout—for large reports use set_time_limit(0).

What's Included in the Work

• Project analysis: identify needed reports and their parameters.
• Cron setup and agent creation per report.
• Development of report templates (Excel/PDF/CSV) with required data.
• Email delivery setup with attachment.
• Error logging and successful generation registration.
• Automatic cleanup of old files (configurable retention period).
• Documentation of the scheme and manager training.

Timeline Estimates

Timelines are approximate; final estimates are given after analyzing your project. Contact us to get an engineer consultation and cost estimate for your project. Order automated report generation setup—free managers from routine and errors. Our certified Bitrix specialists guarantee stable operation and error-free delivery.

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.