We often encounter situations where Yandex.Direct automated strategies operate blindly due to incorrectly configured goals. Without proper conversion tracking from 1C-Bitrix, reports show zeros and budgets are wasted. With over 7 years of experience with Bitrix and Metrika, we guarantee precise setup that boosts conversion rates by 30–50% (average 35% increase within the first month). Correctly configured conversions provide Direct with enough data to train its optimization algorithms, saving up to 40% of the budget for the same sales volume—potentially over $10,000 annually on ad spend.
Metrika Counter and Goals: What Must Be in Place Before Direct Setup
Direct conversions rely on Metrika goals, so first—the counter. In Bitrix, the Metrika counter can be added in several ways: via the bitrix:main.counter module in the template, by direct insertion into header.php, or via OnEpilog.
For goals to work correctly, the counter must load before target events fire. Use synchronous initialization via ym(counterId, 'init', {...}) with the defer: false parameter on pages with forms. In practice, most sites overlook this: the counter loads asynchronously via defer, and fast users submit a form before Metrika initializes, causing conversion loss.
In the b_option table, it's convenient to store the counter ID: COption::SetOptionString("main", "ya_metrika_id", "XXXXXXXX"). Then, when changing the counter, you don't need to modify the template.
Goals in Metrika for e-commerce:
-
JavaScript goal
order_success — on the thank-you page after checkout (most important for Direct)
-
JavaScript goal
add_to_cart — when an item is added to the cart
-
Composite goal with steps: catalog view → product card → cart → checkout
How to Avoid Duplicate Goals on Page Reload?
When the thank-you page reloads, the goal should not be triggered again. We use a session flag: after the first ym reachGoal call, we set $_SESSION['conversion_sent'] = true and check it before sending. In the bitrix:sale.order.ajax component, this is implemented in template.php.
Passing Goal Achievement from Bitrix
The order_success goal is the most important for Direct. The call:
ym(COUNTER_ID, 'reachGoal', 'order_success', {
order_price: 4900,
currency: 'RUB'
});
In Bitrix, the "Thank you" page is either a separate page /personal/order/success/ or the final step of the bitrix:sale.order.ajax component. In both cases, ensure the JS call does not duplicate—when the page reloads, the goal should not be triggered again.
A reliable method: in the bitrix:sale.order.ajax component's template.php, find the block with the condition for successful order creation ($arResult["NEED_PAY"] || $arResult["ORDER_ID"]) and add the Metrika call only there. Take order parameters (order_price) from $arResult["ORDER"]["PRICE"].
For the page /personal/order/success/ — the bitrix:sale.order.detail component provides access to order details via $arResult. Order ID from URL parameter + CSaleOrder::GetByID($orderId).
Step-by-Step Setup Guide
- Install and configure the Metrika counter with proper synchronous initialization.
- Create the
order_success JavaScript goal in Metrika.
- Implement the
ym reachGoal call on the thank-you page, ensuring no duplicate tracking.
- For offline conversions, save the
client_id from the _ym_uid cookie into the order property upon checkout.
- Set up an API call to upload conversions when order status changes to "Completed".
- In Yandex.Direct, create a strategy optimized for the
order_success goal.
- Monitor performance and adjust bids as needed.
Why Offline Conversions Are Critical for E-commerce?
If some orders are handled by managers (phone calls, inquiries without online payment), the standard JS pixel is insufficient. Yandex.Metrika supports uploading offline conversions via API. In practice, API-driven offline conversions are 2 times more accurate than automatic CRM uploads (accuracy difference up to 15%). This ensures offline orders are attributed correctly, improving Direct's optimization data.
Offline Conversions via Metrika API
In Bitrix, this is implemented via the OnSaleOrderStatusUpdate event. When a manager changes the order status to "Completed," send a POST request to https://api-metrika.yandex.net/management/v1/counter/{counterId}/uploads/client_id:
AddEventHandler("sale", "OnSaleOrderStatusUpdate", function($id, $arFields) {
if ($arFields["STATUS_ID"] === "F") { // Finished
// Получаем client_id из b_sale_order_props или пользователя
$httpClient = new \Bitrix\Main\Web\HttpClient();
$httpClient->post($apiUrl, $csvData);
}
});
The Metrika client_id must be saved when placing the order—it comes from the _ym_uid cookie or from the JavaScript method ym(id, 'getClientID', callback). Save it in the order property (b_sale_order_props_value) upon creation.
| Conversion Method |
Accuracy |
Implementation Complexity |
| JS pixel |
High (online only) |
Low |
| API offline |
High (all channels) |
Medium |
| Automatic CRM upload |
Medium |
High |
Structure of client_id
`client_id` is a 64-bit integer stored in the `_ym_uid` cookie in Metrika responses. It can be obtained via the JavaScript method `ym(id, 'getClientID', callback)` or directly from the cookie. For reliability, use `getClientID` in the `onload` event.
Integration with Direct: Automated Strategies
After goals are working and conversions are recorded, switch your Direct strategy to "Conversion Optimization" with the order_success goal. Direct requires at least 10 conversions in the last 28 days for training—this is important to consider when launching.
The Bitrix sale module under typical load does not create delays for Metrika calls. However, if the site has aggressive caching via BXCache with TTL > 3600, verify that the thank-you page is not cached—the bitrix:sale.order.ajax component has CACHE_TYPE = 'N' by default, but custom templates may break this.
What's Included in the Conversion Setup Work
- Audit of current Metrika counter and goal configuration
- Install counter with correct initialization
- Set up JavaScript goals for e-commerce
- Integrate offline conversions via API with client_id saving
- Test all scenarios (online payment, phone calls, inquiries)
- Documentation for usage and support
Contact us for an audit of your current setup—we'll identify bottlenecks and improve Direct effectiveness. Order a turnkey conversion setup: from counter to bid optimization. Get a consultation on implementing offline conversions.Yandex.Metrika API for Offline Conversions
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.
