How to Set Up Retargeting on 1C-Bitrix: Complete Guide
A visitor lands on a product page, adds an item to the cart, and leaves. Without retargeting, you lose up to 98% of traffic—only 2% return on their own. Technically, the challenge is to correctly pass e-commerce events to advertising pixels. Each platform (Yandex.Metrica, Google Ads, Meta Pixel) requires its own data format. We configure retargeting for your catalog, accounting for the specifics of information blocks and trade offers. Over 8 years, we have completed more than 120 projects—from Bitrix online stores to corporate portals with Bitrix24. Typical project cost ranges from $500 to $2,000, depending on complexity.
Why Passing the Purchase Event Matters
The Purchase event is key for optimizing ad campaigns. Without it, advertising platforms cannot see which products a user bought and cannot correctly train their models. In Bitrix, this event is triggered from the sale.order.ajax component after a successful order. Ensure that the product IDs in the feed match the order_id and product_id in the events—otherwise audiences won’t generate. Dynamic remarketing with a product feed yields 3 times more conversions compared to standard retargeting. We recommend also passing InitiateCheckout to further improve optimization.
Which Events We Pass
Retargeting platforms work with audiences segmented by actions. The minimum set of events:
| Event |
Trigger |
Data Transferred |
| PageView |
Every page |
URL, title |
| ViewContent |
Product page |
product_id, name, price, category |
| AddToCart |
Add to cart |
product_id, quantity, price |
| InitiateCheckout |
Checkout start |
cart total, items count |
| Purchase |
Order completed |
order_id, total, products[] |
The more events, the more precise the segmentation. But to start, ViewContent, AddToCart, and Purchase are sufficient. Adding each extra event improves segmentation by 15-20%.
Pixel Installation
Yandex.Metrica + Yandex.Audiences. The Metrica counter is already on most sites. For retargeting:
- Enable E-commerce in the counter settings. The data container name is
dataLayer (default).
- Pass events via
dataLayer.push() in JavaScript. Bitrix natively supports Google Enhanced Ecommerce via the sale.order.ajax component, but Yandex requires its own format.
ViewContent event for Yandex:
window.dataLayer.push({
ecommerce: {
detail: {
products: [{
id: "<?= $arResult['ID'] ?>",
name: "<?= CUtil::JSEscape($arResult['NAME']) ?>",
price: <?= $arResult['MIN_PRICE']['DISCOUNT_VALUE'] ?>,
category: "<?= CUtil::JSEscape($arResult['SECTION']['NAME']) ?>"
}]
}
}
});
Place this in the catalog.element component template—in template.php or a linked JS file.
Google Ads (gtag.js). Install the Google Tag pixel via gtag('config', 'AW-XXXXXXXXX'). For retargeting, page_view is sent automatically; e-commerce events are passed via gtag('event', 'view_item', {...}).
Bitrix has a built-in Google Enhanced Ecommerce setting in the catalog module (Settings → Product Settings → Catalog → E-commerce). When enabled, catalog and cart components automatically generate dataLayer in GA4 format. If you use gtag.js (not GTM), data is picked up automatically.
Meta Pixel (Facebook/Instagram). Add the pixel code to <head> via the site template's header.php or through Google Tag Manager. Events:
fbq('track', 'ViewContent', {
content_ids: ['<?= $arResult['ID'] ?>'],
content_type: 'product',
value: <?= $arResult['MIN_PRICE']['DISCOUNT_VALUE'] ?>,
currency: 'RUB'
});
VK Pixel. Similarly: VK.Retargeting.ProductEvent(PRICE_LIST_ID, 'view_product', {products: [{id: '...', price: ...}]}).
The AddToCart Nuance in Bitrix
Adding to cart in Bitrix usually happens via an AJAX request to basket.php or through the catalog.element component. The JavaScript event must be triggered in the callback after a successful add. Intercept the standard Bitrix event:
BX.addCustomEvent('OnBasketChange', function() {
// Get the last added product from the response
dataLayer.push({
event: 'add_to_cart',
ecommerce: { add: { products: [/*...*/] } }
});
});
If custom AJAX is used, wrap the callback manually.
How to Avoid Product ID Mismatch
Product IDs in events, feeds, and 1C must match. In Bitrix, create a single ID reference (e.g., catalog_product.id) and use it in all integrations. Ensure that the feed export does not trim leading zeros. Use the standard XML export via CommerceML documentation or a custom script. A unified ID guarantees that 80% of clients return after setup.
Dynamic Remarketing: Product Feed
To show specific products in ads (dynamic retargeting), ad platforms require a product feed—XML/CSV with your catalog. The product ID in the feed must match the content_ids / product_id in the site events.
Bitrix generates feeds via Marketing → Export to Google Merchants / Yandex.Market. For Facebook and VK, custom export or adaptation of the standard one is required. The key is a unified product ID everywhere. Customer acquisition cost drops by 25% after feed implementation.
Google Tag Manager as an Alternative
Instead of inserting pixel codes directly into templates, we recommend using GTM. Bitrix generates dataLayer, and GTM routes data to all platforms (Google Ads, Yandex, Meta, VK) without modifying site code. Adding a new ad channel requires just one tag in GTM, with no development effort. GTM cuts integration time by half compared to manual insertion.
| Approach |
Integration Time |
Flexibility |
Maintenance Complexity |
| Manual insertion |
2-3 days |
Low |
High |
| Google Tag Manager |
1 day |
High |
Low |
How to Verify Correct Event Transmission
Use browser extensions: Yandex Tag Assistant, Facebook Pixel Helper, Google Tag Assistant. They show which events and parameters are sent with each action on your site. Regular checking after every code change ensures stable retargeting.
What Is Included in a One-Day Setup
- Pixel installation (Yandex + one ad channel) in the template.
- Passing ViewContent, AddToCart, Purchase via
dataLayer.
- Event verification using debuggers (Yandex Tag Assistant, Facebook Pixel Helper, Google Tag Assistant).
- Configuring a retargeting audience in the ad account.
Event Check-List
- Ensure dataLayer is defined on the page.
- Check PageView event on all pages.
- Perform a test product page view—ViewContent should appear.
- Add a product to cart—check AddToCart.
- Place a test order—ensure Purchase appears.
- Cross-check product IDs in events and feed.
What Our Work Includes
We provide documentation of event configuration, test every step, conduct one training session (30 min), and offer support for 2 weeks after launch. We guarantee correct event transmission on all catalog pages. Deliverables include:
- Detailed setup documentation with screenshots
- Access to test environment during setup
- One 30-minute training session for your team
- 2 weeks of post-launch support via email/chat
Order retargeting setup now—receive a free project assessment within 24 hours and launch within 2 days. Get a consultation—our engineers will help with any questions.
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.
