Get UTM Parameters Into Good Data for Channel Reporting
Good Data can only report on information that has been captured and stored in a CRM or data warehouse. If UTM parameters and related attribution data are not passed through at form submission, campaign reporting in Good Data will be incomplete. The workflow below captures the visit source on arrival, preserves it for later form submissions, sends it to backend tools, and then makes it available for reports on leads, customers and revenue.
Why capture has to happen before Good Data reporting
Good Data is an analytics platform for building reports and dashboards around the metrics a business cares about. Its limitation is practical rather than visual: it reports on stored data. To answer questions such as how many leads a Facebook campaign generated, which LinkedIn campaigns produced the most pipeline, or how much revenue came from SEO, the UTM parameters a visitor arrived with must first be captured on the website and stored alongside the resulting lead or customer record.
A capture snippet placed on the site checks the landing URL for UTM parameters, categorises the visit 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 data is sent with the lead details to the CRM or other backend tool, from where it can flow into Good Data.
Four-step workflow
- Add UTM parameters to advertising and campaign links. Include them on social ads, search ads and bespoke placements such as trade publications, so the arrival source is identifiable.
- Add the capture snippet to the website. After signup, a small code snippet is provided. Add it in the same way as other marketing or analytics tags — typically through the site header setting in the content management system, or through a tag manager such as Google Tag Manager.
- Send attribution to the CRM or other backend tools. Two methods are described:
- Hidden form fields: the capture tool writes attribution data into hidden fields, and those values are submitted with the name, email and other details the lead enters.
- Cookie recapture: a small piece of JavaScript on the form reads the attribution from the cookie and passes it to backend tools. This also helps when visitors sign up with a social login button without completing a conventional form.
- Build reports in Good Data. Once attribution data is in the CRM or data warehouse, create dashboards sorted by channel or campaign. Useful starting questions include leads per Facebook campaign, sales opportunities from Twitter ads, customers from Google ads, revenue from SEO, and average deal size by paid channel.
What raw UTM capture misses
Capturing raw UTM values alone leaves four gaps that a channel-aware capture tool addresses:
- All traffic, not only tagged campaigns: visits from Direct, Referral, Organic Social and Organic Search can also be attributed, so reporting covers every lead and customer rather than only UTM-tagged traffic.
- Persistence across pages and sessions: because attribution is stored in a cookie, it survives the journey from a landing page to a later form page. A visitor who clicks a Google ad, reads a landing page, then moves to a quote form does not lose the original campaign data.
- Cleaner channel data: inconsistent tagging by different people or agencies — for example Facebook, facebook and fb as source values — would otherwise appear as three separate sources. Mapping those variants to one channel, such as Paid Social, produces more reliable totals.
- Landing page and category: the landing page URL and its category, such as /blog, are captured as well. That makes it possible to compare whole site sections and individual pages by leads, customers and revenue generated.
Pre-reporting checklist
Before building reports, run this check:
- Every paid and campaign link carries consistent UTM parameters.
- The capture snippet loads on all key pages, including landing pages.
- A test visit from a tagged link, followed by browsing to a different form page, still submits the original attribution.
- Hidden fields or cookie recapture are in place on every lead form, including social sign-up options.
- Test submissions appear in the CRM with channel, campaign and landing page values populated.
- Good Data reports group by channel and campaign without duplicate source spellings.
If those checks pass, channel and campaign reporting in Good Data should reflect the full journey from first visit to lead, customer and revenue.
Frequently asked questions
What happens if the UTM parameters are not in the URL when a form is submitted?
No. A cookie-based capture stores the first-visit attribution in the browser, so it can still be passed when the form is submitted on a later page. That matters when a visitor lands on a campaign page, browses elsewhere, and only then clicks through to a quote or contact form.
Can attribution be recorded when there are no UTM parameters?
Yes. Attribution can also be recorded for Direct, Referral, Organic Social and Organic Search visits, so reporting is not limited to campaigns that carry UTM parameters.
Why do raw UTM values create misleading reports?
Inconsistent naming — for example Facebook, facebook and fb — can split one source into several report rows. Mapping variants to a single channel such as Paid Social keeps channel totals cleaner.