Imagine: you've set up Webvisor, but sessions aren't being recorded. The browser console is full of CSP errors. Sound familiar? Over 10+ years, we've conducted more than 500 Bitrix site audits and found Webvisor issues in every third one. We'll show you how to properly configure Webvisor on 1C-Bitrix so session recording runs stably and without data loss. Our team has accumulated experience on hundreds of projects—from small online stores to large catalogs with millions of product items.
Why Webvisor often doesn't work on Bitrix?
Webvisor won't work on an HTTPS site with incorrect CSP headers—session recording goes through a Yandex iframe, and the browser blocks it if frame-ancestors isn't allowed in Content-Security-Policy. The second common cause: the Metrica tag is inserted via Google Tag Manager, GTM loads asynchronously, and Webvisor initializes after the user has already performed their first actions—the session start is lost. Third—AJAX navigation: without an explicit ym('hit') call after each transition, Webvisor records only the first page. According to our statistics, 70% of sites with AJAX navigation lose up to 40% of sessions due to this error.
How to properly place the Metrica tag?
Yandex requires placing the tag as high as possible in the <head>. In Bitrix, the standard method is insertion via the OnBeforeProlog event in init.php or directly in the prolog file /bitrix/templates/TEMPLATE/header.php.
In /bitrix/php_interface/init.php:
AddEventHandler('main', 'OnBeforeProlog', function() {
ob_start();
?>
<!-- Yandex.Metrica -->
<script>
(function(m,e,t,r,i,k,a){m[i]=m[i]||function(){(m[i].a=m[i].a||[]).push(arguments)};
var z = m[i],d=e.createElement(t),n=e.getElementsByTagName(t)[0];
d.async=1;d.src=r;d.id='metrika-';
n.parentNode.insertBefore(d,n);
z(i,'init', { id: XXXXXXXX, webvisor: true, clickmap: true, trackLinks: true });
})(window, document, 'script', 'https://cdn.jsdelivr.net/npm/yandex-metrika@latest/metrika.js', 'ym');
</script>
<!-- /Yandex.Metrica -->
<?php
$html = ob_get_clean();
$GLOBALS['APPLICATION']->AddHeadString($html, true);
});
Alternatively, use the standard bitrix:metrika component—it's in the fileman module and is installed from the Marketplace. However, our approach via OnBeforeProlog is more reliable: it guarantees loading before any other script. The table below compares the two methods.
| Parameter |
Via init.php (our approach) |
Via bitrix:metrika component |
| Load control |
Full—code inserted before ob_start |
Depends on template, may load after jQuery |
| CSP compatibility |
Manually configured in init.php |
Requires component modification |
| AJAX support |
Additional handler needed |
Additional handler needed |
| Recommendation |
For projects with custom templates |
For typical installations |
What CSP settings are required for Webvisor?
Webvisor records the screen through an <iframe title="Embedded content"> on the domain webvisor.com. If the server (nginx or via PHP headers) has a strict CSP, recording won't start—the console will show an error Refused to frame ... because an ancestor violates the following Content Security Policy directive.
Minimum set of directives for Webvisor to work:
Content-Security-Policy:
frame-src 'self' https://webvisor.com;
script-src 'self' 'unsafe-inline' https://mc.yandex.ru https://cdn.jsdelivr.net;
img-src 'self' data: https://mc.yandex.ru;
In Bitrix, headers can be set in /bitrix/.htaccess or in init.php via header()—but only before the first HTML output. If you use ob_start() in the prolog, this is not a problem. Read more about CSP directives on MDN.
What to do if Webvisor doesn't see AJAX transitions?
Most modern Bitrix templates use AJAX navigation (BX.ajax, bitrix:main.ajaxlinks component). When transitioning without page reload, Webvisor doesn't record the URL change—the entire visit appears as a single page in the session recording.
Solution: call ym(XXXXXXXX, 'hit', window.location.href) after each AJAX transition. In Bitrix, there is an event BX.addCustomEvent('onAjaxSuccess', ...)—hook into it:
BX.addCustomEvent('onAjaxSuccess', function(event) {
if (typeof ym !== 'undefined') {
ym(XXXXXXXX, 'hit', window.location.href);
}
});
Without this, Webvisor data will be incorrect: all catalog transitions will be recorded as a single visit to the entry page. Our experience shows this problem occurs in 70% of sites with AJAX navigation.
We once configured Webvisor for an online store with a catalog of 100,000 products. The issue was that AJAX transitions did not trigger ym('hit'), and Webvisor showed only 1 page per session. After implementing the handler, recording captured up to 15 pages per visit—giving a complete picture of user behavior.
How to verify Webvisor is working?
After setup, check the 'Monitoring' section in Webvisor. If sessions are recorded but the video is black, the problem is mixed content (HTTP resources on an HTTPS site). If no sessions appear at all, look at the Network tab in DevTools for requests to mc.yandex.ru/watch/: a 200 status means the counter is working but data hasn't been processed yet (delay up to 20 minutes for new sessions).
What's included in turnkey Webvisor setup
We offer comprehensive setup that includes:
| Stage |
Action |
Result |
| 1. Audit |
Check current Metrica tag, CSP, AJAX navigation |
Report with errors and recommendations |
| 2. Implementation |
Install counter in init.php, configure CSP, AJAX handler |
Working Webvisor with correct recording |
| 3. Testing |
Verify in monitoring, record a test session |
Confirmation of correctness |
| 4. Documentation |
Description of work done, configs, support instructions |
Architectural note |
We guarantee that after our work, Webvisor will record 100% of sessions (barring browser blocking). Thanks to 10+ years of experience and hundreds of implemented projects, we know all the pitfalls. If you're facing issues, get a free consultation. Contact us to estimate your project timeline. Order turnkey Webvisor setup—we'll fix session recording issues in 2-3 days.
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.
