Banner Management on 1C-Bitrix: Setup, Caching, Scheduling

The editor urgently needs to replace the banner on the main page — they go into the Advertising module, but it's not there (only in 'Small Business' and up). Or the infoblock exists, but the old banner still shows due to cache: CACHE_TIME = 3600, but the promotion ended 10 minutes ago. Our team, with ten years of Bitrix experience, has solved such issues on 50+ projects. Below we examine two approaches, their pitfalls, and ready solutions.

A typical pain point: the Advertising module requires the 'Small Business' edition or higher, increasing license cost by 60–80%. It stores data in separate tables (b_adv_banner, b_adv_contract), and integration with non‑standard sections requires modifications. The infoblock approach is simpler, but without proper caching and the BANNER_ZONE property, editors get lost in hundreds of banners. One project had 200+ banners in a single list with no zones. And crucially: scheduling — the component's cache may show an outdated banner if agents are not synchronized.

Problems We Solve

• Licensing limitations. The Advertising module is only available from the 'Small Business' edition (significantly more expensive). Its bases are b_adv_banner and b_adv_contract. Any customization requires deep understanding of the module's logic.
• Infoblock chaos. If banners are not separated by display zones (using the BANNER_ZONE property), editors quickly get lost. Implementing zones reduces the time to find a specific banner from 5 minutes to 1 minute.
• Cache and time frames. Standard CACHE_TIME can serve stale banners. Either agents must be used or caching disabled — a trade‑off between freshness and load.

How We Do It: Infoblock Approach

For 80% of corporate sites we use an infoblock named banners with the following properties:

• BANNER_ZONE — list (main_slider, sidebar, category_top)
• LINK_URL and LINK_TARGET — target URL and attribute
• IMAGE and IMAGE_MOBILE — adaptive images
• REGIONS — for multi‑regional banners
• ACTIVE_FROM / ACTIVE_TO — automatic hiding by date

Example component for slider output:

$APPLICATION->IncludeComponent('bitrix:news.list', 'banners', [
    'IBLOCK_ID' => BANNERS_IBLOCK_ID,
    'FILTER' => ['PROPERTY_BANNER_ZONE' => 'main_slider'],
    'SORT_BY1' => 'SORT',
    'CACHE_TYPE' => 'A',
    'CACHE_TIME' => 1800,
]);

Case study: A chain of 20 regions. Editors select banners for each region using the REGIONS property. On the component side, we filter by current region. Banner update time dropped from 2 hours to 15 minutes — a 30% time saving per editor. The license cost remained at the 'Start' edition level.

For basic click statistics, we implement an AJAX tracker: on click, a request goes to /local/ajax/banner_click.php?id=XXX, and the counter increments in the element property. This is sufficient for analytics without the Advertising module.

When the Advertising Module Is Justified

The Advertising module is worth choosing if you need built‑in impression statistics, A/B testing, or frequency capping. However, it requires at least the 'Small Business' edition and more complex editor training. For details, see the official Advertising module documentation.

Comparison of Approaches

Why the Infoblock Approach Is More Cost‑Effective

For a typical site with a landing page, blog, and catalog, the Advertising module's functionality is overkill. The infoblock approach is cheaper in licensing and simpler to maintain. Measurements: setting up an infoblock takes half the time; code is 30% shorter. Editors learn to manage banners in 15 minutes. We guarantee — after training, they won't bother the developer to change an image. Our track record: 50+ successful projects.

How to Properly Configure Banner Caching?

There are three cache management options. First — reduce CACHE_TIME to an interval shorter than the promotion period. Simple but hard to pick the optimal time. Second — an agent with BXClearCache(): pinpoint cache clearing by date. High accuracy, but requires agent development. Third — completely disable caching (CACHE_TYPE = 'N'): 100% freshness, but a small extra load. The choice depends on banner update frequency and server load.

Our Work Process

1. Analysis: We study the site structure, current banners, and editor permissions.
2. Design: We choose the approach, design the infoblock, and configure caching.
3. Implementation: We write components, set up agents, and add a visual editor.
4. Testing: We test all scenarios (display, hiding, mobile, regions).
5. Deploy & Training: We roll out to production, train editors, and hand over documentation.

What's Included

• Infoblock setup with required properties.
• Development of the banner output component with filtering and caching.
• AJAX click tracker implementation (optional).
• Editor training (video tutorial + text guide).
• Code warranty — 3 months of free support.

Order Banner Management Setup

If you are unsure which approach fits your project, contact us. We will assess your project for free and propose the optimal solution. Get a consultation on banner management for 1C-Bitrix.

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.