Lawmatics knows which leads hired you. Your ads don't.
Lawmatics pulls your Google and Meta spend in and shows cost per client inside the CRM, but nothing flows back out. Google Ads keeps optimizing on form fills, and Meta keeps optimizing for more Instant Form submissions, including the DUI inquiry from three states away. We send Hired matters back to each ad platform, matched to the original click.
Free30 minutesNo obligation
Lawmatics · what breaks
What goes wrong with Lawmatics and paid ads
- 01
Google Ads thinks every intake form is a client
The conversion fires on the form or its redirect page, while Lawmatics marks only a fraction of those matters Hired. Smart Bidding chases the cheapest form fillers: spam, wrong practice area, out of state.
- 02
The ROI dashboard is right, but Google can't see it
Lawmatics' Google Ads sync is one-way. Spend and campaigns come in, nothing goes out, so your cost per signed client lives in Lawmatics while the algorithm spending your budget never sees it.
- 03
Matters land with no source, or the wrong one
The pixel reads only utm_source and utm_campaign, needs an exact case-sensitive match, and only works on native embedded Lawmatics forms. Gravity Forms, linked forms, Zapier and API leads skip it.
- 04
LSA callers counted twice
If CallRail and the Local Services Ads lead sync both log the same phone leads, one caller can land as two records. Lawmatics recommends against syncing through both, and while both stay on, cost per lead in Analytics looks better than it is.
Lawmatics · the fix
What changes — Lawmatics
Google bids toward signed clients
Hired matters go to Google Ads as offline conversions with the stored GCLID and Actual Value, so personal injury and family law budgets shift toward searches that become retainers.
Meta learns which Instant Form leads were real
Qualified and Hired stages go back to Meta server-side, so leads intake rejected stop shaping your audiences.
One answer in Lawmatics and in the ad accounts
Source and campaign rules fixed at the root, so Lawmatics Analytics and each ad platform agree over the same closed month.
Lawmatics · architecture
What Lawmatics actually lets you hook into
All of this comes from Lawmatics' help center. Where the docs go quiet, we test instead of assuming.
- 1
Tracking pixel plus embedded custom forms
Placed on the page with the form. Reads utm_source and utm_campaign only, and only for native Lawmatics forms embedded on your site.
- 2
GCLID stored on the matter
Lawmatics captures the GCLID from Google Ads leads provided one is available and shows it in Matter Custom Reports. We confirm it on a live lead.
- 3
Google Ads and LSA integration
One-way: spend and selected campaigns flow in, and LSA messages, bookings and calls sync hourly. No conversion upload.
- 4
Meta Ads integration
Instant Form submissions create matters and spend syncs, for one ad account at a time. Lawmatics doesn't document Pixel or Conversions API events going back to Meta.
- 5
Zapier and outbound webhooks
Zapier pairs Lawmatics triggers with a Google Ads offline conversion action. Webhooks need Premium, send only the matter_id and can't be replayed after 7 failed tries.
Lawmatics · diagnose
Where Lawmatics tracking breaks, in diagnostic order
We start upstream, because a Hired upload can't match a click whose GCLID never reached the matter.
- 01
Is the pixel on the page that holds the form?
A pixel on one template and the form on another loses the UTMs.
- 02
Does a tagged test lead land with source, campaign and GCLID?
Submit from an ad-style URL and open the matter.
- 03
Are leads arriving outside native embedded forms?
Gravity Forms, linked forms and Zapier-created matters bypass the pixel.
- 04
Is one caller arriving through both CallRail and the LSA sync?
A week of calls shows it.
- 05
What is Google Ads bidding on today?
If it's a form fill, signed cases aren't in the signal.
- 06
Does every intake person use Hired the same way?
Inconsistent habits make the upload noisy.
Lawmatics · prove
The QA evidence — Lawmatics
Checked against matters your intake team actually converted, not a sandbox.
Source of truth
Lawmatics matters: Hired date, Actual Value, source, campaign and GClid from a Matter Custom Report
- A tagged test lead with source, campaign and GCLID confirmed on the matter.
- One valued Hired conversion per matter in Google Ads, matched by GCLID.
- Qualified and Hired events confirmed in Meta Events Manager.
- A re-run conversion on an already Hired matter confirmed not to upload twice.
- CallRail and LSA callers confirmed as one matter each.
- Every Hired matter in a closed month matched to a conversion or marked non-paid, then rechecked 30 days later.
Lawmatics · free audit
What we check in the free audit
- Is the pixel on the page that holds the form?
- Does a tagged test lead land with source, campaign and GCLID?
- Are leads arriving outside native embedded forms?
- Is one caller arriving through both CallRail and the LSA sync?
- What is Google Ads bidding on today?
- Does every intake person use Hired the same way?
Checked against
Lawmatics matters: Hired date, Actual Value, source, campaign and GClid from a Matter Custom Report
Free30 minutesNo obligation
Lawmatics · when not to buy
When you don't need this on Lawmatics
Some firms need a settings fix, not a build.
- If you only run Local Services Ads, the hourly lead sync already attributes them, and there are no click IDs to send back.
- If most of your signed cases come from referrals, the paid signal is too small to steer bidding.
- If you bid manually and only want cost per client, the Lawmatics Analytics page covers it once spend sync and match values are right.
- If the only fault is a mistyped UTM match value, fix it in Marketing Settings yourself. We'll point to the field.
Lawmatics · what we deliver
The event map on Lawmatics
Embedded form submitted
A native Lawmatics form, with UTMs and GCLID captured onto the matter. Secondary signal, never the bidding target.
Call from a tracked number
Logged through the CallRail integration and counted once, with any overlap with the LSA phone sync resolved first.
Consultation booked
The appointment in Lawmatics, a mid-funnel signal for campaigns without enough signed cases yet.
Qualified matter
Intake has confirmed practice area and jurisdiction. Spam, wrong-area and out-of-state inquiries stop here.
Hired
The matter converted to Hired. The primary conversion, valued from Actual Value, sent to Google Ads by GCLID and to Meta from the server.
Never counted
Duplicates matched by email or phone, referrals, existing clients, and a second conversion run on a matter that was already Hired.
Written guarantee
95%+ tracking accuracy
Measured against Lawmatics matters: Hired date, Actual Value, source, campaign and GClid from a Matter Custom Report. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Lawmatics questions, answered
Not natively; the Google Ads integration only pulls spend and campaigns in. Conversions go out through Zapier or the matter.converted webhook plus code calling the Google Ads API, both using the GCLID stored on the matter.
The pixel only reads UTMs for native Lawmatics forms embedded on your site, and only utm_source and utm_campaign with an exact, case-sensitive match. Leads from linked forms, Gravity Forms, Zapier or the API need those values passed another way.
Not through the Lawmatics integration, which brings leads and spend in and doesn't document sending events back. We send qualified and Hired stages to Meta from the server so it can learn from intake's decisions.
Zapier works for plenty of firms. The webhook needs a Premium plan and an endpoint, sends only the matter ID, and can't replay failures, so we add logging and a status check.
Hired, valued from Actual Value, once a campaign signs enough cases to learn from. Until then we usually bid on qualified matters or booked consultations and keep form fills as secondary.
More on Lawmatics
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Lawmatics, and what their bookings feed
- SmartAdvocateSmartAdvocate shows which intakes signed. Google Ads never hears about it.
- Case StatusYour clients love Case Status. Your ads still can't tell who signed.
- Clio GrowClio Grow conversion tracking that counts signed clients, not form fills
- Lead DocketLead Docket shows which sources sign cases. Your ad accounts still don't.
- GavelYour Gavel bundles sell. Google Ads says they don't.
- Law RulerLaw Ruler shows who signed. Your ad accounts still think every intake won.
- Assembly NeosNeos shows which intakes became cases. Google Ads never finds out.
- LitifyLitify knows which callers signed. Your ads don't.
Free · 30 min
Send your signed Lawmatics cases back to your ads
Free30 minutesNo obligation
