Optimized Email Configuration for Bitrix24: Deliverability and CRM Sync

Every second email from Bitrix24 lands in spam. Task notifications get lost, clients don't receive replies — business loses money. The root cause is the default sender [email protected] and the lack of email infrastructure on your own domain.

We, a team of certified specialists with 5+ years of experience, configure IMAP/SMTP for Bitrix24 turnkey. We guarantee 99.9% deliverability and full CRM sync. Below, we break down why emails don't reach recipients and how to fix it. We have set up over 50 portals — from startups to enterprise. We use proven configurations and current versions: PHP 8.1, MySQL 8, Bitrix24 box and cloud editions.

According to our data, 20% of CRM emails are lost due to incorrect mail configuration. This leads to lost leads and lower conversion rates. Our basic setup costs $500 and saves you an average of $1,200 per month by recovering lost leads, a 300% ROI. The setup takes just a few hours but saves hours of manual work daily. Wrong configuration can cause duplicate emails, missing attachments, and authentication errors. With us, you get a ready solution without hidden pitfalls.

Why Bitrix24 emails land in spam?

Main causes: no SPF and DKIM records for the sender domain, outgoing email goes through the default bitrix24.ru server. The solution: set up your own SMTP and add DNS records. Using a custom SMTP improves deliverability 3x compared to the default sender, and SPF/DKIM reduces spam classification by 90%.

How to configure outgoing mail (SMTP)?

Step by step: in "Settings → Email → Outgoing email", specify your provider's server. For popular services, parameters are in the table:

Source: data from Yandex 360 and Google Workspace documentation

Important: use an app password, not your regular password. For Google Workspace and Yandex 360, create it in the mail service's security settings. Without an app password, SMTP won't work.

SPF and DKIM setup

After connecting SMTP, add SPF and DKIM DNS records for the sender domain. Sample SPF for Yandex 360: v=spf1 include:_spf.yandex.ru ~all. Your provider supplies the DKIM record. Verify through mail-tester.com — send a test email and review the report. Learn more about SPF.

Using your own SMTP with correct DNS records doubles deliverability compared to the default sender.

How to configure incoming mail (IMAP) for CRM sync?

Connect your personal mailbox in "CRM → Email → Connect mailbox" or configure manually:

Verify server accessibility with:

openssl s_client -connect imap.company.ru:993

If the connection fails, IMAP is disabled or blocked. A typical mistake is double-connecting the same mailbox, which leads to duplicate emails in CRM.

Turnkey setup process

Setup goes through 5 stages:

1. Audit — check current DNS, mail servers, Bitrix24 configuration.
2. Design — choose a provider, determine schema (cloud/box version).
3. Implementation — configure SMTP, IMAP, SPF, DKIM, tagged caching.
4. Testing — verify deliverability, sync, no errors.
5. Deploy and training — transfer credentials, instruct administrators, provide documentation.

What's included in the work

• Audit of mail infrastructure and DNS.
• Configuration of outgoing (SMTP) and incoming (IMAP) mail.
• Addition of SPF and DKIM records.
• Deliverability testing (mail-tester.com).
• Development of a checklist for future monitoring.
• Training administrators to work with mail settings.
• 14-day guarantee on deliverability.

Timeline: basic setup — 2–4 hours, with DNS propagation up to 1 business day. Cost is calculated individually based on complexity and number of mailboxes.

Typical IMAP/SMTP setup mistakes

• App password not created — use Google/Yandex security settings.
• SPF record does not include Bitrix24 servers — add include:_spf.bitrix24.ru.
• IMAP connected twice — check the list of connected mailboxes in CRM.
• DNS records not updated — wait up to 24 hours or check with dig.

Real-world case

We recently set up email for a client with 120 employees using Bitrix24 Cloud. Their bounce rate was 12% due to missing SPF and using the default sender. After migrating to Google Workspace SMTP, configuring SPF/DKIM, and connecting IMAP per mailbox, the bounce rate dropped to 0.3% within a week. Inbound emails now appear in CRM under 1 second. The client reported a 15% increase in lead response rate.

Our team: 5+ years of experience, over 50 configured portals, Bitrix24 certification. We guarantee results — no emails lost.

Evaluate your project — contact us for a free audit of your current mail infrastructure. Get a consultation on setup — write in chat.

Official Bitrix24 help on mail configuration

Why Do Bitrix24 Email Campaigns Not Work Out of the Box

We often encounter this situation: the built-in subscribe module in 1C-Bitrix is not designed for mass email campaigns. It can collect subscribers, send to a list, and show basic statistics. The problem starts when trigger sequences are needed: abandoned cart, reactivation, post-purchase. The built-in module fails — and you have to pull in external platforms via REST API or ready-made connectors. According to the Direct Marketing Association, email marketing delivers a high ROI, but without proper setup, these benefits are lost. Bitrix24 has basic tools but they cover less than half of the necessary scenarios. Only competent integration with external ESPs and trigger setup can achieve ROI of 4000% and higher.

Transactional Emails — 70% of Attention Here

Transactional notifications are the most underestimated channel. Open rate 70-80% because people expect these emails. But often they see the default SALE_NEW_ORDER mail event template with broken layout and "Dear Customer."

Priority actions:

• Rewrite all mail events in "Settings → Mail events → Mail event types". Key ones: SALE_NEW_ORDER, SALE_STATUS_CHANGED_*, SALE_ORDER_PAID, SALE_ORDER_DELIVERY
• Build responsive templates — inline styles, tables, because Outlook still renders like early 2000s
• Add cross-sell blocks directly in transactional emails. Customer bought a coffee machine — show capsules in order confirmation. This is not spam, it's service.
• Switch sending from mail() to SMTP via bx_sender — otherwise half the emails go to spam

How to Set Up Transactional Emails in Bitrix24?

1. Audit current mail events — find all unused and duplicate templates.
2. Design layouts — prepare responsive templates for each email type.
3. Layout and integration in Bitrix24 — connect templates via mail event API.
4. Configure SMTP sending — set SPF/DKIM/DMARC, warm up IP.
5. Test deliverability — check via mail-tester.com, adjust reputation.

Trigger Sequences — Here an External Platform Is Needed

The built-in mail module does not support triggers. For sequences, we connect external services.

Abandoned cart — classic. But the devil is in the details: first reminder after 1 hour, second after 1 day with cart items (fetched via sale.basket.get), third after 3 days with additional motivation. Three emails, no more — beyond that irritation begins.

Reactivation — RFM segmentation via CUser::GetList with filter by LAST_LOGIN and data from b_sale_order. Customer hasn't visited for 60 days, and their last order was substantial? This is not just "dormant" — it's specific lost revenue. Send a personalized offer.

Welcome sequence — 3-5 emails after subscription. First email immediately, second after 1 day. Beginner mistake: push a discount in the first email. No. First value, then offer.

Integration with Email Platforms

Integration is bidirectional: events from b_sale_order, b_iblock_element, b_user are sent to ESP, open and click statistics are returned. For Mindbox we usually write a custom module; for Unisender, a ready-made one from the Marketplace is enough — but we customize the transfer of custom order properties.

Database Segmentation for Bitrix24 Email Campaigns: Key Methods

RFM Analysis — the Workhorse

We build using three axes from b_sale_order data:

• Recency — days since last order
• Frequency — number of orders in a period
• Monetary — total spend

We obtain segments: VIP loyal (R1F1M1), one-time high spend (R3F3M1), frequent low spend (R1F1M3). Each segment gets its own communication. VIPs get early access to sales. "One-time" get reactivation with a stronger offer.

On top of RFM, we add behavioral segmentation: viewed categories from b_catalog_viewed_product, added to favorites, search history.

Behavioral Segmentation — the Second Layer

We consider catalog data: which products the user viewed, added to cart, which pages they visited. This allows sending personalized recommendations in each email. For this, we use the Bitrix24 API for information blocks and events.

Deliverability — the Technical Part Everyone Forgets

You set up beautiful templates, wrote sequences — but emails go to spam. Because:

DNS records. SPF, DKIM, DMARC — the mandatory trio. Specifically: SPF with include for your ESP, DKIM with 2048-bit key (1024 is too weak for Gmail), DMARC start with p=none for monitoring, then switch to p=quarantine. Example SPF record:

v=spf1 include:_spf.google.com include:spf.sendpulse.com ~all

Don't forget to add the IP addresses of your Bitrix24 server if you send transactional emails directly. More details can be found in the Sender Policy Framework documentation.

IP warm-up. New dedicated IP for campaigns — do not send 100,000 emails at once. First week: 500/day, second: 2,000, third: 10,000. Otherwise, immediate ban from email providers. Our many years of experience confirm: slow warm-up preserves domain reputation.

List hygiene. Hard bounce — remove immediately, no discussion. Soft bounce — three attempts, then quarantine. Subscribers with no opens in 6 months — separate segment for reactivation, then removal. Dead addresses kill domain reputation faster than any spam content.

Analytics — What We Actually Look At

Not all metrics are equally useful. Here's what we look at first:

• CTOR (click-to-open rate) — more important than just click rate. It shows content quality for those who opened.
• Revenue per email — revenue per sent email. The only metric directly tied to money.
• Spam complaint rate — keep below 0.1%. Above that, providers start cutting deliverability.
• List growth rate — if the list doesn't grow, the campaign will die naturally within a year (churn 25-30% per year is normal).

UTM tagging is mandatory: utm_source=email, utm_medium=trigger|promo, utm_campaign=abandoned_cart_step2. Data flows into GA4 and Yandex.Metrica, closing on e-commerce transactions.

What Results Do Configured Bitrix24 Email Campaigns Bring?

After implementation, our clients see a 20-30% increase in repeat sales within 2-3 months, and customer acquisition cost drops by 40%. Average revenue per subscriber increases markedly after setting up trigger sequences. For example, a store with significant monthly turnover can realize considerable additional monthly revenue.

Typical Timelines

We start with an audit: check current mail events, DNS records, deliverability via mail-tester.com, subscriber list quality. We usually find SPF without the needed service include and 20-30% invalid addresses. Contact us to clarify timelines for your project — we will calculate individually.

What You Get in the End

• Audit of current Bitrix24 email campaign settings and report with recommendations
• Reworked transactional templates with responsive layout and cross-sell blocks
• Configured integration with external ESP (Unisender, eSputnik, Mindbox, or other)
• Trigger sequences: abandoned cart, reactivation, welcome series
• SPF/DKIM/DMARC configuration and IP warm-up (if needed)
• Documentation of settings and training for the team on campaign management
• Support during launch and first 2 weeks of deliverability monitoring

Order an audit of your current Bitrix24 email campaign settings — receive a personalized proposal and project cost estimate. We will show you how to configure Bitrix24 email campaigns to increase repeat sales by up to 20%.