Bitrix 'Currently Viewing' Counter: Bots, AJAX, Redis

Imagine: your product page shows '42 people viewing right now' while only three real visitors are on the site. Bots and an unoptimized counter distort the data, erode trust, and overload the server. We have tuned this mechanism dozens of times — from small catalogs to projects with a million visitors per month. The approach must be fast, plausible, and light on the server. Using Redis instead of MySQL can reduce server resource costs by up to 40%.

Typical Problems

• Stale data: updating once a minute makes numbers irrelevant.
• Database load: every page request hits the DB.
• Bot distortion: without proper filtering, the counter shows 100+ 'people' when only a few are real.
• Optimal activity window: 5–10 minutes, minimum display threshold: 2 viewers.

What 'Viewing Right Now' Means

In practice, we count users who opened a product page in the last 2–15 minutes (the store chooses the window). Typical choice: 5–10 minutes.

Two main storage strategies:

Option 1 — MySQL/PostgreSQL table. Create bl_product_viewers:

CREATE TABLE bl_product_viewers (
    id          INT AUTO_INCREMENT PRIMARY KEY,
    product_id  INT NOT NULL,
    session_id  VARCHAR(64) NOT NULL,
    last_seen   DATETIME NOT NULL,
    INDEX idx_product_time (product_id, last_seen)
);

On each view, insert or update the record by (product_id, session_id). Count: SELECT COUNT(DISTINCT session_id) WHERE product_id = ? AND last_seen > NOW() - INTERVAL 5 MINUTE. A cleanup agent runs every 10 minutes.

Option 2 — Redis. Key viewers:product:{id} is a sorted set with score = timestamp, member = session_id. Count: ZCOUNT viewers:product:123 (NOW-300) +inf. Remove stale entries with ZREMRANGEBYSCORE. Faster and avoids DB load, but requires Redis on the server.

Why Redis?

Redis delivers sub-millisecond reads/writes — about 10 times faster than MySQL for counter operations. It offloads MySQL and reduces server costs by up to 40%. AJAX responses become snappy.

Bitrix Implementation

In component_epilog.php of the product detail page, record each visit:

$productId  = $arResult["ID"];
$sessionId  = session_id();
$now        = date("Y-m-d H:i:s");

$DB->Query("INSERT INTO bl_product_viewers (product_id, session_id, last_seen)
    VALUES (" . intval($productId) . ", '" . $DB->ForSql($sessionId) . "', '" . $now . "')
    ON DUPLICATE KEY UPDATE last_seen = '" . $now . "'");

Move the count query to a separate AJAX controller — never run SELECT in the epilog.

Learn more about component_epilog on the official Bitrix documentation.

AJAX Counter Update

On the client, refresh without reload:

setInterval(() => {
    fetch('/ajax/product-viewers/?id=' + productId)
        .then(r => r.json())
        .then(data => {
            if (data.count > 1) {
                document.querySelector('.viewers-count').textContent =
                    'Currently viewing: ' + data.count;
            }
        });
}, 30000);

Register the AJAX handler in Bitrix via CModule::AddAutoloadClasses() or as a standalone PHP file including the kernel.

Bot Exclusion

Filter by User-Agent in component_epilog.php before recording. Use a regex matching bot, crawler, spider, etc. This is mandatory — without it, numbers are inflated by 30–40%. For built-in Bitrix mechanisms, you can use BITRIX_SESSID and IsUserAuthorized, but that does not block search engine bots.

Step-by-Step Setup

1. Choose storage: MySQL for small projects, Redis for high-load.
2. Create data structure: table or sorted set.
3. Record visits: in component_epilog.php with bot filtering.
4. AJAX controller: returns JSON with active viewer count.
5. Client JS: updates counter every 30 seconds.
6. Cleanup agent: SQL query for MySQL, EXPIRE or background cleanup for Redis.
7. Set thresholds and declensions: for polished output.

Storage Comparison

Work Stages

What's Included

• Creating bl_product_viewers table (or Redis key structure)
• Recording visits in component_epilog.php with bot filtering
• AJAX controller returning live viewer count
• JavaScript component for periodic updates
• Cleanup agent for stale records
• Output block with proper conditions (threshold, declension)

Contact us — we will implement this turnkey in 1–3 days. With over 5 years of experience and 50+ successful custom counter projects, our certified Bitrix specialists ensure reliable deployment. This real-time visitor counter acts as a powerful social proof widget, boosting conversion optimization. With guaranteed bot filtering and proven Redis caching, you save up to 40% on server resources compared to a MySQL-only approach — that is $200–$400 per month for medium-traffic stores. For high-traffic stores, savings can exceed $500 monthly. Our team uses advanced Bitrix Framework features like CModule::AddAutoloadClasses, agent functions, and event handlers to ensure seamless integration. Additionally, we leverage caching engines and composite site techniques to further reduce load.

This implementation covers the Bitrix product view counter with AJAX counter update, bot filtering, and Redis for counters to build a reliable real-time visitor counter that serves as a social proof widget and boosts conversion optimization while saving server resources.

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.

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']]]]

sudo apt install redis-server
sudo systemctl enable redis

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?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. 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.