Why calls and chats go uncounted
Analytics records what happens in the browser. A form submission is an event on a page, so it arrives with the session's source and campaign attached. A phone call happens on a telephone network after the visitor has left the page, or without a visit at all when the number came from a van, a leaflet or a business listing. A chat happens inside a widget that often runs in its own frame or on another company's domain, and a message sent through a messaging app leaves the site entirely. None of these reaches the analytics property unless someone builds the bridge.
The result is a measurement plan that sees part of the demand. Mobile visitors from local search tap the number instead of filling the form, so mobile looks like it converts badly. Campaigns that make the phone ring look expensive per lead. The troubleshooting page on marketing that is not generating leads lists uncounted enquiries as a cause of apparent decline, and the quickest test is the one it suggests: compare the report with the count kept by the people answering the phone. If the two differ widely, the reports are measuring how people choose to get in touch, not how much demand marketing created.
The lead generation measurement plan already lists calls as a capture surface with a row in its specification. This guide fills in that row: what to count, how to attribute it, how to record it and how to judge it.
What to count as an enquiry
Calls and chats produce several signals, and only some of them are enquiries. Decide the definitions before choosing a tool, because the tool will happily count everything.
| Signal | What it shows | Where it is recorded | Treat it as |
|---|---|---|---|
| Tap on a phone link | Intent to call from a mobile page | Analytics event | A diagnostic, not an enquiry |
| Number revealed or copied | Weaker intent; often a desktop visitor | Analytics event, where the site has a reveal button | A diagnostic |
| Call connected | A call reached the business | Call tracking system or phone log | A raw count, reported beside the enquiry |
| Missed call | A caller nobody answered | Call tracking system or phone log | A service failure with a cost |
| Qualified call | A call that meets the business's written rule | Call tracking system, then the CRM | The enquiry |
| Chat started | A visitor opened or replied to the chat | Chat widget event in analytics | A diagnostic |
| Chat lead | A chat that captured a request and contact details | Chat system, then the CRM; analytics event | The enquiry |
| Messaging conversation | A conversation opened through a messaging link | The messaging account; the CRM when a lead is created | The enquiry once a request is recorded |
The qualification rule deserves the most thought. A minimum call length is the common proxy, and the geo-targeted campaigns guide recommends setting one for local advertisers so that hang-ups and wrong numbers do not inflate results. Duration is still only a proxy: a long call can be a complaint and a short one can be a booking. Where the people answering can record an outcome (new enquiry, existing customer, supplier, wrong number, sales call), the outcome is the better rule, and the duration becomes a fallback for calls nobody classified. Whatever the rule, write it into the measurement plan with its owner, because a rule that lives only in a tool's settings will change without anyone noticing.
Only the enquiry rows should become key eventsA GA4 event marked as important to the business, the property's measure of success. or platform conversions. The key events guide explains why a short list of meaningful events beats marking every interaction; a phone tap marked as a key event is the call equivalent of counting page views as leads.
Attributing calls to a source
There are four ways to connect a call to the marketing that caused it, and they answer different questions.
| Method | How it works | What it answers | Where it falls short |
|---|---|---|---|
| One number per channel or campaign | Each channel, printed piece or listing shows its own forwarding number | Which channel produced calls, including offline ones | Coarse; people save numbers and keep using them long after a campaign ends |
| Numbers swapped per visit | A script on the site shows each visitor a number from a pool and links the call to that visit's source | Which campaign, keyword or landing page produced website calls | Only covers callers who visited; a pool too small for the traffic misattributes calls; depends on consent for the tracking it relies on |
| Ad platform call features | The ad platform supplies a number in the ad or on the site and counts calls from its own ads | Calls from that platform's ads | Each platform sees only its own ads, so totals overlap |
| Asking the caller | The person answering asks how the caller found the business and records the answer | Referrals, word of mouth, the van, the recommendation | Memory is imperfect; needs discipline on every call |
Most businesses combine them. A number per offline channel covers vans, print and listings; numbers swapped per visit cover the website; asking covers everything else and checks the other two. Agree with whoever owns local listings before putting a tracking numberAttributing phone calls to the marketing source that produced them, usually by showing different tracking numbers per source or visitor. on a business profile, because listings depend on the business's details being consistent across the web. The tutorial on measuring Google Business Profile results picks one count of record for the profile's calls and sets it beside the profile's own performance data.
Ad platform call features need a separate word. Google's documentation on conversion tracking lists phone calls among the actions it can count, alongside website actions, and the local ads guide describes the forwarding number and the minimum call length that make those counts usable. Their set-up belongs to the Google Ads conversion tracking guide. For measurement design the point is that a platform's call count is that platform's claim: a caller who clicked a search ad, saw a social ad and then rang the number on the van may be counted by two platforms and by the van number. Reconcile the total against the phone log, not by adding the platform figures together.
Attributing chats and messages
A chat on the website starts inside a session that already has a source, so attribution is easier than for calls if the chat events reach analytics. Record the chat with the same discipline as a form: an event when the visitor starts a conversation, and a separate event when the chat captures a request and contact details, with parameters for the page and the type of request. Google's documentation describes events as the way analytics measures specific interactions, and the events and parameters guide recommends one event with a parameter over many near-identical events, so a single lead event with a method parameter (form, chat, call) keeps every enquiry in one report. Widgets that run in their own frame or on another domain often need the chat provider's own callbacks or a data layer push to expose those events; test them in preview before trusting the counts.
Messaging links (a button that opens a conversation in a messaging app) and chat sessions handled outside the site need the source carried with them. Two approaches work. Tag the links that lead to the conversation with campaign parameters, following the naming convention, and record the click as an event. And where the messaging app allows a prefilled first message, include a short reference for the campaign or page, so that the person handling the conversation can record the source in the CRM. The conversation itself is invisible to analytics; the click and the CRM record are the two ends of the bridge. When message ads run beside instant forms, the comparison of click-to-message ads and instant forms shows how to read both routes on the same qualified-lead counts.
Chatbots add a counting trap. A greeting the bot sends to every visitor is not a conversation, and a conversation the bot ends without a request is not an enquiry. Count chats where a person asked for something and left a way to reply. The same counting rules hold inside an experiment such as the product page chat test, which records the arm on every conversation and judges chat on orders per visitor rather than on chats started.
Recording outcomes in analytics and the CRM
A call or chat enquiry needs two records: one that carries its source, and one that follows it to a booked job, a sale or a lost lead. They meet on a shared identifier.
- The identifier. The call tracking system and the chat system each give every conversation an identifier. Write it into the CRM record when the lead is created, alongside the source, medium, campaign, landing page and timestamp, so that a booked job can be traced back to the conversation and the conversation to its source.
- Analytics. Record the on-site steps: the phone tap, the chat started, the chat lead. Mark the chat lead as a key event if chats are a main route for enquiries. Calls themselves stay in the call system, because they happen off the site.
- The CRM. Record every qualified call, chat lead and messaging lead as a lead with its method and source, using the same source fields as web forms so that reports group them together. The CRM connection guide covers capturing campaign values into those fields and sending qualified outcomes back to ad platforms through an Offline Conversion ImportUploading outcomes recorded outside the website, such as closed deals, to an ad platform..
- The combined report. Leads by source and method from the CRM, with booked work and value, beside sessions and spend by source. The join is by source and date, not by person, and the report says so.
Treat the CRM as the place where a call becomes a customer. Analytics can show that a chat started on the pricing page after a paid search visit; only the CRM can show that it became a booked job worth something. Where there is no CRM yet, a shared sheet with one row for each enquiry can play the CRM's part, as the tutorial on keeping an enquiry record sets out.
Quality, response and recordings
Counting calls is half the job; the other half is whether the business answered and converted them. Three measures belong in every review.
- Missed and unanswered calls by hour. A campaign running when nobody answers buys calls the business then loses. Read missed calls by hour and day beside spend, and either staff the hours or schedule the ads.
- Response to chats and callbacks. Lead Response TimeAverage time between a new lead arriving and the first contact from sales. for chat leads and requested callbacks is a service measure that marketing depends on; a slow reply turns a paid enquiry into a lost one. Report it by source, because enquiries from some channels may arrive out of hours.
- Qualified and booked rates by source. The share of calls and chats that met the rule, and the share of those that became booked work, by channel. A channel with many calls and few bookings is a targeting or message problem, not a measurement success.
Recordings and transcripts are useful for checking qualification and training staff, and they are personal data. The GDPR defines personal data broadly, as any information relating to an identified or identifiable person, which covers a caller's voice, name, number and what they said. Its principles of data minimisation and storage limitation apply: record only what the stated purpose needs, decide who may listen, and keep recordings and transcripts no longer than that purpose requires. Whether and how callers are told, and the lawful basis, are questions for whoever owns privacy in the business; this guide is not legal advice. Never send caller numbers, names or transcript text into analytics; the guide to keeping personal data out of analytics explains how such values leak in and how to stop them. A caller's number stored in the CRM is First-Party DataData a business collects directly from its own customers, visitors and users. held under the CRM's access and retention rules, which is where it belongs.
A calls and chats measurement table
The table below is the section of the measurement plan that calls and chats need. Fill the definition column in the business's own words and keep it with the plan.
| Item | Definition to write down | System of record | Reported as |
|---|---|---|---|
| Phone taps | Taps on phone links, by page and device | Analytics | Diagnostic, weekly |
| Calls connected | Calls reaching any tracking number | Call tracking system | Raw count beside enquiries |
| Missed calls | Calls not answered, by hour and day | Call tracking system | Service measure, weekly |
| Qualified calls | The written rule: outcome recorded, or the chosen minimum duration as a fallback | Call tracking system, then CRM | Enquiry, by source |
| Chat leads | Chats that captured a request and a way to reply | Chat system, CRM; analytics event | Enquiry, by source; key event |
| Messaging leads | Conversations from messaging links where a request was recorded | CRM | Enquiry, by source |
| Booked work | Enquiries that became jobs, appointments or sales, with value | CRM | Outcome, by source and method |
| Cost per qualified enquiry | Spend divided by qualified calls, chat leads and forms, per channel | Spend data and CRM | Efficiency, monthly |
| Source check | The caller's own answer to how they found the business | CRM | Cross-check on the tracked source |
The CPA calculator does the arithmetic for cost per qualified enquiry once the counts are right; the hard part is the counts. For a campaign built to make the phone ring or open a conversation, the call and message campaign launch checklist puts these definitions, numbers and CRM fields in place before launch.
Brassfennel Plumbing counts its phone
Brassfennel Plumbing is an invented firm of eight engineers that takes most of its work by phone. Its reports showed 41 form leads a month, and paid search looked expensive at that rate. The firm adds a tracking number for each of four channels (paid search, its business profile, the vans and leaflets, and the website for everyone else), a chat event on the site, and an outcome field the office team fills in on every call. A qualified call is one marked as a new enquiry, or, where nobody marked it, one lasting over 90 seconds.
| Channel | Calls connected | Qualified calls | Chat leads | Form leads | Booked jobs |
|---|---|---|---|---|---|
| Paid search | 168 | 112 | 21 | 17 | 74 |
| Business profile | 104 | 77 | 0 | 0 | 49 |
| Vans and leaflets | 61 | 39 | 0 | 0 | 22 |
| Website, other sources | 72 | 46 | 33 | 24 | 41 |
| Total | 405 | 274 | 54 | 41 | 186 |
Forms were 11% of the month's 369 enquiries. Paid search's cost per enquiry falls from £126 on forms alone to £14 on all qualified enquiries, and its cost per booked job is £29 on £2,150 of spend. The table also shows 37 missed calls between 5pm and 7pm, when the search campaign was still running and the office had closed; the firm moves the ad schedule and sets a callback rule for that window.
Common mistakes
- Counting phone taps as calls. A tap is intent from a mobile page; the call log says whether anyone rang.
- Counting every call as an enquiry. Existing customers, suppliers and wrong numbers inflate the figure and teach bidding systems the wrong lesson.
- Adding platform call counts together. Each platform counts its own calls; the phone log is the total.
- Letting campaign numbers outlive their campaigns. Customers save numbers, so a retired number keeps ringing and needs a home in the reports.
- Ignoring missed calls. Calls nobody answered are enquiries marketing paid for and the business lost.
- Leaving source out of the chat record. Without campaign values on the chat lead, the CRM shows chats as a channel rather than as a method.
- Sending caller details to analytics. Numbers and names belong in the CRM under its access rules, never in event parameters.
- Keeping recordings by default. Recordings and transcripts are personal data; keep what the purpose needs, for as long as it needs it.
The measurement planning hub places this guide beside the measurement plan and tracking plan it extends.
