How to Capture UTM Parameters in Clio
If your law firm runs Google or Facebook ads, the ad platforms can report impressions and clicks but not which of those clicks became paying clients. Capturing UTM parameters in Clio closes that gap: each new lead can arrive with the campaign and landing-page context that brought them in. This guide walks through the four setup steps, explains what the hidden fields contain, and shows how to turn the resulting data into useful reports.
What you are actually building
The setup has three moving parts. First, a small script on your website reads the UTM parameters on the visitor's first landing page and stores them in the browser. Second, your lead-capture form includes hidden fields that receive those stored values. Third, your form tool passes the completed submission, including the hidden values, into Clio.
The important design choice is the browser storage step. Without it, attribution only survives if the visitor submits a form on the same page they landed on. With it, a visitor who clicks an ad, lands on your homepage, browses to a service page, and then submits a contact form still carries the original campaign data into Clio.
Four setup steps
- Install the tracking script on your website. The script captures UTM parameters when a visitor arrives and keeps them in the browser for later form submissions.
- Add hidden fields to your lead-capture forms. The fields used in this setup are: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Most form builders let you drag a hidden field type into the form.
- Let the script populate the hidden fields. When a visitor submits a form, the stored UTM data is written into those fields automatically.
- Pass the submission into Clio. Your form tool sends the lead's name, phone number, other form details, and the hidden attribution values to Clio, where you can view them or build reports.
What the hidden fields contain
The channel fields describe where the lead came from at increasing levels of specificity. A paid search lead might show Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign, and Channel Drilldown 3 = a specific ad or account name.
The landing-page fields describe the first page the visitor saw. Landing Page might hold a full URL such as a corporate-law services page, while Landing Page Group holds the broader section, such as services. Together, the two sets of fields let you separate the acquisition channel from the content that first attracted the visitor.
Setup checklist before you go live
- Confirm the tracking script is present on every page that can receive campaign traffic, not only the homepage.
- Confirm each lead-capture form contains all six hidden fields with names that match what your form tool expects.
- Submit a test form after arriving through a tagged URL, then check that the hidden values appear in the form submission record.
- Confirm the form tool's connection to Clio includes the hidden fields, not only the visible contact fields.
- Check that a visitor who lands on one page and submits a form on another still carries the original UTM values.
Worked example: two capture methods, one visitor journey
Take a visitor who clicks a Meta ad for a family-law consultation. The ad's destination URL carries a campaign tag and points to a practice-area page. The visitor reads that page, opens the site menu, moves to a separate consultation-booking page, and submits the form there.
Under a same-page-only capture method, the booking page has no campaign tag in its URL, so the submission record shows no source. The lead reaches Clio as an unattributed contact, and the Meta campaign gets no credit for it.
Under browser-stored attribution, the tag from the practice-area page was saved when the visitor first arrived. At submission time the form's hidden fields are filled from that saved record: the channel resolves to Paid Social, the drilldowns identify the platform and campaign, and the landing-page fields point back to the practice-area page rather than the booking page. The Clio record now answers two separate questions — which campaign produced the lead, and which page first earned the visitor's attention.
Two different failures to diagnose
If the hidden fields are empty on the form submission, the problem is usually upstream: the script is missing from the landing page, the UTM parameters were stripped by a redirect, or the visitor arrived without campaign tags. If the hidden fields are populated in the form tool but the values do not appear in Clio, the problem is downstream: the form-to-Clio connection is not mapping those fields. Checking the form submission record first tells you which side of the setup to investigate.
Why channel grouping matters more than raw UTM strings
Raw UTM values are only as consistent as your tagging habits. Consider a firm whose older Google Ads links use utm_medium=adwords while newer ones use utm_medium=ppc. A tool that stores raw strings sees two unrelated sources, and someone has to merge them by hand before the firm can state how many leads Google Ads produced.
A channel-grouping layer sidesteps that bookkeeping. Each lead is assigned to a predefined channel — Paid Search, Organic Search, Paid Social, Organic Social, Referral, and so on — even when the underlying tags differ. Monthly channel totals stay comparable, and the drilldown fields still preserve the finer detail for anyone who needs it.
Four reports worth building first
Leads by Channel answers a capacity question: across a given month, how is new-lead volume distributed among your acquisition sources? It is the report to open when you want to know whether the mix is shifting, not just whether one campaign worked.
Leads by Facebook Ads Network answers a placement question. Meta can serve the same campaign across Facebook, Instagram, Messenger, and WhatsApp, and this breakdown shows which of those surfaces is actually producing inquiries for your firm — useful when you are deciding where to concentrate creative effort.
Customers by Google Ads Campaign answers a quality question. Clicks and form fills are not the same as retained clients, and this report separates campaigns that generate signed clients from campaigns that generate activity. Budget and testing decisions can then follow the campaigns that convert.
Revenue by Keyword answers a search-term question, provided the keyword is included in your Google Ads UTM parameters through a tracking template. It links specific search terms to leads and revenue, giving you evidence for both paid bidding priorities and the topics worth targeting organically.
What to decide before you start
Decide which forms count as lead-capture forms and whether every one of them will receive the six hidden fields. Decide who will check a test submission after setup and who will review channel totals each month. Decide whether keyword-level reporting matters to your firm; if it does, plan the Google Ads tracking template before campaigns accumulate untagged history. These decisions are more important than the installation itself, because they determine whether the data in Clio stays complete and comparable over time.
Frequently asked questions
Do UTM parameters survive if the visitor submits a form on a different page from the one they landed on?
Yes, when the tracking script stores the values in the visitor's browser. The stored values are written into the hidden fields at the point of form submission, so the original campaign data is preserved even after the visitor navigates to another page.
Which hidden fields need to be added to the form?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Most form builders let you add these by dragging a hidden field type into the form.
What is the difference between Channel and Channel Drilldown fields?
Channel is the broad source category, such as Paid Search or Organic Social. The drilldown fields add specificity beneath it, such as the ad platform, the campaign, or the specific ad or account.
Why would two Google Ads links appear as different sources?
If one link uses utm_medium=ppc and another uses utm_medium=adwords, a raw-string capture method treats them as separate sources. A channel-grouping layer assigns both to Paid Search so the totals stay comparable.
How do I know whether the problem is on the form side or the Clio side?
Check the form submission record first. If the hidden fields are empty there, the issue is upstream in the script, the landing page, or the tagging. If the values are present in the form tool but missing from Clio, the issue is in the form-to-Clio field mapping.