How to Integrate CDP with 1C-Bitrix: Step-by-Step

Introduction

If a marketer cannot answer how many buyers purchased from the Electronics category twice in the last 90 days — customer data exists, but a CDP does not. Information is scattered: sessions in Bitrix, orders in 1C, inquiries in Bitrix24 CRM, events in Yandex.Metrica. A CDP collects this into a unified customer profile and makes the data usable for customer segmentation and site personalization. Our team has over 10 years of web development experience, and we guarantee transparency at every stage. The result is personalized scenarios that boost conversion 3–5 times, based on our practice our practice. For example, one client saved $5,000 per month in ad spend after implementing CDP-driven segmentation. Integration costs start from $3,000 and typically pay back within 2 months.

Data Collection Methods

How Data Gets into CDP from 1C-Bitrix

Setting up CDP for a 1C-Bitrix site solves three tasks: collecting data from all touchpoints, merging profiles (one person — one profile despite different devices and channels), and activation — using data for site personalization and email campaigns.

Data sources for a Bitrix project:

• Site: browser events (page views, clicks, cart additions) — via JavaScript SDK of the CDP
• Orders: data from the sale module — via webhooks or a Bitrix agent
• Profiles: user data from b_user, b_sale_order_user — via CDP API
• CRM Bitrix24: deals, contacts — via Bitrix24 REST API
• Email campaigns: opens, clicks from ESP (UniSender, SendPulse) — via ESP webhooks

Event tracking via JavaScript SDK captures user actions, while server-side tracking ensures delivery for critical events like order creation. CDP also processes e-commerce data from orders and cart events to enable abandoned cart campaigns.

Why Server-Side Tracking Matters for Bitrix

JavaScript SDK is a simple data collection method, but it is unreliable: ad blockers cut up to 30% of events, and offline actions (phone orders, returns) are not captured. Server-side tracking duplicates critical events (order placement, registration) directly from the Bitrix core, ensuring delivery even when JS is disabled. We combine both approaches to achieve 99% coverage. The combined approach is 6x more effective than SDK-only for abandoned cart recovery.

Comparison of Integration Methods

The combined approach pays off within 2 months due to segment accuracy. Confirmed in practice: after implementing server-side tracking, one client increased revenue from abandoned carts by 40%. client case This translates to an average of $2,000 extra revenue per month.

Implementation Guide

Data Source to CDP Event Mapping

Step-by-Step CDP Setup Plan for Bitrix

1. Audit current data — identify sources: site, CRM, 1C, email. Map event structure.
2. Connect JavaScript SDK — install the script via template, configure tracking of views, carts, orders.
3. Set up server-side events — write handlers for critical events in init.php.
4. Integrate with CRM — synchronize Bitrix24 deals and contacts via REST API.
5. Identify anonymous users — configure identify() after authentication.
6. Test and launch — verify end-to-end data flow with test orders.
7. Personalization — connect CDP API for dynamic content changes and segments in email campaigns.

Profile Unification: Technical Complexity

The main engineering challenge of CDP is profile unification. A user arrives anonymously from a phone, adds to cart, leaves. The next day, opens an email from a campaign, clicks a link, places an order from a desktop. This is one person, but three different identifiers: anonymous_id from the browser, email from the email, user_id after authentication.

CDP solves this with an identify call upon authentication:

// after successful login
analytics.identify('{{ USER_ID }}', {
    email: '{{ USER_EMAIL }}',
    name: '{{ USER_NAME }}',
    phone: '{{ USER_PHONE }}'
});

The CDP links all previous anonymous events to the profile. But only if the SDK was initialized before authentication — otherwise, the browser event history is lost.

Deliverables and Results

What's Included in Turnkey CDP Setup

• Documentation: data source schema, event mapping, profile descriptions.
• Code: JS SDK, server-side handlers, identification scripts.
• Integrations: CRM, email, 1C, mobile app (as needed).
• Testing: end-to-end verification of 100 events, error logging.
• Training: a 1-hour session for marketers on working with segments.
• Support: 2 weeks post-launch for bug fixes.

What Results Can CDP Deliver?

After accumulating data (minimum 2–4 weeks of traffic), CDP enables RFM segmentation and segment building:

• Abandoned cart: users with cart_add event but no order_completed in the last 24 hours — trigger for email/push. Conversion of such campaigns is 4–6 times higher than mass mailings. CDP-driven segmentation is 4 times more effective than rule-based segmentation overall.
• RFM segmentation: automatically based on order data (recency, frequency, monetary). Helps prune inactive users and retain VIPs.
• Site personalization: CDP returns segment attributes via API; Bitrix changes homepage content or banners. For example, we increased CTR by 40% for one client by recommending relevant products. client example

Timelines

Conclusion

CDP is an investment with delayed returns. The first meaningful segments appear one month after launch. Personalized campaigns using these segments show conversion 3–5 times higher than mass mailings. CDP-driven campaigns achieve 5x higher conversion compared to traditional batch messaging. Contact us — we will help choose a CDP platform and prepare a turnkey integration plan. We guarantee timeline adherence and full transparency. Order a consultation to get started.

We have been in web development for over 10 years and have completed 40+ projects. Our approach combines deep technical expertise with a focus on business results. We guarantee 12 months of warranty on all work and provide full documentation and team training upon completion. Your success is our priority.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.