CRM / Bitrix24 · analytics · marketing
Traffic-source analytics in Bitrix24
Client:
NDA
Category: CRM / Bitrix24
Stack: Bitrix24, call tracking, web analytics, PHP
Timeline: 2–3 weeks
Problem
The client did not know which ad channels actually drove inquiries and sales — budget was split by gut feel, and some campaigns quietly ran at a loss.
Constraints
Different traffic sources (calls, form requests, messengers) had to be brought into one picture with no manual tagging and no data loss in call tracking.
What I did
- Set up source tracking through call tracking and web analytics tied to Bitrix24 deals
- Automatic tagging of inquiries by channel and ad campaign — no manual tagging by managers
- A rollup across dozens of traffic sources and campaigns in a single report
- The "source → inquiry → deal → outcome" chain visible right in the CRM
Architecture
Ads and channels
→ Call tracking
→ Web analytics
→ Bitrix24 CRM
→ Source report
Result
The client saw which channels and campaigns actually drove deals and could reallocate budget deliberately — instead of guessing.
What can be reused
Call tracking and web analytics tied to the CRM with no manual tagging
Rollup across many sources and campaigns in one report