Setting up Click Heatmaps on 1C-Bitrix
Imagine: on a catalog page 80% of clicks land on the product name, yet the link only leads to the "Add to cart" button. A click heatmap visualizes this behavior—a clear sign that the layout doesn't match user expectations. But for the map to be reliable, it must be correctly configured for 1C-Bitrix. According to our statistics, 90% of heatmap issues on this CMS stem from AJAX content and dynamic loading. Fixing this yields accurate data as early as the next day. In this article we'll dive into how to configure tools (Yandex.Metrica, Hotjar, Clarity) without losing data. For a quick start, contact us—we'll help with selection and integration.
Choosing a Heatmap Tool
| Tool |
Bitrix Specifics |
Recommendation |
| Yandex.Metrica (click map) |
Requires reinitialization on AJAX |
For simple sites without SPA; setup is 2x faster than Hotjar |
| Hotjar |
Full sessions, field masking, segmentation |
For detailed UX analysis; starts at $39/month |
| Microsoft Clarity |
Automatically records clicks, field masking |
Best free alternative; 3x cheaper than Hotjar |
Yandex.Metrica is better for sites with minimal dynamics, Clarity for free session recording. Hotjar offers more details but requires a budget.
Yandex.Metrica: Built-in Click Map
The most accessible tool is the built-in click map of Yandex.Metrica. It is enabled with the clickmap: true flag. No additional code is needed—Metrica intercepts clicks via a global event handler.
The problem on Bitrix arises with AJAX navigation and dynamically added elements. Metrica binds handlers on page load—clicks on elements that appear after an AJAX response (e.g., products in infinite scroll) are not captured in the map. Solution: call ym(ID, 'hit', url) after each AJAX update. This reinitializes the tracker and records clicks on new elements. More details on handling AJAX in Bitrix.
Why AJAX Clicks Aren't Recorded in the Standard Map?
The standard tracker binds event handlers on page load. After an AJAX request, the DOM changes but handlers remain on old elements. To fix this, after each AJAX update call ym(ID, 'hit', url) for Metrica or hj('identify') for Hotjar. With Clarity, reinitialization is unnecessary—it automatically tracks changes. In practice, if your site uses infinite scroll in the catalog, without modification you may lose up to 30% of clicks. A properly configured integration raises recording accuracy to 95%. For example, fixing a misconfigured heatmap saved one client $1,500 monthly in ad optimization.
Hotjar and Microsoft Clarity on Bitrix
For more detailed heatmaps, Hotjar or Microsoft Clarity are used. Both are added via a single script in <head>. In Bitrix, this is done through init.php or directly in the template:
// In header.php of the template
\Bitrix\Main\Page\Asset::getInstance()->addString(
'<script>/* Hotjar Tracking Code */
(function(h,o,t,j,a,r){
h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)};
h._hjSettings={hjid: XXXXXXX, hjsv: 6};
a=o.getElementsByTagName("head")[0];
r=o.createElement("script"); r.async=1;
r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv;
a.appendChild(r)
})(window,document,"https://static.hotjar.com/c/hotjar-",".js?sv=");
</script>',
true
);
How to Exclude Service Pages from the Heatmap?
Click maps should not collect data on login, cart, checkout pages—they contain personal data. Exclusion protects against leaks and complies with 54-FZ. In Yandex.Metrica, use "Filters" in counter settings: exclude /bitrix/, /personal/, /cart/, /order/. For Hotjar, use the suppressSession parameter or conditional initialization in the template:
<?php
$excludePaths = ['/cart/', '/order/', '/personal/'];
$currentPath = $_SERVER['REQUEST_URI'];
$exclude = false;
foreach ($excludePaths as $path) {
if (strpos($currentPath, $path) === 0) {
$exclude = true;
break;
}
}
if (!$exclude):
?>
<!-- Hotjar script -->
<?php endif; ?>
Special Considerations for Login Pages
Personal account and checkout pages in Bitrix are wrapped by the bitrix:main.login.form component or rules in the main module. Hotjar and Clarity record such pages, but if a user is not logged in, the URL may redirect—the tracker will record clicks on the login page instead of the target. Check via the "Pages" report in Clarity: if /order/ appears with zero clicks and a high exit rate, users are not reaching it due to redirect.
How to Segment Heatmaps by Device?
Click heatmaps on mobile and desktop should be analyzed separately. In Hotjar it's automatic with a toggle. In Metrica, use segments in the "Click Map" report. Bitrix adaptive templates often change element order on mobile (CSS order), so a "red spot" on desktop and mobile will be on different DOM elements, even if visually in the same screen location. Analyze separately to avoid missing UX issues.
Example code for reinitializing Yandex.Metrica after AJAX
BX.addCustomEvent('onAjaxSuccess', function(){
ym(ID, 'hit', window.location.href);
});
Experience and Guarantees
Our team has 8 years of experience in 1C-Bitrix development, certifications, and over 200 completed projects. We guarantee correct heatmap operation accounting for AJAX, SPA, and responsiveness. By our estimates, incorrect configuration can reduce data accuracy by up to 30%, and missed opportunities from wrong decisions can reach a significant portion of turnover. With proper integration, accuracy rises to 95%. Investment of $500 in setup pays back quickly. Get a consultation—contact us to discuss your project.
What's Included in the Work?
- Selection of optimal tool (Metrica, Hotjar, Clarity) based on business needs
- Integration via template or init.php with caching considerations
- Exclusion of service pages (personal account, cart, checkout)
- AJAX navigation modifications for correct click recording on dynamic elements
- Device segmentation and team training on report usage
Setup Process
- Analysis — study site architecture, identify problem areas (AJAX, redirects)
- Planning — choose tool and integration scheme, agree on exclusions
- Implementation — add code to template, set up reinitialization
- Testing — verify recording on all page types and devices
- Deployment — launch to production and provide access to reports
Timeline: 1 to 3 business days depending on complexity. For an accurate estimate, contact us—we'll provide a free consultation and find the best solution.
| Stage |
Time (hours) |
| Analysis and tool selection |
1-2 |
| Integration and exclusions |
2-4 |
| AJAX adjustments |
2-6 |
| Testing |
1-2 |
| Total |
6-14 |
Order heatmap setup — we will conduct an audit within 1 day and offer the optimal solution.
What Professional 1C-Bitrix Installation Includes
We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.
How to Choose Hosting and Edition for 1C-Bitrix Installation?
BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.
VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.
Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
What Server Settings Are Critical for 1C-Bitrix?
Web Server and PHP
nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.
Database and Caching
MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:
'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
SSL, Email, and Cron
SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.
Security and Administration
File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.
How Long Does 1C-Bitrix Installation and Configuration Take?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.
Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.
Deliverables
- Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
- Installed and activated license of the required edition.
- SSL certificate, email settings, cron and backups.
- Documentation: all configuration parameters, access credentials, cron tasks.
- Content manager training: how to log into admin panel, add products, upload images.
- Post-installation support for 30 days — consultations on settings.
Why Trust Professionals with Installation?
Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.
