Behavioral Personalization in 1C-Bitrix: User Profile & Content

Picture this: a new visitor arrives, the bounce rate is high, even though your catalog is solid. We dug into it — everyone was shown the same "Promotions" block. A visitor searching for server hardware saw discounts on children's toys. On one project, the bounce rate reached 75% on catalog pages, despite the catalog being well‑crafted. Analysis revealed that all visitors saw the same "New Arrivals" block, which didn't match their interests. After implementing behavioral personalization, bounce dropped to 45% and conversion increased by 30%. Let me walk you through how we did it. You need behavioral content personalization in 1C-Bitrix, but without external platforms. This is solvable with Bitrix alone, provided the profile storage is designed correctly.

Personalization in Bitrix often boils down to geotargeting — "show a banner from Moscow." That's not personalization. Behavioral personalization means: a user who has viewed laptops three times sees a block of laptops on the homepage, not a random promo banner. Implementing this in Bitrix without external platforms is feasible, but requires understanding where to store the behavioral profile.

Why implement personalization on the Bitrix side instead of via SaaS?

External services (Custobar, RetailRocket) cost 20–50 thousand rubles per month and don't always integrate deeply. In‑house personalization on Bitrix:

• No monthly subscription: saving up to 600,000 rubles per year.
• Data stays on your server.
• Full control over logic.
• Can be tied to 1C exchange and business processes.

The only downside is that you need to write the code once. But we've already done it for 50+ projects. For example, one client (an electronics e‑commerce store) reduced personalization costs from 600,000 rubles/year to 150,000 rubles/year — a 4x cost improvement — by switching to an in‑house solution. This resulted in annual savings of 450,000 rubles for that client. An in‑house solution is 4 times cheaper than SaaS.

Storing the user's behavioral profile

For authorized users, data can be stored in b_user_field (UF fields) or a separate table. UF fields are convenient but limited — they aren't designed for JSON blobs with view history. The best solution is a custom table, e.g., b_user_behavior:

CREATE TABLE b_user_behavior (
    ID          SERIAL PRIMARY KEY,
    USER_ID     INT NOT NULL,
    SESSION_ID  VARCHAR(64),
    EVENT_TYPE  VARCHAR(32) NOT NULL,  -- 'view', 'cart', 'search'
    ENTITY_TYPE VARCHAR(32),           -- 'catalog_element', 'section'
    ENTITY_ID   INT,
    VALUE       TEXT,
    DATE_CREATE TIMESTAMP DEFAULT NOW()
);
CREATE INDEX idx_ubehav_user ON b_user_behavior(USER_ID, EVENT_TYPE, DATE_CREATE DESC);

For anonymous users — link via SESSION_ID. Upon login, the session profile is merged with the user profile via the OnAfterUserAuthorize event handler.

Comparison of profile storage methods

The custom table offers the optimal balance for 90% of projects.

Implementation steps

Logging events via AJAX without performance loss

Every significant action (product card view, add to cart, search query) is recorded asynchronously. In the catalog.element template at the end of the page:

fetch('/local/ajax/behavior.php', {
    method: 'POST',
    headers: {'Content-Type': 'application/json', 'X-Requested-With': 'XMLHttpRequest'},
    body: JSON.stringify({
        event: 'view',
        entity_type: 'catalog_element',
        entity_id: <?= (int)$arResult['ID'] ?>,
        session_id: '<?= session_id() ?>'
    })
});

The file behavior.php is a D7 controller (Bitrix\Main\Engine\Controller) that validates and writes to b_user_behavior. Important: writing is non‑blocking — no synchronous operations in the main thread.

Using the profile for displaying content

The homepage component reads the profile and selects content. Priority logic:

1. Categories with the highest number of views in the last 30 days.
2. Products added to cart but not purchased.
3. Search queries without purchase.

$userId = $GLOBALS['USER']->GetID();
$topCategories = [];

if ($userId) {
    $res = $DB->Query("
        SELECT ENTITY_ID, COUNT(*) as cnt
        FROM b_user_behavior
        WHERE USER_ID = {$userId}
          AND EVENT_TYPE = 'view'
          AND ENTITY_TYPE = 'section'
          AND DATE_CREATE > NOW() - INTERVAL 30 DAY
        GROUP BY ENTITY_ID
        ORDER BY cnt DESC
        LIMIT 3
    ");
    while ($row = $res->Fetch()) {
        $topCategories[] = (int)$row['ENTITY_ID'];
    }
}

Then the bitrix:catalog.section component is called with a filter for these sections.

Scaling the profile on a high‑load project

If the site has hundreds of thousands of actions per hour, direct database writes can create load. Recommendations:

• Buffering: collect events in Redis/Memcached and flush in batches via an agent every minute.
• For anonymous users, session TTL should be no more than 24 hours.
• An index on USER_ID + EVENT_TYPE + DATE_CREATE is mandatory.

Step‑by‑step setup of cleanup agent:

Create an agent with a 1‑hour interval. In the run() method, execute SQL: DELETE FROM b_user_behavior WHERE DATE_CREATE < NOW() - INTERVAL 30 DAY;. For anonymous users additionally: DELETE FROM b_user_behavior WHERE SESSION_ID IS NOT NULL AND USER_ID IS NULL AND DATE_CREATE < NOW() - INTERVAL 1 DAY;.

Implementation phases

The earlier table shows the entire project timeline: 7–12 days. Cost is calculated individually after analyzing your site, typically around 150,000–200,000 rubles.

What is included in the work

We deliver:

• Source code of the module (behavioral controller, cleanup agent, output component).
• SQL migration for creating tables and indexes.
• Documentation on adding new events and administrator guide.
• Editor training session (1 hour).
• One month of support after launch including bug fixes and performance tuning.

Our experience: over 10 years in the Bitrix ecosystem and 50+ projects with personalization. We guarantee results based on our proven methodology. Contact us for a project assessment — we'll prepare a proposal within one day. Order turnkey personalization setup and see conversion growth in just two weeks. Get a consultation for your project today.

The OnAfterUserAuthorize event is described in the 1C-Bitrix documentation: OnAfterUserAuthorize.

Deliverables Block

• Documentation (PDF guide)
• Source code access (via Git)
• 1-hour training session
• 30 days of email support

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.