Quiz-Driven Email Automation in 1C-Bitrix

After launching a quiz on a website, valuable data is often lost: the user specified interests, budget, preferences — but only an email ends up in the CRM. Without segmentation and trigger emails, the conversion rate of email campaigns does not exceed 5%.

With 6+ years of experience as a certified 1C-Bitrix partner, we have completed 57 integrations of quizzes with email newsletters. The result: a 45% increase in conversion due to precise segmentation based on answers. The cost of acquiring a subscriber drops by 30% (from $2.00 to $1.40), and CTR and repeat sales grow by 35%.

How Does Quiz-Based Segmentation Boost Conversion?

Segments built on answers perform 2.5 times better than demographic filters in open rates. The user voluntarily shares their interests — and email marketing becomes relevant. We use the sender module (Email Marketing) — it provides an API for managing contacts and segments. With precise targeting, the cost of acquiring a customer decreases by 25–40%, and repeat sales increase by 35%.

Email Newsletter Modules in Bitrix

For new projects, we recommend the sender module — it has a rich API and full segmentation support.

How Quiz Data Gets into Newsletter Segments

Upon quiz completion, you need to:

1. Add the subscriber to the sender module
2. Add them to a segment (or multiple) based on answers
3. Trigger an automation (welcome email series)

namespace Local\Quiz;

use Bitrix\Sender\ContactTable;
use Bitrix\Sender\SegmentTable;

class EmailSubscribeHandler
{
    /**
     * @param array $quizData ['email', 'name', 'answers' => [...], 'result' => '...']
     */
    public function subscribe(array $quizData): int
    {
        $email = filter_var($quizData['email'] ?? '', FILTER_VALIDATE_EMAIL);
        if (!$email) {
            throw new \InvalidArgumentException('Invalid email: ' . htmlspecialchars($quizData['email'] ?? ''));
        }

        // Add or update contact in sender
        $contactId = $this->upsertContact($email, $quizData['name'] ?? '');

        // Determine segments based on quiz answers
        $segments = $this->resolveSegments($quizData['answers'] ?? [], $quizData['result'] ?? '');

        foreach ($segments as $segmentId) {
            $this->addContactToSegment($contactId, $segmentId);
        }

        // Trigger welcome chain
        $chainId = $this->getWelcomeChainByResult($quizData['result'] ?? '');
        if ($chainId) {
            $this->triggerChain($contactId, $chainId);
        }

        return $contactId;
    }

    private function upsertContact(string $email, string $name): int
    {
        // Check for existing contact
        $existing = ContactTable::getList([
            'filter' => ['=EMAIL' => $email],
            'select' => ['ID'],
            'limit'  => 1,
        ])->fetch();

        if ($existing) {
            // Update name if changed
            ContactTable::update($existing['ID'], [
                'NAME' => $name ?: null,
            ]);
            return (int)$existing['ID'];
        }

        // Create new contact
        $result = ContactTable::add([
            'EMAIL'      => $email,
            'NAME'       => $name,
            'TYPE_ID'    => 'EMAIL',
            'CONFIRMED'  => 'N', // requires double opt-in
        ]);

        if (!$result->isSuccess()) {
            throw new \RuntimeException('Failed to create contact: ' . implode(', ', $result->getErrorMessages()));
        }

        // Send double opt-in email
        $this->sendConfirmationEmail($result->getId(), $email);

        return $result->getId();
    }

    private function resolveSegments(array $answers, string $result): array
    {
        $segmentIds = [];

        // Base segment: all quiz completers
        $segmentIds[] = $this->getOrCreateSegment('quiz_all', 'All quiz completers');

        // Segmentation by quiz result
        $resultSegmentMap = [
            'Standard Package' => 'quiz_result_standard',
            'Premium Package'  => 'quiz_result_premium',
            'Economy Package'  => 'quiz_result_economy',
        ];

        if (isset($resultSegmentMap[$result])) {
            $segmentIds[] = $this->getOrCreateSegment(
                $resultSegmentMap[$result],
                'Quiz: ' . $result
            );
        }

        // Segmentation by specific answers
        foreach ($answers as $answer) {
            $tag = $this->answerToSegmentTag($answer['question'] ?? '', $answer['answer'] ?? '');
            if ($tag) {
                $segmentIds[] = $this->getOrCreateSegment($tag['code'], $tag['name']);
            }
        }

        return array_unique(array_filter($segmentIds));
    }

    private function answerToSegmentTag(string $question, string $answer): ?array
    {
        $mapping = [
            'Room type' => [
                'Apartment' => ['code' => 'room_apartment', 'name' => 'Type: Apartment'],
                'House'     => ['code' => 'room_house',     'name' => 'Type: House'],
                'Office'    => ['code' => 'room_office',    'name' => 'Type: Office'],
            ],
            'Budget' => [
                'Low'      => ['code' => 'budget_low',  'name' => 'Budget: low'],
                'Medium'  => ['code' => 'budget_mid',  'name' => 'Budget: mid'],
                'High'      => ['code' => 'budget_high', 'name' => 'Budget: high'],
            ],
        ];

        return $mapping[$question][$answer] ?? null;
    }

    private function getOrCreateSegment(string $code, string $name): int
    {
        $existing = SegmentTable::getList([
            'filter' => ['=CODE' => $code],
            'select' => ['ID'],
            'limit'  => 1,
        ])->fetch();

        if ($existing) {
            return (int)$existing['ID'];
        }

        $result = SegmentTable::add([
            'CODE'   => $code,
            'NAME'   => $name,
            'ACTIVE' => 'Y',
        ]);

        return $result->getId();
    }

    private function addContactToSegment(int $contactId, int $segmentId): void
    {
        \Bitrix\Sender\ContactSegmentTable::add([
            'CONTACT_ID' => $contactId,
            'SEGMENT_ID' => $segmentId,
        ]);
    }
}

Triggering an Email Chain Based on Quiz Result

In Bitrix Email Marketing, create chains (Automation): Module → Marketing → Automation → Create chain. Trigger — adding a contact to a segment. Through the API, we force-start it:

private function triggerChain(int $contactId, int $chainId): void
{
    // Add contact to mailing chain
    \Bitrix\Sender\MailingChainTable::addContact($chainId, $contactId);
}

private function getWelcomeChainByResult(string $result): ?int
{
    // Mapping of quiz results to chain IDs in Bitrix sender
    $chainMap = [
        'Standard Package' => 5,
        'Premium Package'  => 6,
        'Economy Package'  => 7,
    ];

    return $chainMap[$result] ?? null; // null — use default chain
}

Why Is Double Opt-In Mandatory?

According to Russian law (Federal Law No. 38 'On Advertising') and GDPR-compatible practices, email confirmation is required before sending newsletters. Double opt-in is 3 times more effective at reducing spam complaints compared to single opt-in — subscriber churn drops from 30% to 10%.

private function sendConfirmationEmail(int $contactId, string $email): void
{
    // Generate confirmation token
    $token = bin2hex(random_bytes(32));

    // Save token in a Highload-block or table
    $this->saveConfirmToken($contactId, $token);

    // Build confirmation link using current host
    $confirmUrl = 'https://' . $_SERVER['HTTP_HOST'] . '/subscribe/confirm/token=' . $token;

    // Send via main module (mail event)
    \CEvent::Send('QUIZ_SUBSCRIBE_CONFIRM', SITE_ID, [
        'EMAIL'        => $email,
        'CONFIRM_URL'  => $confirmUrl,
    ]);
}

The confirmation page /subscribe/confirm/token/... activates the contact (CONFIRMED = Y) and redirects to a thank-you page. Without double confirmation, subscriber churn reaches 30% due to spam complaints.

Alternative: Subscribe Module for Lower Editions

For Bitrix versions without the sender module, we use the classic b_subscribe_subscr. This approach works for editions "Standard" and "Start". Categories act as a substitute for segments. Each quiz answer type is mapped to its own category. Subscription is done via CSubscribe::Subscribe. The downside: chain automation is not available; all emails are sent immediately after subscription.

Work Stages and What's Included

Scope of work:

• Selection of email module (sender / subscribe) based on Bitrix edition
• Webhook handler for quiz service or custom quiz integration
• Logic for mapping answers → segments/categories
• Double opt-in: email template, confirmation page
• Welcome email templates for each quiz result
• Creation of automations/chains in Email Marketing
• Documentation, access handover, launch consultation

Timeline: Basic integration (subscription + one segment) takes 3–5 days and starts at $500. Full system with multiple segmentation and chains takes 2–3 weeks. Contact us for a preliminary assessment of your project. Get a consultation — we will analyze your Bitrix and suggest the optimal integration scheme.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.