How to get UTM parameters into Looker
Looker can only break down performance by channel and campaign if those values arrive with your lead, opportunity and revenue records. This guide explains the capture-to-reporting flow, the two handoff options, and the checks that keep campaign data usable.
Why capture comes first
Looker is a business intelligence platform for exploring and sharing analytics, but its reports depend on the records supplied to it. UTM parameters therefore need to be captured on the website and attached to downstream lead or customer data before Looker can show which channels and campaigns produced them.
How the capture tool works
Website code reads the UTM values in the arriving URL, groups the visitor into a channel such as Organic Search, Paid Search or Paid Social, and stores that attribution in a browser cookie. When a form is submitted, the stored values can travel with the form data into a CRM or other backend system, and from there into Looker.
Four-step workflow
- Add UTM parameters to every paid and campaign link, including social ads, search ads and bespoke placements such as trade publications, so the arriving traffic can be identified.
- Install the capture snippet on the website, either through the site header in the content management system or through a tag manager such as Google Tag Manager.
- Choose a handoff method: hidden form fields that receive the stored values on submission, or a small script that reads the cookie and passes the values onward. The script option is useful for social sign-up buttons that bypass a standard form.
- Send the enriched records from the CRM or backend system into Looker, then build dashboards for leads, sales opportunities, customers, pipeline and revenue by channel or campaign.
Pre-reporting checklist
Use this checklist before trusting a Looker breakdown: confirm every campaign link carries UTM values; confirm the snippet fires on all relevant pages; submit a test form and check that UTM and channel fields arrive in the CRM; move to a different page before submitting to confirm cookie persistence; standardise source naming so variants such as Facebook, facebook and fb do not split one source into three; and record the landing page and its section so content performance can be reviewed alongside channel performance.
What fuller capture adds
Beyond raw UTM values, a fuller capture approach also classifies visitors arriving without UTM parameters, including Direct, Referral, Organic Social and Organic Search traffic. That broader coverage makes it possible to account for every lead and customer rather than only tagged advertising visits. It also records the landing page and the page category, such as a blog section, so individual pages and whole site sections can be compared.
| Handoff option | How it works | Best fit |
|---|---|---|
| Hidden form fields | Stored UTM values are written into form fields and submitted with name, email and other entries | Standard website forms |
| Read the stored cookie | A small script retrieves UTM values and passes them to backend tools | Social sign-up buttons and other non-form conversions |
Options as described in the source; actual implementation depends on the owner's forms, CRM and Looker connection.
Frequently asked questions
Why do UTM parameters need to be collected before Looker can report on them?
Looker reports on data it receives, so UTM values must first be captured on the website, stored with the visitor, and passed through a CRM or backend system where leads and revenue are recorded. Once those records reach Looker, channels and campaigns can be compared against leads, opportunities, customers and revenue.
What are the two ways to pass stored UTM data into backend tools?
Hidden form fields let the capture tool write stored UTM values into a submission alongside name and email. Reading the stored cookie with a small script is an alternative that also works when signup happens through Google or Facebook buttons rather than a conventional form.
Why can inconsistent UTM naming distort Looker reports?
Raw values can fragment reporting when the same source is written as Facebook, facebook or fb. Grouping variants into a consistent channel such as Paid Social prevents one source from appearing as several separate sources in Looker.
How does cookie storage help when a form is not on the landing page?
Storing the values in a browser cookie preserves them when a visitor moves from a campaign landing page to a separate quote or contact page. Without that persistence, a form on a different page may have no UTM values to submit.