Skip to content

Get UTM parameters into Microsoft Power BI for channel reporting

Power BI dashboards are only as useful as the data connected to them. To break leads, customers, opportunities and revenue down by marketing channel and campaign, UTM and related attribution values must be captured on the website, stored with each conversion record, and then made available to Power BI.

How attribution data reaches Power BI

A site code snippet reads technical visit information, including UTM values in the landing URL, and classifies the visitor into a channel such as Organic Search, Paid Search or Paid Social. That classification is stored in a browser cookie. When a form is submitted, the stored attribution values, together with details such as the landing page, are sent to the CRM or other backend system. Once those fields sit alongside lead, customer and revenue records, Power BI can group outcomes by channel or campaign and answer questions about customers from a given ad platform, average deal size by source, campaign revenue and overall advertising return.

Four-step implementation checklist

  1. Add UTM variables to every paid and custom campaign, including social, search and bespoke activity, so the origin of each visit can be identified. 2. Install the provided site code using the CMS header settings or a tag manager, following the same pattern as other marketing tags. 3. Pass the stored values into the CRM or backend store at conversion. 4. Connect Power BI to that store and build reports grouped by channel or campaign. Before building dashboards, check that each conversion record carries the expected UTM fields, channel, landing page and landing page group.

Hidden fields versus cookie recapture

Hidden fields are filled when the form page loads and travel with the submitted data, which suits standard forms. Cookie recapture uses a small JavaScript addition to retrieve stored values at submission and avoids hidden fields; it is particularly useful where social sign-in buttons let people register without completing a conventional form. Choose based on the conversion path, then test a submission from a tagged landing page to confirm every field arrives in the backend record.

Why go beyond raw UTM capture

Capturing only raw UTM values misses visits without tags, such as referral, organic social, organic search and direct traffic, so not every lead can be sourced. Cookie storage also preserves campaign information when a visitor browses several pages before converting, unlike tools that read UTM values only from the form page URL. Normalisation handles inconsistent tagging from different teams or agencies: variants of the same source are mapped to one standard channel instead of appearing as separate sources. Landing page and landing page group add a further view, allowing a whole site section and an individual page to be compared for leads, customers and revenue.

Reporting questions the data can support

Use the finished data to compare outcomes that matter commercially: leads from a search campaign, pipeline from a professional-network campaign, sales opportunities from social advertising, customers from editorial content, and revenue attributed to organic search. If a breakdown looks fragmented, inspect the underlying UTM values for spelling and capitalisation variants before changing the dashboard.

UTM to Power BI workflow checklist
StepActionCheck before moving on
1Tag paid and custom campaigns with UTM parametersEvery active campaign URL carries consistent UTM values
2Install the site code via CMS header or tag managerCode fires on landing pages and stores attribution in a cookie
3Send attribution to the CRM or backend store at conversionA test submission contains UTM, channel and landing page fields
4Connect Power BI to the backend storeReports group leads, customers, opportunities and revenue by channel or campaign

Workflow summary based on the captured four-step process; implementation details depend on the owner's CMS, forms and CRM.

Frequently asked questions

Why does Power BI not show campaign results automatically?

Power BI can only report on data it receives. If UTM values are not stored with each lead, customer, opportunity or revenue record in the connected CRM or backend system, campaign and channel breakdowns will be missing or incomplete.

What is the shortest reliable workflow?

Add UTM parameters to paid and custom campaigns, install the site code, pass attribution data into the CRM or backend store on form submission, then connect Power BI to that store. The four-step workflow below follows that order.

Should I use hidden fields or cookie recapture?

Hidden form fields work when visitors submit a normal form. Recapturing values from the browser cookie with JavaScript is useful when signup buttons such as social sign-in bypass a conventional form.

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

Raw URL capture loses values when the form is on a later page. Storing attribution in a browser cookie preserves the original campaign information across pageviews and sessions until submission.

Why normalise UTM values instead of reporting them raw?

Inconsistent values such as Facebook, facebook and fb can split one channel into several apparent sources. Normalising values into a standard channel, such as Paid Social, prevents misleading splits in reports.