Smotrów Design is a global design and technology company. Our commitment
- office@smotrow.com
- Smotrow Signature
- Smotrów Related
- Local time: 12:37 AM
Smotrów Design is a global design and technology company. Our commitment
This article explains what to measure, how to set it up, and why analytics is an architectural discipline, not a reporting afterthought.
Every law firm with a website has some form of analytics installed. Usually Google Analytics. Usually set up during the initial build. Usually never properly configured beyond the default. The result is a dashboard that shows pageviews, sessions, and bounce rate - metrics that tell the firm almost nothing about whether the website is actually working.
The managing partner asks: "Is the website generating clients?" The marketing team opens Google Analytics and sees 3,000 sessions last month. But they cannot answer the question. They do not know which of those sessions came from someone looking for legal services versus someone who stumbled on a blog post. They do not know which practice area pages generate the most inquiries. They do not know whether the contact form on the redesigned contact page performs better than the old one. They do not know which publications lead visitors to submit an inquiry versus which ones are read and forgotten.
This gap is not a tool problem. It is an architecture problem. The data a firm can collect is determined by decisions made when the website is designed and built - how forms capture data, how events are tracked, how URLs are structured, and how the website connects to the CRM. These are not analytics configurations. They are architectural decisions.
At Smotrów Design, we build the analytics data layer into every law firm website from the start - not as a post-launch addition, but as a core component of the technology architecture. This article explains what that means in practice.
This article is part of our series on designing websites for law firms, which includes guides on five key elements of a law firm website, homepage content, attorney profile pages, practice area pages, contact page design, photography, website SEO, CRM integration, website technology, lead generation, publications and insights, GEO and AI visibility, how to choose a website design agency, international law firm websites, the About page, website migration, and when to approach a redesign.
Not all metrics are equally valuable. The standard analytics dashboard shows dozens of data points. For a law firm, only a handful directly inform business decisions.
These are the metrics that answer the managing partner's question: is the website generating clients?
The total number of contact form submissions is useful, but it becomes actionable only when broken down by practice area. If the Banking & Finance practice page generates fifteen inquiries per month and the Litigation page generates two, the firm knows where the website is working and where it needs attention. This requires the contact form to capture which practice area the inquiry relates to - a design decision made when the contact page is built.
Which page was the visitor on when they decided to submit an inquiry? Was it the practice area page, an attorney profile, a publication, or the contact page directly? This data reveals which content drives conversions - not just which content gets read.
On mobile, tapping a phone number is a conversion event. Tracking these clicks (via event tracking on tel: links) captures inquiries that never touch the contact form. For many law firms, phone calls outnumber form submissions.
If the firm offers online booking (as we described in our CRM integration guide), each completed booking is a high-value conversion event that should be tracked separately from general form submissions.
The full journey: which channel brought the visitor (organic search, direct, referral, social), which pages they visited, and which action they took. This is the metric that connects marketing investment to client acquisition. In GA4, this requires properly configured conversion events and attribution modeling.
These metrics indicate whether the website's content is working - even when visitors do not convert immediately.
How long do visitors spend on practice area pages versus attorney profiles versus publications? Low engagement time on a practice area page suggests the content is not resonating. High engagement time on publications suggests the firm's thought leadership is working. This data is more useful when segmented by page type than as a site-wide average.
A visitor who enters through a publication and then visits a practice area page and an attorney profile is demonstrating the exact navigation pattern that the site's internal linking architecture is designed to produce. Tracking pages per session by entry point reveals whether the architecture is working.
Which publications generate the most traffic, the longest engagement time, and the highest rate of onward navigation to practice area pages? This data directly informs the firm's content strategy - as we described in our guide to the publications section, the Insights section should be a strategic asset, not a random collection of posts.
Which attorneys attract the most profile views, and from which sources? A partner whose profile is viewed fifty times per month from organic search is generating personal brand equity. A partner whose profile is viewed twice per month may need better content, more publications linked to their profile, or stronger internal links from practice area pages.
These metrics indicate whether the website's technical performance is supporting or undermining the user experience.
Largest Contentful Paint (LCP), First Input Delay (FID), and Cumulative Layout Shift (CLS) - the metrics Google uses to evaluate page experience. These directly affect search rankings and are reported in Google Search Console. For law firm websites, the most common LCP issue is unoptimized hero images, and the most common CLS issue is fonts loading after content renders. Both are technology stack decisions.
Mobile performance is typically 30-50% slower than desktop. If the firm's practice area pages load in 1.5 seconds on desktop but 4.5 seconds on mobile, over 60% of visitors are getting a degraded experience. Monitor this by device type, not as a site-wide average.
Monitor Google Search Console for coverage errors. After a website migration, 404 monitoring is critical - any broken URL represents lost authority and a poor user experience.
A visitor who lands on an attorney profile from a Google search, reads the contact email, and calls the firm has "bounced" in analytics terms - but has converted in business terms. Bounce rate without context is misleading.
A high pageview count driven by bot traffic, internal visits, or irrelevant blog posts tells the firm nothing about business performance. Pageviews only matter when segmented by page type and user intent.
Averaging a five-minute publication reading session with a thirty-second contact page visit produces a meaningless number. Always analyze duration by page type.
This is the central argument of this article. The quality of the analytics data a firm collects is not determined by the analytics platform. It is determined by architectural decisions made when the website is designed and built.
If every publication on the site lives under /insights/ and every practice area page lives under /practices/, GA4 can automatically segment traffic by content type using page path rules. If URLs are inconsistent or flat (everything at the root level), segmentation requires manual tagging for every page. Clean, hierarchical URL structures - planned during information architecture, not after launch - make analytics dramatically more useful.
A contact form that captures only name, email, and message produces a CRM record with no context. A form that also captures (through hidden fields invisible to the visitor) the page URL the form was submitted from, the practice area the page relates to, UTM parameters from the traffic source, and a session identifier that connects to GA4 gives the firm a complete picture of how the inquiry originated. These hidden fields are architectural decisions built into the form component - not GA4 configurations.
GA4 is event-based - every meaningful user interaction must be explicitly defined as an event. For law firm websites, the essential events include form submission (by form type: contact, consultation booking, newsletter), phone number click (tel: link), email click (mailto: link), attorney profile view, publication scroll depth (did the visitor read 25%, 50%, 75%, or 100% of the article?), practice area page view (distinguished from general pageviews), and file downloads (vCard, PDF profile). These events must be configured in the website's code or through Google Tag Manager during development. They cannot be retroactively applied to historical data. A site that launches without proper event tracking has no way to recover the data it missed.
A headless CMS like Strapi structures content as typed objects with explicit fields and relationships. Every publication has an author field (linked to an attorney), a practice area field (linked to a practice), and a content type field (legal alert, analysis, guide). When the frontend renders these objects, it can pass the structured metadata to GA4 as custom dimensions - automatically classifying every pageview by author, practice area, and content type without manual tagging.
This means the firm can answer questions like: "Which author's publications generate the most onward navigation to practice area pages?" or "Which content type (legal alerts vs. analysis vs. guides) produces the highest engagement time?" These insights are impossible without the CMS-to-analytics pipeline that is built during development.
The ultimate measure of a law firm website's effectiveness is not traffic or engagement - it is clients. Connecting the website's analytics to the CRM closes the loop: the firm can track a visitor from their first search query, through the pages they visited, to the form they submitted, to the CRM record that was created, to the consultation that was booked, to the engagement that was signed.
This end-to-end tracking requires the form to pass source data to the CRM (hidden fields), the CRM to store the website source data alongside the client record, and the firm to periodically reconcile CRM data with analytics data to calculate true conversion rates by channel, page type, and practice area. Without this integration, the website and the CRM operate as separate systems - and the firm can never answer the question "how many clients did the website generate this quarter?"
GA4 is the standard analytics platform for law firm websites. The default installation tracks pageviews and some automatic events. For meaningful law firm analytics, additional configuration is required.
Define conversion events: form submission, phone click, consultation booking. These should be marked as "key events" in GA4 so they appear in conversion reports. Create custom dimensions: page type (practice area, attorney profile, publication, contact), practice area, author, content type. These dimensions allow segmentation that the default reports cannot provide. Configure cross-domain tracking if the firm uses separate domains for different offices or services. Set up data filters to exclude internal traffic (the firm's own IP addresses), bot traffic, and staging environment traffic.
Link GA4 with Google Search Console to see which search queries drive traffic and how those queries connect to on-site behavior. This integration is essential for evaluating SEO performance and GEO effectiveness - the firm can see not just which keywords rank, but which keywords drive engagement and conversions.
For sites where direct code modification is complex (particularly WordPress sites with multiple plugins), Google Tag Manager provides a management layer for event tracking. For modern frameworks like Next.js, event tracking is typically implemented directly in the application code - which is more reliable, more testable, and easier to maintain alongside the rest of the codebase.
Check for technical issues: 404 errors in Search Console, sudden drops in traffic, event tracking failures. These are early warning signals that something has broken - particularly important in the weeks following a website migration.
Review conversion metrics: total inquiries, inquiries by practice area, inquiries by source. Compare to the previous month and to the same month last year. Identify trends - is a specific practice area generating more inquiries? Is organic traffic growing? Are publications driving onward navigation?
Conduct a deeper analysis: which pages generate the most valuable inquiries (those that convert to engagements)? Which traffic sources produce the highest-quality leads? Which publications should be updated or expanded based on performance data? This analysis should inform the firm's content strategy for the next quarter - as we described in our guide to the publications section, publishing decisions should be data-informed, not arbitrary.
Compare year-over-year performance across all key metrics. Calculate the website's contribution to client acquisition. Use this data to evaluate the website's ROI and to inform decisions about redesign timing, content investment, and technology updates.
The default GA4 installation tracks pageviews and a few automatic events. Without custom event tracking, conversion definitions, and content classification, the data is too generic to inform business decisions. Configuration must happen during the website build, not months later.
Sessions, pageviews, and bounce rate are easy to report but difficult to act on. The only metrics that matter to firm leadership are those that connect website activity to client acquisition. If the monthly analytics report cannot answer "how many inquiries did the website generate, from which practice areas, through which channels?" - it is measuring the wrong things.
The website shows 50 form submissions last month. The CRM shows 12 new matters opened. Are these connected? Without integrated tracking, the firm cannot know whether the website is generating the clients who become matters - or just generating noise.
If the firm's attorneys, staff, and developers are not excluded from analytics, the data is contaminated. A partner checking the website three times a day inflates pageview counts and distorts engagement metrics. IP filters and internal traffic identification should be configured at launch.
A firm that redesigns its website without first documenting analytics performance has no way to evaluate whether the new site performs better or worse. As we covered in our migration guide, the pre-migration audit must include a complete analytics baseline.
Analytics is not a reporting tool. It is a feedback system that tells the firm whether its website is achieving its purpose - attracting the right visitors, engaging them with relevant content, and converting them into clients. The quality of that feedback is determined not by the analytics platform, but by the architectural decisions made when the website is designed and built: how URLs are structured, how forms capture data, how events are tracked, how the CMS classifies content, and how the website connects to the CRM.
The firms that treat analytics as an architectural discipline - building the data layer into the website from the start, not configuring it as an afterthought - are the firms that can answer the questions that matter. Not "how much traffic did we get?" but "which practice areas generate the most valuable inquiries, through which channels, from which content?"
This article is part of our series on designing websites for law firms. For guidance on specific pages and elements, explore our guides on homepage content, practice area pages, attorney profile pages, contact page design, photography, website SEO, CRM integration, website technology, lead generation, publications and insights, GEO and AI visibility, how to choose a website design agency, international law firm websites, the About page, website migration, and when to approach a redesign. For a broader perspective, start with five key elements of a law firm website.
