Your LawLytics site gets the inquiries. Google Ads can't tell which ones signed.
On LawLytics, tracking code goes in through the Support team, the Google Analytics tile is built for traffic reports, and the Facebook connection posts blog articles rather than installing a Pixel. So your ads usually optimize on a page load after a form, counting the spam you later flag beside the divorce consult that retained. We rebuild tracking around the leads you already mark Converted and send those signed cases back to Google Ads and Meta.
Free30 minutesNo obligation
LawLytics · what breaks
What goes wrong with LawLytics and paid ads
- 01
Google Ads counts the spam I flag as a new client
The usual setup fires on the Redirect URL page or response message, before anyone reads the inquiry. Submissions you later Flag Spam have already taught Smart Bidding what a good lead looks like, so it buys more of them.
- 02
I don't know what tracking code is actually on my site
LawLytics routes Google Ads tags, CallRail, chat and scheduling snippets through Support. Years of tickets later, nobody at the firm has a list, and a past agency's tag can still fire beside the new one, doubling every form fill and making your cost per lead look half what it is.
- 03
Facebook is connected, so why is Meta blind?
The LawLytics Facebook integration announces new blog posts on your page. It doesn't install a Meta Pixel or pass leads, so unless someone added a Pixel separately, Meta campaigns for injury or immigration clients optimize for cheap clicks and never see who called back.
- 04
Leads land in three places and none of them talk to the ads
The native form, an embedded Lawmatics or JotForm intake, and chat tools like Intaker or Blazeo each collect leads separately. Some export to Clio or Smokeball, some stay in the LawLytics inbox, and no ad account can say which produced a retainer.
LawLytics · the fix
What changes after we fix it — LawLytics
Bidding learns from retained clients
Leads marked Converted, in LawLytics or in Clio or Smokeball after export, go to Google Ads as offline conversions matched by click ID or hashed email and phone. Estate planning and bankruptcy budgets follow signed matters, not form fills.
Meta gets a real signal
Promoted and Converted leads reach Meta through the Conversions API from a first-party server container, so audiences are built from people intake accepted.
A written map of every tag on the site
Each snippet Support added is listed with its purpose; duplicates and dead agency code come out in one ticket.
LawLytics · architecture
What LawLytics actually lets you hook into
All of this comes from LawLytics' help center. Where it's silent, we list a check, not a claim.
- 1
Google Analytics integration
You authorize Google under Integrations and pick a GA4 property per site; reports then show inside LawLytics. Form submissions as key events aren't documented, so we test them live.
- 2
Tracking code placed by Support
Google Ads tags, call tracking, chat and scheduling snippets are sent to Support to place. Tag Manager isn't named in the help center, so we confirm with Support that a first-party container tag goes in the same way.
- 3
Form builder with a Redirect URL
Each form takes an optional post-submit page, giving every form a clean confirmation URL. Documented field types are text, dropdowns and checkboxes, so we confirm whether a hidden click-ID field works or capture it in the container.
- 4
Lead statuses and native exports
Submissions can be promoted to leads and marked Converted or Lost. Clio, Clio Grow and Smokeball receive submissions natively.
- 5
No conversion API or webhook documented
Nothing in the help center sends conversions to ad platforms, so signed cases reach them through our server setup, fed from your lead list or from Clio or Smokeball.
LawLytics · diagnose
Where LawLytics tracking breaks, in the order we check
Tags first, forms second: on LawLytics most faults were installed by a ticket long ago.
- 01
List every script on the live site
Old agency Google Ads tags and a second GA property are the usual finds.
- 02
Find what the conversion fires on
Response message, Redirect URL page or button click. Each behaves differently once the sidebar form sits on every page.
- 03
Check the cookie banner against the tags
LawLytics' consent banner is one setting. Confirm whether tags wait for consent.
- 04
Follow one test inquiry to the lead record
Is the ad click or source on the submission, or on the Clio Grow lead after export?
- 05
Compare Converted leads with reported conversions
Lead by lead over a closed month, with spam-flagged submissions taken out.
LawLytics · prove
The QA evidence — LawLytics
Run on your live LawLytics domain with a real submission, not in the editor preview.
Source of truth
LawLytics Form Submissions and Active Leads, with each lead's Converted or Lost status (or the matching Clio Grow or Smokeball lead when submissions export there)
- A test inquiry from an ad-tagged URL, with click ID or hashed contact details confirmed.
- One Google Ads conversion per submission, and one Meta event with the same event ID on its browser and server copies.
- A spam-flagged test submission absent from the primary conversion.
- A CallRail call and a chat lead each logged once, under their own source.
- Converted leads matched one by one against each platform over a closed month, then again 30 days later.
LawLytics · free audit
What we check in the free audit
- List every script on the live site
- Find what the conversion fires on
- Check the cookie banner against the tags
- Follow one test inquiry to the lead record
- Compare Converted leads with reported conversions
Checked against
LawLytics Form Submissions and Active Leads, with each lead's Converted or Lost status (or the matching Clio Grow or Smokeball lead when submissions export there)
Free30 minutesNo obligation
LawLytics · when not to buy
When a LawLytics firm doesn't need us
Plenty of LawLytics firms should spend nothing on this.
- If you don't run Google Ads or Meta, the built-in GA reports are enough.
- If you sign only a few clients a month, offline imports carry too little data to steer bidding. Track qualified consultations first; that's a smaller job.
- If every lead already reaches Lawmatics or Clio Grow with click IDs sent back to Google Ads, your intake tool owns tracking.
- If the only fault is a stale tag, ask LawLytics Support to remove it. Don't pay us for a one-line ticket.
LawLytics · what we deliver
The event map on LawLytics
Contact form submitted
The native LawLytics form, page or sidebar version, read on its own Redirect URL page. Secondary, never the bidding target.
Call from a tracked number
From the CallRail or other call tracking snippet, counted once per caller above a duration you set.
Chat or embedded intake lead
Intaker, Blazeo, a Lawmatics or JotForm intake: tagged by source so it never doubles the native form.
Promoted to Lead
A submission moved to Active Leads, or the matching Clio Grow or Smokeball lead. Used while signed volume is thin.
Converted
The primary conversion: a lead set to Converted, sent server-side to Google Ads and Meta, with a fee value where you record one.
Never counted
Spam-flagged submissions, Lost leads, current clients, and the second copy when one person sends both sidebar and page forms.
Written guarantee
95%+ tracking accuracy
Measured against LawLytics Form Submissions and Active Leads, with each lead's Converted or Lost status (or the matching Clio Grow or Smokeball lead when submissions export there). Miss it and we keep working at no cost.
From $400 · See packages
FAQ
LawLytics questions, answered
Usually, through Support. LawLytics has Google Ads, call tracking and chat code sent to its Support team to install, but no help article names Tag Manager, so we confirm it with Support first. Once the container is in, tag changes happen there without new tickets.
Its help article covers connecting a GA4 property for traffic reports and doesn't document form submissions as key events. We test it on a live inquiry and add the event if it's missing.
No. That integration posts your new blog articles to Facebook. A Pixel or Conversions API setup is separate work.
Mark them Converted in LawLytics, or in Clio or Smokeball, then send them to Google Ads as offline conversions matched by click ID or hashed email and phone, which Google calls enhanced conversions for leads.
Yes. LawLytics names CallRail as supported call tracking, installed by Support from the vendor's snippet. The usual fix is one person counted for both a call and a form.
More on LawLytics
- 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 LawLytics, and what their bookings feed
- FindLawFindLaw reports contacts. Which ones became signed cases?
- ProSitesYour ProSites site sends appointment requests. Which ads actually put patients in the chair?
- PBHSYour PBHS report counts leads. Which ads actually bring in consults?
- LinktreeYour ads say people clicked your Linktree. Did anyone book?
- Mitchell 1Mitchell 1 shows you the calls. It can't show which ads filled your bays.
- OfficiteYour Officite portal shows visitors. Which ads actually fill your schedule?
- Ours PrivacyOurs Privacy took the pixels off your site. Now your ads can't tell which clicks became patients.
- Dealer SpikeDealer Spike sends the leads. Your ads can't tell which ones bought a unit.
Free · 30 min
Find out which LawLytics leads your ads paid for
WhatsAppFree30 minutesNo obligation
