Website Integration with Bitrix24: Requests, Sources and End-to-End Analytics
A company spends money on advertising, requests arrive by email, someone transfers them to the CRM, and someone does not. A month later, you cannot tell which ads brought in clients, and some requests remain unanswered.
What should go into Bitrix24
- requests from website forms with all fields;
- calls with the phone number, recording, and source;
- messages from chats and messaging apps;
- dealer applications and quote requests;
- source: advertising channel, campaign, keyword.
How this is set up
- Website forms send data to Bitrix24 via API or built-in CRM forms.
- UTM tags and visit data are saved together with the request.
- Calls are connected through telephony with number swapping to track the source.
- Requests are routed to managers based on rules.
- The manager receives a notification and a task with response time control.
Common problems
- some forms are not connected to the CRM;
- UTM tags get lost when navigating between pages;
- duplicate leads from the same client;
- no control over request response times;
- managers do not log results, and advertising is optimized blindly.
Frequently asked questions
Are built-in Bitrix24 forms suitable?
For simple scenarios, yes. For complex forms, calculators, and client portals, integration via API is more convenient.
How do you send sales results back to advertising?
Through end-to-end analytics, covered in detail in a separate article.
Can you connect messaging apps?
Yes, through Bitrix24 Open Channels or integrations.
