Can you measure website inquiries without tracking visitors?
Start with a reliable inquiry record and search data. Add visitor tracking only when a specific decision needs it and the privacy work is justified.

An accounting firm asks whether its new website is working. The dashboard shows visits, but the partner still cannot tell whether anyone found the right service, sent an inquiry, or became a suitable client. Another owner has no dashboard at all and assumes there is nothing to measure.
You can measure the useful part of a service website without following each visitor around it. Keep a dependable record of genuine inquiries, check whether the contact route works, and use aggregate search data to see which pages people find. Add visitor analytics only when you can name a decision that those simpler measures cannot support. A visit, a button click, an inquiry, and a client are different events.
This is a measurement choice, not a claim that all tracking is harmful or that a tool is legally exempt. The right setup depends on the information collected, the business, and the applicable privacy rules.
Begin with the business question
Write down what the website is meant to help someone do. For a bookkeeper, that may be understanding the services and requesting a first conversation. For a repair shop, it may be checking service availability before calling. The useful question is then concrete: Are suitable customers reaching us through that path, and where does it fail?
Define an inquiry before counting it. A form submission, call, or email can be a new inquiry if it comes from a distinct prospective customer about a service you offer. A test message, spam, duplicate follow-up, or existing customer’s routine question belongs in another category. Decide who records the source when it is known, who marks an inquiry as suitable for follow-up, and when the team closes it. Do not equate a submitted form with a qualified lead or a sale.
A small shared register can hold the date, service requested, broad source such as website or referral, contact channel, owner, and next step. Keep only the personal details the team needs for that work, restrict access, and follow the business’s retention policy. Ask “How did you hear about us?” when it is useful, but allow “not sure” rather than forcing a confident answer. Someone may search for the company after a referral, so even an honest answer can describe several touchpoints.
What national data can and cannot tell you
Statistics Canada reported that 17% of businesses collected customer or client information through web tracking technologies, a third party, or data mining in 2021. This is a combined category, not a web tracking rate. The underlying Survey of Digital Technology and Internet Use covered Canadian enterprises in most sectors with at least five employees; it does not describe every sole proprietor. It also does not say which approach produced better inquiries. The figure is useful here because it makes the collection choice visible: installing a tool can change what information a business gathers, while a site can still be assessed from the inquiries it receives.
There is no national conversion rate in that figure to apply to your site. Your own inquiry definitions, contact-path tests, and customer conversations are more useful for deciding whether a page needs work.
Use search data for discovery, not client outcomes
If you control the site, set up Google Search Console’s Performance report for the correct property. It shows impressions and clicks from Google Search, with views by page, query, country, and date. Look at whether the service pages you care about appear for relevant searches and whether people click through. A click from Google is not a measured inquiry, and Search Console does not cover every way someone reaches your site.
Treat small query lists carefully. Google omits some queries for privacy and limits displayed rows, so a table of visible queries is not a complete list of people or searches. Compare like periods and pages, and annotate major changes such as a new page or seasonal closure. If a page is discovered but the team receives no relevant inquiries, inspect the offer and contact route before assuming the title needs another keyword.
You can also note where the contact action appears on a page, whether it works on a phone, and whether it gives a clear next step. Those are observations the team can test directly. They do not require a pixel that follows visitors across sites.
Test the contact route like a customer
Send a safe test inquiry from a phone and a desktop browser. Check the confirmation, the message that reaches staff, the reply address, and the handoff to the person who will respond. If the business serves customers in English and French, test both paths. Repeat after changes to the form provider, email routing, or site. A form can render correctly while its notification goes to an unmonitored inbox.
Ask someone who has not worked on the site to find the right service and contact method. Watch where they hesitate. Can they tell what information to prepare, whether the business serves their location, and what happens after they write? Our guide to clear service pages helps with the page itself; the contact accessibility guide helps when the form is only one of several paths.
Record a failed test as a problem to fix, not as a visitor conversion statistic. If staff cannot receive an inquiry, a low dashboard number may hide a broken handoff. If the firm receives many irrelevant requests, better service wording or routing may help more than more traffic.
Decide when analytics earns its place
Visitor analytics can help answer a narrower question, such as which parts of a multi-step booking path people reach before stopping. First write the decision you would make from that evidence. Then ask what event data is necessary, whether a less intrusive test would answer it, who will review the report, and when the collection will end or be reassessed. An unused dashboard adds maintenance and privacy work without improving a decision.
Do not treat a click event as proof that a person completed a request. If you measure form completion, verify that the event fires only after the server accepts the submission and that failures are visible to the team. If you compare channels, keep the source rules consistent and disclose when attribution is unknown. A call from a search result or a later direct visit may never appear in a website event report.
For a Québec business, the Commission d’accès à l’information explains that collecting personal information by website brings transparency duties, and technologies that identify, locate, or profile people require prior information and a means for people to activate those functions; they cannot be on by default. Review the actual tool and configuration with a qualified privacy adviser when needed. A label such as “anonymous analytics” does not settle what the tool collects or which rules apply.
Read the measures together
At a regular review, put the evidence side by side: relevant search visibility, working contact paths, new inquiries, suitable inquiries, and what happened after follow-up. Look for a change you can explain and test. A page with many clicks and few suitable inquiries may be attracting the wrong question, offering unclear service details, or sending people to a broken form. A page with few clicks but good referrals may be doing its job for a small audience. Neither pattern proves a redesign is needed by itself.
For a bookkeeping practice, the first improvement might be a clearer description of who it serves and what a first inquiry should include. The practice can test that wording and review the next set of inquiries before adding any tracking. If the decision later depends on a detailed journey through a portal or booking flow, a developer can map the minimum events and a privacy specialist can review collection and notice. This is an illustrative process, not a result from a client project.
The owner can start with the inquiry register and a contact-path test. Professional help becomes useful when several forms, languages, booking tools, or reporting systems need to agree on what counts as a completed request. If you are planning a service website around that path, see Red Comet’s website services and bring your inquiry definition to the conversation.
Sources
- Statistics Canada, What happens with your personal contact information when you share it with Canadian businesses?, published January 6, 2023; based on the 2021 Survey of Digital Technology and Internet Use.
- Statistics Canada, Digital technology and Internet use, 2021, survey population and methods.
- Google Search Console Help, How are you performing on Google? and Dimensions and data groupings.
- Commission d’accès à l’information du Québec, Collecte de renseignements personnels.

