A website does more than put a business on the map.
It helps people find a service, learn about it and request a visit. Different tools do different jobs—and send different information.
Start with the owner’s questions.
Google Analytics illustrates measurement. A separate scheduling tool illustrates booking. A booking event appears in analytics only when an appropriate event or integration is configured.
In the visitor’s browser
A visit to the home-services website begins.
A separate analytics provider
Event data can include page context and a pseudonymous identifier.
In the owner’s report
A useful indication of how someone arrived.
A source report helps answer the owner’s question. It does not reveal every person’s search history, and the provider receives more detail than this summary shows.
Technical sourcesSynthetic example. These controls do not read visitor data, send tracking requests, or save information. A report count is not a count of unique customers.
The count is only part of the picture.
The owner can see a simple report while the analytics provider receives more detailed event data. A pseudonymous identifier is not automatically anonymous.
Page context, recipients, settings, consent and later use all matter. An ordinary business purpose does not establish that every setup is harmless.
Why the details matter.
The same label—“analytics”—can describe different data and uses. Court records help explain why a public service page and a sensitive patient portal should not be treated as equivalent.
Read the court examplesFamiliar tools. Different jobs.
Analytics
Measures visits, sources and activity to help an owner understand the website.
A summary report does not show every field received by the provider. Analytics is not automatically a session recording.
Booking
Lets a visitor request an appointment or a service visit.
This is a separate tool. Measuring successful requests needs the right integration or event setup.
Advertising
Helps attribute responses to ads and measure campaigns.
Advertising integrations and matching can add uses or identifiers beyond base traffic reporting.
Session replay
Reconstructs interactions to help identify usability problems.
Recording and masking settings matter. This differs from a simple engagement metric.
Chat and forms
Send a visitor’s question or request to a business or service platform.
What a person writes, the recipient and the sensitivity of the context introduce separate facts.
Some details are worth opening.
What can a basic analytics event include?
Google documents automatically collected events and web parameters including page URL, page title, referrer, language and screen resolution. The data actually sent depends on the implementation. Reports do not reveal a visitor’s name simply because someone loaded a page. Google’s event documentation.
Does a form event contain everything typed into a form?
The documented enhanced-measurement form events include form metadata. That is different from a universal claim that every answer is captured. URLs, other scripts and custom settings can change the flow. Google’s enhanced measurement documentation.
Does rejecting cookies mean no data is sent?
It depends on the setup. Google distinguishes basic consent mode, which blocks tags before consent, from advanced mode, which can send measurements without cookies when consent is denied. This technical distinction does not resolve a particular legal claim. Google’s consent-mode documentation.
Why does the type of page matter?
A public service page is different from a patient portal or a sensitive form. URLs, titles, identifiers and entered information can carry meaning beyond a count. The actual page, fields, recipients and configuration need to be examined. Read a healthcare case example.