Clio Grow conversion tracking that counts signed clients, not form fills
Google Ads and Meta report a steady stream of leads, yet only a few of them ever reach Hired in your Clio Grow Pipeline. The ad platforms can't see that gap: they stop at the page holding your intake link, so they keep bidding on anyone who fills in a form. We carry the ad click into each Grow lead and send every matter that reaches Hired back to Google and Meta, so your budget follows signed cases.
Free30 minutesNo obligation
Clio Grow · what breaks
What goes wrong with Clio Grow
- 01
"Google says the leads are pouring in. We aren't signing them."
Your ads count the inquiry, but Hired only exists in your Grow Pipeline. Smart Bidding optimizes toward whatever you count as a conversion, so it keeps buying inquiries from callers you'd never take.
- 02
The intake form lives on Clio's page, not yours
A public Grow intake form is a link you paste on your site. Once a prospect clicks through, your site tags lose them, and unless the click ID is passed along, the new matter has no record of the ad.
- 03
Marketing source is whatever your staff picks
Clio fills in the source automatically only for its Local Services Ads integration. Otherwise staff pick it by hand, unless an API integration sets it. "Google" in a dropdown can't tell you which campaign produced a retained divorce or DUI client.
- 04
Paid and unpaid consults take different roads
Clio Scheduler sends unpaid bookings to the Leads inbox and paid ones straight into the Pipeline. Track one path and your consult count is quietly wrong.
Clio Grow · the fix
What changes — Clio Grow
Google and Meta learn which leads became clients
Each matter that reaches Hired goes back to the ad click that started it, valued from the matter's projected value, so bidding favors the searches that sign.
Every intake path accounted for
Your own form posts the click ID and UTMs into Grow. For hosted intake forms and Scheduler links, we test whether they can take the click on your account, and move that path onto your own form if they can't.
Your Grow reports and your ad reports agree
For leads we post through the API, source and campaign are set from the actual ad, and we confirm they carry through to the Matter Revenue Report's first-touch and campaign columns so those line up with spend.
Clio Grow · architecture
What Clio Grow actually lets you hook into
Clio documents three marketing hooks for Grow: the Local Services Ads integration, a Google Analytics ID field in its WordPress plugin, and a GA4 connection on Grow AI's website chat. None of them sends hired matters to Google Ads or Meta. What Clio does document is enough to build that loop properly.
- 1
Lead Inbox API
POST a lead with a required referring_url and from_source; the newer Grow API version also takes an optional marketing source and campaign. The landing URL, click ID and UTMs go into referring_url.
- 2
Clio Grow API: matters
Read matters updated since a given time. Each returns status category, hired date, projected value and its originating inbox lead.
- 3
Public intake forms and Scheduler links
Hosted on Clio and linked from your site. Whether a click ID can be passed into them is tested on your account, never assumed.
- 4
WordPress plugin
Accepts a Google Analytics ID and a thank-you redirect, but its form fields are fixed, so there's no documented slot for a click ID.
- 5
No Zapier for Grow
Clio says its Zapier integration works with Clio Manage only, so Grow automation runs through the API.
Clio Grow · diagnose
Where Clio Grow tracking breaks, in diagnostic order
Start at the handoff from your site to Clio, because that's where the ad click usually disappears.
- 01
Click your own ad and submit a test lead
Open it in Grow. No click ID on the referring URL means nothing downstream can be matched.
- 02
List what fires a conversion today
Often it's the click on the link to Clio's form, not the finished submission, so the ad platforms count intent, not leads.
- 03
Follow paid and unpaid Scheduler bookings separately
One lands in the inbox, the other in the Pipeline. Both should count once.
- 04
Compare Hired matters with reported conversions
By hired date, over a closed month, with LSA leads split out.
- 05
Check source and campaign on recent hires
Blank or guessed sources mean your Matter Revenue Report credits the wrong channel.
Clio Grow · prove
The QA evidence — Clio Grow
Every check runs on your live site and real Grow account, using a test lead you delete afterward.
Source of truth
Clio Grow matters with a Hired status category, counted by hired date, with projected value and the originating inbox lead
- A test lead from a tagged ad URL, with the click ID visible on the Grow inbox lead.
- That lead accepted, moved to Hired, and recorded exactly once in Google Ads and once in Meta.
- A paid and an unpaid Scheduler booking each traced to the right event.
- Ignored and spam leads confirmed absent from every platform.
- Hired matters reconciled one by one against platform conversions for a closed month.
- The same reconciliation repeated 30 days later.
Clio Grow · free audit
What we check in the free audit
- Click your own ad and submit a test lead
- List what fires a conversion today
- Follow paid and unpaid Scheduler bookings separately
- Compare Hired matters with reported conversions
- Check source and campaign on recent hires
Checked against
Clio Grow matters with a Hired status category, counted by hired date, with projected value and the originating inbox lead
Free30 minutesNo obligation
Clio Grow · when not to buy
When you don't need this on Clio Grow
Some firms are better off leaving Grow exactly as it is.
- If your paid leads come only through Local Services Ads inside Grow, Google already ties them to the ad and bills per lead. There's no click to carry.
- If you sign only a handful of cases a month, the ad platforms won't get enough hires to learn from. Optimize to accepted leads and revisit later.
- If you don't run Google or Meta ads and your bankruptcy or immigration clients come by referral, Grow's referral and source fields already answer your question.
- If your team never moves matters to Hired or Not hired, fix that habit first. We can't send outcomes that aren't recorded.
Clio Grow · what we deliver
The event map on Clio Grow
Lead received in Grow
From your own form through the Lead Inbox API, with the landing URL and click ID stored in referring_url, plus Grow AI chat and phone leads. Public intake forms skip the inbox and create a matter directly. Tracked, not bid on.
Lead accepted as a matter
Quick Intake or Add contact. The qualified-lead signal; ignored, spam and "Not a lead" items never fire.
Consultation booked
A Clio Scheduler appointment, with paid consults reported separately from unpaid ones.
Matter hired
The primary conversion: status category becomes Hired, dated by hired date, valued from projected value.
Revenue confirmed (Grow plus Manage)
For firms that convert matters to Clio Manage, we confirm whether collected fees can adjust the value later.
Excluded on purpose
Not hired matters, conflicts, existing clients' new matters, and Local Services Ads leads, which Google already bills and attributes.
Written guarantee
95%+ tracking accuracy
Measured against Clio Grow matters with a Hired status category, counted by hired date, with projected value and the originating inbox lead. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Clio Grow questions, answered
Clio documents Local Services Ads inside Grow, plus a GA4 connection on Grow AI's website chat that it says links chat leads back to the ad click. Nothing documented sends hired matters to Search or Performance Max campaigns, so that return trip is built with the Grow API and Google's offline conversion import.
Clio doesn't document a way to add your own tags to hosted intake forms or Scheduler pages, and we confirm that on your account. Your site tags see the click toward the form, not the submission, so we take outcomes from Grow's records.
The click ID is stored with the Grow lead. When the matter is marked Hired, we upload it as an offline conversion with hashed contact details, and Meta gets the same hire through the Conversions API.
It fills your inbox, but its fields can't be changed. We usually swap it for your own form posting to the Lead Inbox API so the click ID comes along.
The projected value your team enters on the matter, so a contingency personal injury case and a flat-fee estate plan report different amounts. If you convert matters to Clio Manage, we check whether collected fees can correct it later.
More on Clio Grow
- Clio PaymentsYour ads count consult requests. Clio Payments knows who actually paid the retai…
- Clio → Google AdsConnecting Clio to Google Ads
- Clio → MetaConnecting Clio to Meta Conversions API
RELATED GUIDES
Booking tools beside Clio Grow, and what their bookings feed
- Assembly NeosNeos shows which intakes became cases. Google Ads never finds out.
- GavelYour Gavel bundles sell. Google Ads says they don't.
- Law RulerLaw Ruler shows who signed. Your ad accounts still think every intake won.
- Lead DocketLead Docket shows which sources sign cases. Your ad accounts still don't.
- IntakerIntaker shows you every chat. Your ads can't tell which ones signed.
- SmokeballSmokeball conversion tracking: your ads count form fills, Smokeball counts signed clients
- LitifyLitify knows which callers signed. Your ads don't.
- LawmaticsLawmatics knows which leads hired you. Your ads don't.
Free · 30 min
See which Clio Grow leads your ads really paid for
WhatsAppFree30 minutesNo obligation
