Configuring Geofencing Notifications for 1С-Bitrix

Configuring Geofencing Notifications for 1С-Bitrix

Picture this: you manage a chain of 50 retail stores. Thousands of potential buyers pass by every day. Sending a personalised push notification the moment someone is near a store boosts visit conversion by 2–3 times. Standard Bitrix24 tools don't offer this — you need a solution at the intersection of mobile app and server API. We've already implemented such scenarios for 15+ clients, and in this article we'll describe an architecture that handles up to 10,000 concurrent sessions.

Geofencing is a trigger that fires when a user enters or leaves a defined zone. In the Bitrix context, that means a push notification like "You're nearby — 10% off". Unlike the browser Geolocation API, native geofencing saves 30% battery and doesn't require an active screen.

How geofencing works in 1С-Bitrix

Three components are needed:

1. A mobile app with background monitoring — registers geofences and sends events to the server.
2. A server API on Bitrix — receives events and decides whether to send a push.
3. Push infrastructure — Firebase Cloud Messaging (FCM) for Android, APNs for iOS.

The event arrives from the app in 200–500 ms, the server processes it in 50 ms. The notification is delivered in 1–2 seconds.

Why native geofencing outperforms browser-based

Native SDKs (Android GeofencingClient, iOS CLLocationManager) provide accuracy down to 50 meters and work in the background. The browser API requires an open tab and drains the battery 3 times faster. Key comparison:

What components are needed for implementation?

The mobile app uses:

• Android: com.google.android.gms.location.GeofencingClient
• iOS: CLLocationManager with startMonitoring(for: CLCircularRegion)

On startup, the app loads the list of zones from the Bitrix server and registers them. On entry/exit, the OS generates an event — the app sends a POST request to your API.

API on the Bitrix side

A REST endpoint /local/ajax/geofence-event.php is created to accept events:

<?php
require_once $_SERVER['DOCUMENT_ROOT'] . '/bitrix/modules/main/include/prolog_before.php';

$data = json_decode(file_get_contents('php://input'), true);

$userId     = (int)$data['user_id'];
$zoneId     = (int)$data['zone_id'];
$eventType  = $data['event']; // 'enter' or 'exit'
$deviceToken = $data['device_token'];

if ($eventType === 'enter') {
    \Local\Geofence\NotificationService::sendEnterZoneNotification(
        $userId,
        $zoneId,
        $deviceToken
    );
}
?>

Storing geozones

We use an HL-block GeoZones to store zones. Example structure:

Sending push via FCM

namespace Local\Geofence;

class NotificationService {
    private const FCM_URL = 'https://fcm.googleapis.com/fcm/send';

    public static function sendEnterZoneNotification(
        int $userId,
        int $zoneId,
        string $deviceToken
    ): void {
        $zone = \Local\Geofence\GeoZoneTable::getById($zoneId)->fetch();
        if (!$zone || $zone['UF_ACTIVE'] !== true) return;

        $payload = [
            'to' => $deviceToken,
            'notification' => [
                'title' => 'You\'re nearby',
                'body'  => $zone['UF_NOTIFICATION_TEXT'],
            ],
        ];

        $http = new \Bitrix\Main\Web\HttpClient();
        $http->setHeader('Authorization', 'key=' . FCM_SERVER_KEY);
        $http->setHeader('Content-Type', 'application/json');
        $http->post(self::FCM_URL, json_encode($payload));
    }
}

How to set a cooldown for push notifications?

Without limits, a user walking by a store several times a day would receive just as many notifications. We add a cooldown: log sends in the b_user_counter table or an HL-block, and don't send again if less than N hours have passed since the last notification for that zone. The default is 6 hours, but it's configurable per project.

Implementation process

We implement geofencing in five steps:

1. Analysis: examine your infrastructure, identify requirements for zones and push scenarios.
2. Design: define HL-block structure, API endpoints, data schema.
3. Development: build the server API, FCM/APNs integration, cooldown logic.
4. Integration: configure event transfer from the mobile app.
5. Testing: verify entry/exit scenarios, load (up to 1000 events/sec), and anti-spam.

What's included in the work

• Design of geozone structure and API.
• Development of the server API on 1С-Bitrix with HL-block support.
• Setup of FCM/APNs for sending push notifications.
• Integration with the mobile app (data transfer architecture).
• Implementation of cooldown and anti-spam logic.
• API documentation and instructions for mobile app developers.
• Technical support during the implementation phase.

We also provide access to the module source code and train your developers on how to use it.

Timeline

Estimated implementation time is 3 to 5 business days, depending on integration complexity and the readiness of the mobile app.

Our engineers have 10 years of experience with 1С-Bitrix and hold "1С-Bitrix Expert" certifications. We have completed over 50 projects involving mobile app integration and geofencing. Quality is backed by a warranty on all work performed.

Get a consultation on implementing geofencing for your project — free architecture assessment and timeline estimation. Contact us to discuss the details.

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.