Bitrix24 Email Tracker Setup: Linking Emails to Deals
When an internal email is sent from a personal mailbox and doesn't reach CRM — the deal context and contact history are lost?
Based on our experience, up to 30% of client inquiries disappear precisely due to the disconnect between email and the system. Implementing a Bitrix24 email tracker solves this: each email is automatically linked to a deal or contact. In a few hours of setup, you gain full communication transparency — email losses drop to 2-5%. Our engineers have been configuring the tracker for over 9 years, completed more than 50 projects — from startups to corporations with hundreds of mailboxes.
Why are emails lost in CRM?
The most common cause is a mismatch between the email address in the CRM contact and the email. Different domain, typo, alias — check the EMAIL field of the contact. The second reason is an incorrectly connected mailbox: IMAP server not responding or app password not configured (relevant for Google, Yandex). The third is mixing connection methods: a mailbox configured both as personal and shared, which duplicates emails. The solution is to use only one method. In our practice, over 90% of problems are resolved in a single session.
How does Bitrix24 email tracker solve the email linking problem?
The email tracker is a feature of the CRM module that links emails to contacts and deals by email address. It works in two ways:
-
Connecting a personal mailbox via IMAP. The manager connects their mailbox. Bitrix24 scans folders every 5 minutes via the agent
\Bitrix\Mail\Internals\MessageTable and creates activities in CRM if the sender/recipient address matches the database.
-
BCC tracker. A special BCC address, a copy of the email goes to CRM. The BCC tracker is set up 3 times faster than IMAP (5–10 minutes vs 30–60). It doesn't depend on the email provider — works with any client.
Technically, both methods use the mail module for receiving and CRM for parsing. According to Bitrix documentation, IMAP connection supports IMAP v4rev1.
Typical problems and their solutions
| Problem |
Cause |
Solution |
| Emails don't link to deal |
Email in message and CRM don't match |
Check the EMAIL field of the contact, correct the address |
| IMAP authorization error |
IMAP not enabled or wrong app password |
Enable IMAP, create an app password |
| Duplicate emails |
Mailbox connected twice (personal and shared) |
Remove one connection |
| BCC copies don't create activity |
Incorrect BCC address (spaces, typos) |
Copy the BCC address without extra characters |
How to set up an email tracker for a department
Step-by-step personal mailbox setup
- Go to CRM → Mail → Connect mailbox (or in the employee's profile).
- Choose a provider: Google, Microsoft 365, Yandex, Mail.ru, or enter IMAP server manually.
- For Google and Microsoft — OAuth authorization, for others — login and password. If the provider requires an app password, create one.
- Specify folders to scan: "Inbox" mandatory, "Sent" optional.
- Set rules for emails from unknown senders: ignore, create a lead, or create a contact.
How to set up a BCC tracker in 5 minutes?
- In the CRM mailbox settings, get the unique BCC address (issued automatically).
- When sending an email from any client, add this address to the BCC field.
- Bitrix24 will receive the copy and create an
email activity in the related entity.
- Verify: after sending, the deal or contact should have the email in the timeline.
Details of BCC tracker operation
The BCC tracker uses a system-created mailbox. Emails are processed by an agent that checks headers and creates activities. Maximum delay — up to 2 minutes.
IMAP connection: what you need to know
If your mail server is non-standard, enter parameters manually: server (e.g., imap.example.com), port (993 for SSL, 143 for STARTTLS), encryption. Bitrix24 supports IMAP v4rev1. For corporate servers, you may need to whitelist Bitrix24 IP addresses. Ensure IMAP is enabled on the provider side — this is a mandatory condition.
Comparison of connection methods
| Characteristic |
Personal mailbox (IMAP) |
BCC tracker |
| Requires mailbox access |
Yes, login/password or OAuth |
No, only BCC address |
| Supports outgoing emails |
Yes (if Sent folder is enabled) |
Only outgoing (copy) |
| Depends on email provider |
Yes, needs IMAP access |
No, works with any client |
| Duplicate risk |
Higher (if mailbox connected again) |
Minimal |
| Setup time |
30–60 minutes |
5–10 minutes |
| Processing speed |
Up to 2 minutes per email |
Up to 10 seconds |
Open and click tracking
When sending from CRM, Bitrix24 automatically adds a tracking pixel and wraps links. Data is visible in the timeline ("Read" icon), triggers, and reports. Limitation: if the client disables image loading, the pixel doesn't fire — this is standard behavior for all trackers.
What's included in the setup
- Audit of current email infrastructure: which mailboxes, providers, exchange schemes.
- Connection of personal manager mailboxes (IMAP/OAuth).
- Setting up a shared departmental mailbox (e.g., sales@).
- Generation and implementation of BCC tracker.
- Calibration of linking rules to deals/contacts (including handling unknown addresses).
- Testing with real emails and error correction.
- Documentation on setup and employee training.
- Post-setup: answering questions within a week.
Contact us for an evaluation of your project — we'll prepare a solution in one day. Get a consultation on email tracker setup tailored to your business processes. Order the setup — and your emails will never be lost again.
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?
- Audit current mail events — find all unused and duplicate templates.
- Design layouts — prepare responsive templates for each email type.
- Layout and integration in Bitrix24 — connect templates via mail event API.
- Configure SMTP sending — set SPF/DKIM/DMARC, warm up IP.
- 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
| Service |
When to Choose |
Pitfalls |
| Unisender |
Small business, quick start |
API limits on free plan, slow sending with >50k base |
| Mindbox |
Large e-commerce, CDP needed |
Long deployment (2-3 months), expensive license, but segmentation is best in market |
| eSputnik |
Mid-sized e-commerce, omnichannel |
Good price/functionality balance, decent API |
| SendPulse |
Email + SMS + push in one |
Multichannel out of the box, but automation weaker than Mindbox |
| RetailRocket |
Product recommendations |
Focused on ML recommendations in emails, not a universal ESP |
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
| Task |
Timeline |
| Reworking transactional templates |
1-2 weeks |
| Basic email strategy (5-7 triggers) |
3-4 weeks |
| Complete CDP integration (Mindbox/eSputnik) |
6-10 weeks |
| ESP integration via API |
1-2 weeks |
| Responsive email template design (set of 8-12 emails) |
1-2 weeks |
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%.