VK Product Ads on Bitrix: Integration and Setup

A catalog of 50,000 products generates a YML file in 15 minutes — the server crashes, ads don't launch. A typical situation for online stores on 1C-Bitrix. We rewrote queries with tagged caching and agents — generation time reduced by 7.5 times, to 2 minutes. Ads launched first time. Clients save up to 30% budget due to up-to-date prices and product availability. On one project, after implementing the server-side API, conversion increased by 25% and cost per lead decreased by 18%. Proper integration allows VK to segment audiences more accurately and reduce cost per click by 15–20%.

According to VK Ads documentation, for correct operation of dynamic ads, transmitting the purchase event via server-side API is mandatory.

How to Export a Product Feed for VK

VK accepts feeds in YML (Yandex Market) format or its own JSON format. Bitrix has built-in export to YML via the catalog module: "Shop → Export goods → Yandex.Market". We use the same file for VK. Important: the YML should only contain products in stock with correct currencies. For proper display, all images must be in absolute URLs.

Configure the export:

• Select the information block and catalog sections.
• Enable image export — PICTURE in absolute URLs.
• OFFER_URL template — URL of the product detail page.
• Specify price types, currency, and delivery settings.

The feed is saved to a path (e.g. /upload/vk_feed.xml) and updated by an agent every 2–4 hours. In your VK Ads account, add the feed via URL https://your-site.ru/upload/vk_feed.xml. More about YML format in the CommerceML documentation.

Installing the VK Pixel

VK Pixel is a JavaScript code that tracks visitor actions. Obtain your pixel ID in "VK Ads → Audiences → Pixels".

Insert the pixel code into the site template. In Bitrix, this is done via "Settings → Product Settings → Analytics" or directly in the header.php file. Alternatively, use Google Tag Manager.

In the catalog.element component template, add JavaScript with VK.Goal calls and data from $arResult.

Which Events to Send to VK Pixel?

For retargeting and optimization, four events are sufficient: homepage view, product view, add to cart, purchase. Be sure to pass product ID and price. For purchase, also pass the total amount. This allows VK to build audiences like "viewed but not purchased" and "abandoned cart", and optimize bids for conversions.

Why Use Server-Side VK API?

The browser pixel is blocked by AdBlock and doesn't work for offline conversions. Server-side VK API (Conversions API) sends data from your server. When an order is paid, in the OnSaleOrderPaid handler, send a POST to https://api.vk.com/method/ads.checkRetargetingPixelDomain using \Bitrix\Main\Web\HttpClient.

Accuracy comparison:

Server-side VK API is 1.5 times more accurate than the browser pixel. Server-side sending is mandatory for accurate statistics under 54-FZ and for proper retargeting.

Typical Problems and Solutions

• Error in YML: images without absolute URLs — VK won't load product cards. Check PICTURE settings.
• Pixel doesn't fire: conflict with other scripts or incorrect pixel ID. Check browser console.
• Purchases not recorded: set up server-side API — browser pixel loses up to 30% of events.

// handler OnSaleOrderPaid
use Bitrix\Main\Web\HttpClient;

$http = new HttpClient();
$http->post('https://api.vk.com/method/ads.checkRetargetingPixelDomain', [
    'access_token' => 'TOKEN',
    'pixel_id' => 'PIXEL_ID',
    'events' => json_encode([[ 
        'event_name' => 'purchase',
        'event_time' => time(),
        'user_id' => $userId,
        'products' => $products,
        'value' => $total
    ]])
]);

Work Process

1. Audit — check current feed, catalog structure, pixel settings.
2. Design — choose export architecture considering catalog size (up to 100,000+ items).
3. Implementation — write custom agents, caching, event handlers.
4. Testing — verify on staging and live server, compare events.
5. Deployment and documentation — hand over instructions for the marketer.

What We Configure (Deliverables)

• Product export to YML with optimized queries and agent schedule.
• Install VK pixel code into site template.
• JavaScript events on product, cart, and success order pages.
• Server-side purchase event via Conversions API on OnSaleOrderPaid.
• Feed linking to VK ad account for dynamic ads.
• Setup documentation and marketer instructions.

Timeline and Cost

Basic setup takes 2 to 4 days. If custom fields, 1C integration, or large catalog (over 100,000 items) are needed, the timeline extends to 7 days. Cost is calculated individually after auditing your site.

Our team consists of certified specialists with 8+ years of Bitrix experience. We guarantee correct feed and pixel operation. Get a consultation — contact us. Contact us for an audit of your project.

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.