Skip to content

Get UTM parameters into Bitrix24 and report on lead source

Knowing which campaigns create leads, customers and revenue helps you shift effort toward what works. The workflow below connects website visits to Bitrix24 records by tagging campaigns, preparing forms to receive source data invisibly, and then using the stored values in CRM reporting.

Why lead source belongs in the CRM

Growth decisions improve when every CRM record shows how the contact arrived. A positive return from one paid campaign, for example, is a reason to invest more there, while weak channels may deserve less. Recording the source of each lead and opportunity makes that comparison possible inside Bitrix24 or in a separate analytics tool.

Step 1: Tag campaigns before traffic arrives

Start by tagging every advertisement and campaign consistently. Coverage should include social platforms such as LinkedIn, Facebook and Twitter, as well as search engines such as Google, Bing and Yahoo. Without tags on the incoming visit, later form data has no campaign context to carry forward.

Step 2: Add invisible fields to lead forms

Next, add invisible fields to each lead-capture form. Visitors do not see them, but a tracking tool can populate them before submission. The same drag-and-drop approach applies whether the form is built inside Bitrix24 or with a third-party builder such as Gravity Forms or Jotform.

Field checklist

Use these six fields so channel detail and entry-page detail travel with the submission: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; Landing Page Group. Check that each field is present on every form used for lead capture, not only on campaign landing pages.

Step 3: Let the tracking script populate the fields

A website script scans each visit for UTM parameters, referrer information and device data. It then assigns a channel such as Paid Search, Organic Search or Paid Social and saves the result in a browser cookie. When a form is completed, the saved values fill the invisible fields automatically.

Worked example: from paid search click to CRM record

Consider a file-storage company whose paid search advertisement appears for a query about sharing large files. A visitor clicks through, requests a demo, and the invisible fields are completed with Channel set to Paid Search, Channel Drilldown 1 set to Google, Channel Drilldown 2 set to Share Files Campaign, and Channel Drilldown 3 set to Demo Request Ad. The entry page is recorded as www.dropbox.com/features/share, with Features as its group. On submission, Bitrix24 receives those values together with the visitor's name, email and phone details, ready for reporting by campaign and channel.

Why this approach gives cleaner reporting

Capturing every visit matters because UTM-only tools miss organic and direct traffic. Cookie storage also preserves the original campaign when the conversion form sits on a different page from the landing page. Cleaning inconsistent values prevents variants such as different capitalisation or abbreviations for the same social source from splitting one channel into several report rows. Recording the landing page and its group additionally shows whether content such as a blog is generating leads and customers.

Pre-launch check

Before relying on reports, test one tagged campaign end to end: confirm the visit is categorised, the invisible fields fill correctly, the submitted Bitrix24 record contains all six values, and a report groups records by channel and drilldown without duplicate variants. Repeat the check for an organic visit and for a visitor who moves to a different page before submitting.

Frequently asked questions

How do UTM parameters reach Bitrix24 through a form?

Add UTM parameters to every ad and campaign, including paid social and search placements. Then add invisible fields to each lead form for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. A tracking script reads UTM, referrer and device data, categorises the visitor, stores it in a browser cookie, and completes those fields when the form is submitted so Bitrix24 receives the source data with the lead details.

Does this only work for traffic with UTM parameters?

Yes. The approach described monitors all visitors, not only those arriving with UTM parameters, so organic search, organic social, direct and referral visits can also be categorised and passed to the CRM.

What if a visitor lands on one page and submits a form on another?

Yes, because the categorised data is stored in a cookie. The original campaign data can therefore survive a move from the landing page to a different page where the visitor completes a form.

Why clean UTM values before reporting?

Cleaning helps when the same source is tagged inconsistently, for example with different capitalisation or abbreviations. Normalising those variants into one channel prevents a single source appearing as several separate sources in CRM reports.