Websites & AI Search · Build · Published Nov 19, 2026
Law Firm Website Analytics: The GA4 Key Events That Matter
For owners and office managers whose GA4 shows visitors but cannot say whether anyone asked for help: the five key events to track, the setup in order with an owner for each step, and the tracking bug we found on our own site.
Law firm website analytics should count the actions that lead to a consultation, not just visits. In GA4 those are key events, and a standard property can mark up to 30 (Google Analytics Help, 2026). Most small firms need five: form lead, phone tap, booking click, booking confirmed, download. Mark them, test them, then check them monthly against intake.
Key takeaways
- Google defines a key event as one that "measures an action that's particularly important to the success of your business" (Google Analytics Help, opened Nov 19, 2026).
- Marking a key event is not retroactive: it "doesn't change historic data" (Google). Set them up before you need the numbers.
- We set up our own key events on Oct 27, 2026; before that, none had been defined (first-party, GA4).
- Our download-form lead event did not fire until a fix on Nov 14, 2026; it was confirmed firing on the live site on Nov 19 (first-party). Test every event.
- In Clio's 2024 secret-shopper test, 40% of firms answered calls, down from 56% in 2019 (Clio, Oct 7, 2024, vendor). A counted inquiry still needs an answer.
Get the free scorecard
Which GA4 key events should a law firm track?
Five, each tied to a step toward a consultation. Google's recommended event for a lead form is generate_lead, which "measures when a lead has been generated (for example, through a form)" (Google Analytics developer reference, opened Nov 19, 2026). The other four are custom events with plain names. Four of the five are the names we use on our own site; phone_click is the one we recommend for firms that publish a phone number.
| Event name | Fires when | Useful parameters | Key event? |
|---|---|---|---|
| generate_lead | A contact or consultation form is submitted | form_name, lead_type | Yes |
| phone_click | Someone taps a tel: link | link_text | Yes |
| book_call_click | Someone clicks the scheduling link | link_text | Yes |
| booking_confirmed | The scheduling tool returns the person to a thank-you page on your site | booking_source, booking_campaign | Yes |
| kit_download | A guide or template file is downloaded | file_name | Yes |
Leave the value and currency parameters empty. Google notes "value is typically required for meaningful reporting" in ad and revenue reports, but a firm judging its website needs counts and sources, not a dollar figure per inquiry. GA4's enhanced measurement can also send form_submit "when the user submits a form" and file_download for links to files such as PDF, DOCX and XLSX (Google Analytics Help, enhanced measurement). Use those as a cross-check; the five named events above are what you star.
Why do visits alone mislead?
Because a visit count cannot tell a firm whether the site produced a single consultation. A spike can be bots, one shared article, or people who read and leave. Google now separates the two ideas: "Events that measure actions that are important to the success of your business are now called 'key events,'" while "A 'conversion' now refers to an important action that you want to use to measure the performance of your ad campaigns" (Google Analytics Help, conversions vs key events). A firm without paid ads needs only key events.
The key event is also only half of the story. When Clio's researchers posed as prospective clients in 2024, "Of the 500 law firms emailed, only 33% responded, a drop from 40% in 2019," and 48% of firms were "essentially unreachable by phone" (Clio, Oct 7, 2024, vendor study). Analytics tells you an inquiry arrived; only intake turns it into a consultation.
How do you set up key events, step by step?
In this order, because each step depends on the one before. Allow an afternoon for a site with a developer or a tag manager, plus a week of watching.
| Step | Owner | Where | Where it breaks |
|---|---|---|---|
| 1. Send the five events | Web developer | Site code or Google Tag Manager | Form host changes the form markup the script looks for |
| 2. Test each one live | Web developer | Admin, DebugView, with Tag Assistant | Testing one form and assuming the rest work |
| 3. Star them as key events | Owner or office manager | Admin, Data display, Events, star icon | Starring before the event has fired once, so it is not listed |
| 4. Exclude your own visits | Office manager | Admin, data filters (Internal traffic) | Leaving the filter in Testing |
| 5. Stop the scheduler stealing credit | Office manager | Web data stream settings (unwanted referrals) | Bookings credited to the scheduling site instead of the source |
| 6. Link Search Console | Owner | Admin, Product links, Search Console Links | No verified owner on the Search Console side |
| 7. Keep 14 months | Owner | Admin, data retention setting | Year-over-year comparisons in explorations vanish at 2 months |
- Test before you trust. "DebugView displays the events and user properties that Analytics collects from a user in real time" (Google). Submit every form on the site once and watch each event arrive.
- Star once listed. Under Admin, Data display, Events, click the star; a standard property allows 30 key events and Analytics 360 allows 50 (Google). Reports count from that moment.
- Filter internal traffic. Once a data filter is active, Google says "the effect on the data is permanent" (Google), so run it in Testing for a week first.
- Mark the scheduler as an unwanted referral. Google built the setting for sites whose visitors leave for a third-party page and come back (Google); a booking page works the same way.
- Link Search Console. You need "the Editor role on the Google Analytics property" and verified ownership in Search Console; the data arrives "48 hours after it is collected" and covers up to 16 months (Google).
- Set retention to 14 months. Standard properties offer 2 or 14 months; the setting "only affects explorations and funnel reports," not standard reports (Google).
Worked example: our own key events, Jul to Nov 2026
Worked example from FirmFooting's own site (first-party, dates from our setup log). We installed GA4 and Microsoft Clarity on Jul 22, 2026. Our Oct 22 review found that no key events had been defined; only GA4's default lead events existed, and our site never sends them. We added book_call_click, generate_lead and kit_download on Oct 27, and a booking_confirmed event plus an internal-traffic tag on Nov 13.
Then the lesson. On Nov 14 we found that generate_lead had never fired from our download forms since Oct 27. Our form host removes a marker attribute from forms when it serves the page, and our script looked for that marker, so it skipped every form. The lead events GA4 did record came only from thank-you pages. The fix was to detect forms by a hidden field the host keeps, and the event was confirmed firing on the live site on Nov 19, 2026. We had tested one form, not every form. Step 2 in the table exists because of this.
The free Law Firm KPI Scorecard has intake lines and twelve weeks of trend. Add the monthly generate_lead count next to inquiries logged by intake.
How should you read the numbers each month?
Compare GA4 with the intake log, every month, in one table. GA4 undercounts (a reader who phones from another device) and overcounts (test submissions), so treat it as a pattern detector and the intake log as the record. A gap of a few is normal; a gap that grows is a broken event or a broken inbox.
| Line | Source | Sample month | What to do if off |
|---|---|---|---|
| Form leads in GA4 | generate_lead count | 14 | Check DebugView on each form |
| Form entries received | Form host or inbox | 17 | Find which form is silent |
| Booking clicks | book_call_click | 9 | None; context only |
| Bookings confirmed | booking_confirmed | 5 | Check the scheduler redirect |
| Inquiries in intake log | Intake log, all sources | 23 | The record of truth |
| Replied same business day | Intake log | 20 of 23 | Review the 3 with the intake owner |
Read the sample row by row: 17 form entries against 14 GA4 leads means one form is probably silent, which is exactly what happened to us. The 23 intake inquiries include phone calls GA4 never sees.
Privacy: what should never reach GA4?
Names, emails, phone numbers and matter details. Google's policy asks that "no data be passed to Google that Google could use or recognize as personally identifiable information (PII)," and warns that "PII is often inadvertently sent in these URLs and titles" (Google Analytics Help). Scheduling tools often add the person's name and email to the thank-you page address, so our booking page strips the whole query string before analytics loads. Send event names and form names only. The attorney approves what the site collects and the privacy policy that describes it; check your state's privacy rules.
What differs for immigration, family and PI firms?
Immigration firms often run forms in more than one language: give each its own form_name so a silent Spanish form is visible. Family law firms should keep form names neutral ("contact") and never put case types in page titles that analytics records. Personal injury firms live on phone calls, so phone_click matters most, and the intake log matters more than any event.
Mistakes to avoid
- Testing one form. Fix: submit every form once after any site change and watch DebugView.
- Starring too many events. Scrolls and page views as key events bury the real ones. Fix: five, no more.
- Counting your own clicks. Fix: an internal traffic filter, tested first.
- Trusting GA4 over intake. Fix: the monthly reconciliation above, with the intake log as the record.
What to do this week
- Open GA4, Admin, Events, and write down which events are starred today.
- Ask your developer to send the five events in the table, with the names shown.
- Submit every form once with Tag Assistant open and confirm each event in DebugView.
- Star the five, link Search Console and set retention to 14 months.
- Add the reconciliation to the first business day of each month.
By the numbers
| Figure | Value | Source |
|---|---|---|
| Key events per standard property | 30 (360: 50) | Google Analytics Help |
| Data retention options, standard | 2 or 14 months | Google Analytics Help |
| Search Console data in GA4 | Up to 16 months, after 48 hours | Google Analytics Help |
| Firms answering calls, secret shopper | 56% (2019), 40% (2024) | Clio, 2024 (vendor) |
| Firms responding to email | 40% (2019), 33% (2024) | Clio, 2024 (vendor) |
| Key events defined before Oct 27, 2026 | None | FirmFooting GA4 (first-party) |
| Days our form lead event was silent | 18 (Oct 27 to Nov 14) | FirmFooting setup log (first-party) |
Frequently asked questions
What are key events in Google Analytics 4?
Key events are the events you mark as important to the business, such as a form submission or a booked consultation. Google renamed them from conversions; "conversion" now refers to measuring ad campaign performance.
Which GA4 key events should a law firm track?
Five: generate_lead for form submissions, a phone tap, a scheduling link click, a confirmed booking, and a guide or template download. Keep the list short so the important actions are easy to see.
How do I mark an event as a key event in GA4?
In Admin, under Data display, open Events and click the star next to the event. The event must have fired at least once to be listed. Marking counts from that moment and does not change historic data.
Should a law firm link Google Search Console to GA4?
Yes. It adds the search queries and landing pages behind organic visits. You need the Editor role in GA4 and verified ownership in Search Console, and the data arrives about 48 hours after Search Console collects it.
Why does GA4 show fewer leads than my inbox?
Usually a form that does not send its event, a visitor who phones instead, or a blocked tracking script. Submit every form once with DebugView open, then compare GA4 with the intake log each month.
Sources
- Google Analytics Help, "Conversions vs. key events in Google Analytics." support.google.com
- Google Analytics Help, mark events as key events. support.google.com
- Google Analytics developer reference, recommended events (generate_lead). developers.google.com
- Google Analytics Help, enhanced measurement events. support.google.com
- Google Analytics Help, Search Console linking. support.google.com
- Google Analytics Help, data retention. support.google.com
- Google Analytics Help, "Best practices to avoid sending Personally Identifiable Information (PII)." support.google.com
- Google Analytics Help, "Filter out internal traffic." support.google.com
- Google Analytics Help, "Identify unwanted referrals." support.google.com
- Google Analytics Help, "Monitor events in DebugView." support.google.com
- Clio, Legal Trends Report release, Oct 7, 2024 (vendor). prnewswire.com
- FirmFooting GA4 setup history, Jul 22 to Nov 19, 2026. First-party. All Google pages opened Nov 19, 2026.
Where to go next
- Law firm website and AI search library
Every website guide.
- The website intake closed loop
What happens after the event fires.
- AI assistant referrals: how to track them
The channel these events sit beside.
- The owner's Five-Number Friday
Where the monthly count belongs.
Count the inquiries, then answer every one
Get the free Law Firm KPI Scorecard to put key events next to intake numbers, or book the free Missed-Deadline Risk Audit to find where inquiries and dates slip. When the site needs rebuilding with these events built in, Client Door is FirmFooting's website build, wired to intake.