Measure calls and CRM records, not sessions
Written by AERVIO, a Montreal studio. Human-reviewed before publish. Contact: hello@aervio.io · +1 438-498-3913.
The number worth reviewing every week is how many real conversations started, and from which page. Not sessions, not pageviews, not time on site. A session count tells you that a browser loaded your site. It does not tell you whether the phone rang, whether the form posted, or whether a person on your team replied before the buyer called a competitor.
Most Montreal companies we talk to already have a dashboard. It is usually accurate and usually irrelevant to the decision in front of the owner. Traffic is up 18%, and nobody can say whether anyone called.
Why sessions mislead small teams
Sessions are easy to collect, so they get reported. They also respond to things unrelated to business: a bot wave, a seasonal blog spike, an email blast to your own list, a page that ranks for a question nobody buys from.
Three common traps:
- Traffic that cannot buy. A guide ranking for a definition term can add thousands of sessions and zero enquiries. That is not a failure of the guide. It is a failure of using sessions to judge it.
- Traffic you cannot attribute. Direct and "unassigned" can hide half the visits that matter, especially when someone reads on a phone and calls from another.
- Averages over small numbers. If you receive 12 enquiries a month, a 30% change in sessions is noise. A change in who gets a reply inside a business day is not.
We are not anti-analytics. We are anti-reporting that never touches the pipeline. The smallest tracking that can answer "which URL started this CRM record" is usually enough. This is the same logic behind our growth retainers: measure the thing that started the conversation, then ship the next change.
The four measures we start with
- Conversations started. Calls answered, calls missed, forms posted, emails received, each as a record with a source URL.
- Response time. Median time from enquiry to first human reply, in business hours. A page that generates leads nobody answers is a cost, not a win.
- Stuck conversations. Records open more than five business days with no next step. This is where revenue leaks quietly.
- Source URL, not channel. "Organic" is a channel. `/services/seo-geo` is a page you can edit, and the page is what you can improve next month.
Everything else is context. Search Console queries explain why a page was found. Speed and uptime explain why a form may have failed. None replace the four above.
Calls are the hard one, and the one that matters
For many local and B2B services in Quebec, the phone is still the conversion. Pretending otherwise inflates the form numbers and hides the real pattern.
A workable setup for a small team:
- A click-to-call event on mobile, fired when a visitor taps the number
- A tracked number on pages where call volume matters, with a plain-language note about why
- A call-notes field in the CRM filled in by whoever answers: name, topic, source if the caller mentions it
- A missed-call rule: anything unanswered gets a callback task, assigned to a named person
This is boring on purpose. A more elaborate call-intelligence tool can be worth it later. Early on, a note in the CRM beats a dashboard nobody opens.
Forms: count the post, not the page view
A thank-you page view is a weak signal. Redirects break, tags fail, someone refreshes. The reliable event is the record created in the CRM, with the landing URL, the language of the page, and the consent timestamp. That is why we prefer to connect the site, the CRM, and search as one system instead of running three vendors with three versions of the truth.
If your form still sends an email to a shared inbox, you are not measuring it. You are hoping. Start there.
What a useful weekly view looks like
Short enough to read in two minutes on a Monday:
| Question | Where the answer lives |
|---|---|
| How many conversations started last week? | CRM, by created date |
| Which three URLs started the most? | CRM source field |
| How many waited longer than one business day? | CRM, first-reply timestamp |
| Which queries brought the people who actually enquired? | Search Console, matched to the landing URL |
| Did anything break? | Form post log and uptime check |
Notice what is absent: bounce rate, average session duration, pages per visit. They can be useful to a developer diagnosing a page. They should not run the meeting.
Rules we hold ourselves to
We do not promise rankings, and we do not pretend a small sample is a trend. If a page generated four conversations last month and six this month, the honest statement is that it is promising and worth watching. We do not build a strategy on it.
We also keep consent proportional. If you run tags, we keep them few, documented, and aligned with Law 25. Ad platforms get the conversions they need to optimise, and not a copy of every field in your CRM. Nothing here requires a consent-banner maze or a tag manager with sixty entries.
For more on how search visibility fits this picture, our SEO and GEO approach in Montreal uses the same measure: a page earns its place by starting conversations a person could have, not by looking busy in a chart.
What to do this week
You do not need a new tool. You need one agreement and one table.
- Agree on what counts as a conversation for your business: a call longer than a minute, a form with a phone number, a quote request.
- Make sure each one becomes a record with a source URL somewhere you can export.
- Look at last month. Count conversations by URL. Count the ones that waited more than a business day.
- Pick the page with the most unanswered or stuck conversations, and fix the follow-up before the page.
If the data is not there yet, that is the first project, and a small one. Send a note to hello@aervio.io or call +1 438-498-3913, weekdays 9–17 ET, with read-only access to your analytics and a description of how enquiries arrive today. We will tell you what can be measured this month, what needs a small build, and what to ignore. Our growth retainer exists for the weeks after launch when this becomes the Monday habit.
Questions
Do we have to stop using Google Analytics?
No. Keep it if the team reads it. We just stop treating sessions as the result. The weekly number is conversations started in the CRM, with the source URL attached.
How do you measure phone calls from a website?
A tracked number on the pages that matter, a click-to-call event, and a call log that lands in the CRM with the landing URL. Small companies often start with a simple call-notes field filled in by whoever picks up.
What if our sales cycle is six months?
Then the meeting looks at stage movement rather than closed revenue. The question stays the same: which pages started conversations that are still alive, and which started ones that went cold.
Read next
Let's write the next step.