Dynamic Retargeting in Yandex.Direct for Bitrix

Dynamic retargeting in Yandex.Direct enhances ad performance, but configuring it on Bitrix often causes trouble. A typical situation: product cards don't load in smart banners, even though the feed and metric are set up. The reason is a mismatch of the product ID in the YML feed and dataLayer. We help avoid such errors and set everything up turnkey. Our approach includes an audit of the current state, code modifications, and testing. As a result, you get CTR growth of up to 40% and a reduction in abandoned carts of 15–20%. Dynamic retargeting is 2–3 times better than standard retargeting in terms of CTR because it shows the user exactly the products they viewed.

Why Is a Unified Product ID Important?

Yandex matches the product feed with view data using the ID. If the feed has <offer id="123"> but dataLayer passes id: "456", retargeting won't work. We use the information block element ID ($arResult['ID']) in both places. In rare cases, stores use an article number—then the identifier must be identical everywhere. ID mismatch causes 70% of smart banner issues.

How Does the YML Feed Affect Retargeting?

Configure the export via "Store → Product Export → Yandex.Market". In the feed parameters, specify:

More details on the YML format can be found in the official Bitrix documentation.

How to Pass Events to Yandex.Metrica?

For retargeting to work, you need to enable e-commerce in the Metrica counter (ecommerce: true) and pass events to dataLayer. Example for a product view (in the catalog.element template):

window.dataLayer = window.dataLayer || [];
dataLayer.push({
    ecommerce: {
        detail: {
            products: [{
                id: '<?= $arResult['ID'] ?>',
                name: '<?= CUtil::JSEscape($arResult['NAME']) ?>',
                price: <?= $arResult['CATALOG_PRICE_1']['PRICE'] ?? 0 ?>,
                category: '<?= $sectionName ?>'
            }]
        }
    }
});

Events add (add to cart) and purchase are passed similarly. Bitrix has built-in integration with Yandex.Metrica—enable it in the web analytics settings. Some events (e.g., order) will be passed automatically via the bitrix:sale.checkout component. Verify that data reaches through the "Webvisor" report—it's the only way to ensure correctness.

How to Create Retargeting Segments?

Once data appears in Metrica (at least 1000 visitors over 28 days), create segments in Yandex.Audiences:

• Viewed product, didn't buy — condition: detail event within 90 days, exclude those who reached the "Purchase" goal.
• Added to cart, didn't buy — add event, without the "Purchase" goal.
• Purchased — "Purchase" goal—use to exclude from retargeting.

In Direct, create a "Smart Banners" campaign, connect the product feed and segments. Yandex will automatically select relevant cards.

Steps to Set Up a Smart Banner Campaign

1. Create a YML product feed and ensure it's accessible via URL.
2. Enable e-commerce in the Yandex.Metrica counter.
3. Add the dataLayer code to the catalog, cart, and checkout templates.
4. Wait for statistics to accumulate (at least 1000 visitors over 28 days).
5. Create segments in Yandex.Audiences.
6. Launch a "Smart Banners" campaign in Yandex.Direct, attaching the feed and segments.

Order a full cycle of setup from audit to launch. Our engineers guarantee correct operation. Setup starts at $500, and typical monthly savings on wasted ad spend exceed $200.

What's Included in Our Setup

• YML feed: configure export with correct fields, update agent, publication.
• Metrica counter: enable e-commerce, install on all pages.
• DataLayer: add detail, add, purchase events to catalog and cart templates.
• Segments: create three targeted segments in Yandex.Audiences.
• Campaign: create smart banners with feed and segment linkage, initial bids.
• Testing: verify correct display of cards and statistics.
• Documentation: description of all changes, identifier mapping, update recommendations.

We have configured dynamic retargeting for 50+ online stores on Bitrix. The average CTR increase for smart banners is 40%, and the percentage of abandoned carts decreases by 15–20%.

Common Errors and Solutions

• ID mismatch: check that the feed and dataLayer use the same identifier. Most often it's the information block element ID.
• Slow feed: enable caching of the YML file using Bitrix\Main\Data\Cache. Update every 4 hours.
• Empty segment: ensure events reach Metrica through the "Webvisor" report. If dataLayer isn't filling, check the JavaScript syntax.
• Smart banners not showing: verify the campaign is active, geotargeting is set, and feed is attached.

Contact us for a project assessment—we'll analyze the current state within one day. Get a consultation and an accurate proposal for dynamic retargeting setup.

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.