Problem: Leads in VK Ads but not in CRM
A marketer launches a campaign in VK Ads, collects leads via lead forms, exports them to CSV, manually enters them into CRM. Some applications get lost, response time ranges from hours to the next day. Audiences for retargeting are collected manually, costs are calculated in a separate spreadsheet. We know this pain: over 10 years we have completed more than 50 projects integrating VK Ads with Bitrix24 and guarantee that manual work becomes a thing of the past—leads land in CRM in seconds, audiences are built from CRM segments, costs are imported automatically. The VK Ads and Bitrix24 combo works as a single organism—ad budgets bring measurable sales, not just leads. We'll evaluate your project in 1 hour, set up turnkey in 2-3 working days. Budget savings after setup range from 30% to 50% on cost per lead, which can save up to 300,000 rubles monthly.
Why sync VK lead forms with CRM?
VK Ads allows creating lead forms—users fill out an application right in the feed without leaving for a website. Without integration, these applications stay in the VK cabinet waiting for manual export. According to our data, up to 50% of leads are lost during manual export—managers fail to process the application while the client is still online.
When connected to B24, lead forms sync via CRM → Sales Generator or via REST API. How it works:
- User fills out a lead form in VK.
- VK sends a webhook with the application data.
- B24 receives the webhook and creates a lead (or deal—depends on settings) with filled fields: name, phone, email, UTM tags.
- A responsible manager is assigned, robots trigger at the first funnel stage.
Time from form submission to lead appearing in CRM: 2-3 seconds. The manager gets a notification and can call back while the client still remembers they left an application. Response speed increases 10 times compared to manual transfer.
Mapping lead form fields
Fields of the VK lead form need to be mapped to CRM fields. Standard fields (name, phone, email) map automatically. Custom form fields (city, budget, service type) require manual setup—create a field in CRM, specify the mapping.
| VK Ads Field | B24 CRM Field | Comment |
|---|---|---|
| Name | Contact name | Automatic |
| Phone | Phone | Automatic |
| Automatic | ||
| Custom field | Custom lead field | Manual mapping |
| utm_source, utm_campaign | UTM_SOURCE, UTM_CAMPAIGN | Via link parameters |
For example, if the lead form has a field "Budget", we create a custom field with the same name in CRM and attach it to the lead. This allows building reports by budget and segmenting audiences.
Audiences from CRM segments
Reverse sync: CRM data flows into VK Ads as audiences for targeting. Scenarios:
- Look-alike based on customers: export segment "All clients with closed deals in the last year" → VK builds a similar audience.
- Retargeting based on non-closed deals: segment "Deals at proposal stage, no activity for 14 days" → show ads to these contacts.
- Exclude existing clients: upload active client base → exclude from acquisition campaigns, avoid wasted budget.
Audience export works via CRM Marketing → Audiences. B24 sends hashed phones and emails to VK (data is hashed, not transmitted in clear text). VK matches hashes with its user base.
Audiences can be updated automatically: when a contact enters a CRM segment, they are added to the VK audience. This is set up with regular sync scheduling, e.g., every hour.
How to send offline conversions from CRM to VK Ads?
VK Ads supports sending offline conversions—events that happened in CRM after an ad click. When a deal moves to "Closed successfully" stage, B24 can send a conversion event back to VK Ads.
This enables VK algorithms to optimize ad delivery based on actual sales, reducing acquisition cost by 30-50% and saving ad budget. For complex scenarios, custom integration via REST API works 3 times faster than the default connector.
Mechanism:
- A pixel is created in VK Ads and a conversion event is set up.
- In B24, a robot is configured on the "Closed successfully" stage—it calls a webhook or REST method that passes conversion data to VK.
- VK matches the conversion with the click via click_id or contact data hash.
Example of setting up a webhook for offline conversion
// Example of calling Bitrix24 REST API
$result = $webhook->call('crm.deal.update', [
'id' => $dealId,
'fields' => [
'UF_CRM_CONVERSION_SENT' => 'Y'
]
]);
?>
Then the robot sends a POST request to the VK Ads webhook URL with a JSON containing click_id and deal number.
Cost import and end-to-end analytics
B24 pulls cost data from VK Ads via API:
- Costs broken down by campaigns and ads
- Number of impressions, clicks, CTR
- Data updates automatically (frequency: once per day, can be triggered manually)
In the end-to-end analytics report, VK costs are matched to leads and deals via UTM tags. You can see how much was spent on a campaign, how many leads obtained, how many converted into deals, what is the customer acquisition cost (CAC). For example, after setup, CAC can drop from 5,000 to 2,500 rubles.
For correct operation, all links in VK ads must contain UTM tags with utm_source=vk (or similar value matching B24 tracking settings).
Table: manual vs automated process
| Criterion | Manual handling | VK Ads + B24 integration |
|---|---|---|
| Lead appearance time in CRM | 1-24 hours | 2-3 seconds |
| Lead loss | up to 50% | 0% |
| Manager response speed | from hours | 5-10 minutes |
| Audience updates | once a week | real-time |
| Ad costs | manual calculation | automatic import |
Built-in connector vs custom integration
B24 provides a built-in connector for VK in the end-to-end analytics section. It covers basic scenarios: cost import, lead form connection.
For advanced scenarios (automatic audience export with dynamic update, offline conversion tracking, custom field sync) additional development is needed via VK Ads REST API and B24 webhooks. Custom integration pays for itself in 2-3 months thanks to savings on manual labor and ad budget optimization.
What's included in integration setup (deliverables)
- Connecting VK Ads ad account to B24 via built-in connector
- Lead form sync: field mapping, responsible assignment, robots for incoming leads
- Setting up CRM audience export to VK Ads (look-alike, retargeting, exclusions)
- Cost import and end-to-end analytics report setup
- Tagging ad campaigns with UTM tags
- Setting up offline conversion tracking from CRM to VK Ads
- Testing: fill lead form → verify lead creation → check UTM → verify report
- Training managers and documentation for working with integration
For more details on setup, read the official Bitrix24 documentation.
Want the same integration? Get a consultation for your project—we'll estimate timelines and costs in 1 hour. Contact us to start turnkey integration.