How to get UTM parameters into Domo
Domo dashboards are only as reliable as the data behind them. If UTM and channel information never reaches your CRM or warehouse, campaign reporting in Domo will be incomplete. This guide explains a four-step flow that captures attribution on the website, stores it with each lead, and makes it available for Domo reports on leads, customers, pipeline and revenue.
How capture works before Domo reporting
A website capture snippet works much like the code used for web analytics. On each visit it examines technical signals, including UTM parameters in the URL, to work out where the visitor came from. It then groups the visit into a channel such as Paid Search or Organic Search and stores that attribution in a browser cookie. When the visitor submits a form, the stored UTM, channel and landing page data can travel with the lead into a CRM or warehouse, from where Domo can read it. That makes questions answerable in Domo such as how many customers a social campaign produced, how average deal size differs between two ad platforms, and what return a campaign delivered.
Four steps to get UTM data into Domo
Step 1: Add UTM variables to every ad and campaign, across social networks, search engines and other placements such as trade publications, so each visit carries a recognisable origin. Step 2: Install the capture code on the website. After signup a snippet is provided, similar in style to analytics code; it can usually be added through the site builder's settings header area, or through a tag manager such as Google Tag Manager or Tealium. Step 3: Move the stored data out of the cookie and into your backend tools, using hidden form fields or JavaScript cookie retrieval as described below. Step 4: Connect Domo to the CRM or warehouse and build dashboards covering leads, customers, sales opportunities and revenue by channel and campaign.
Two ways to pass attribution into your CRM
Hidden fields give the capture code a destination inside the form, so attribution is submitted together with the visitor's name, email and other lead details. Reading the cookie with a small piece of JavaScript achieves the same handover without relying on visible form structure, and it is the recommended route when sign-up can happen through Google or Facebook buttons instead of a conventional form. In both cases the goal is identical: attribution must be saved against the lead record, not left only in the browser.
Reports Domo can then support
Once attribution sits beside customer records, Domo reporting can answer practical questions: how many leads a Twitter campaign generated, which LinkedIn campaign produced the most leads or pipeline, how many sales opportunities and customers came from Facebook Ads, and how much revenue SEO delivered. The same dataset supports comparisons across channels rather than isolated campaign counts.
Why fuller attribution beats raw UTM capture
Capturing raw UTMs alone misses visits without parameters. A fuller approach also records Organic Search, Direct, Referral and Organic Social traffic, so every lead has an origin. Cookie storage also solves a common loss point: a visitor may land on a campaign page, browse elsewhere, and only later reach a quote or contact form on a different page. Because the values persist in the cookie, they survive that journey. Cleaner grouping helps too — variants such as Facebook, facebook and fb can be recognised as one Paid Social channel instead of three competing sources. Finally, landing page and landing page group are captured alongside UTMs, so Domo can show whether a whole section such as a blog, or one individual post, is generating leads, customers and revenue.
Pre-reporting checklist
Before building reports, run this check: every campaign carries UTMs; the capture code is present on all pages; a test visit from a tagged link converts on a different page and still arrives in the CRM with its channel; a non-UTM visit is also attributed; inconsistent source spellings roll up to one channel; and landing page data is present on the lead record. If any check fails, fix that stage first — Domo cannot report on data that never reached the warehouse.
| Approach | How it works | Best fit |
|---|---|---|
| Hidden fields | Attribution is written into the form and submitted with lead details such as name and email | Standard lead capture forms |
| Cookie retrieval with JavaScript | Attribution is read from the browser cookie and passed to backend tools | Sites with Google or Facebook sign-up buttons and no conventional form |
Comparison of the two handover methods described in the source workflow.
Frequently asked questions
What are the four steps to analyse UTM parameters in Domo?
Add UTM parameters to every ad and campaign, install the capture code on the site, pass the stored attribution data into your CRM or warehouse through form fields or cookie retrieval, then connect Domo to that system for reporting.
Which is better: hidden fields or reading the cookie?
Hidden fields write the data into the form submission alongside name and email. Retrieving it from the cookie with JavaScript is recommended when visitors can sign up with Google or Facebook without completing a form.
Does this only work for paid campaigns with UTMs?
No. Attribution can also be recorded for Organic Search, Direct, Referral and Organic Social visits that carry no UTM parameters, so every lead has a channel.
What happens if the form is on a different page from the landing page?
Storing the values in a browser cookie preserves them across pages and sessions, so a visitor who lands on a campaign page and converts on a later form page is still attributed correctly.
How are messy UTM values handled?
Inconsistent values such as Facebook, facebook and fb can be recognised and grouped under one channel, such as Paid Social, instead of appearing as three separate sources.