Reporting guide
Call tracking dashboard: from raw call counts to cost per qualified call
A call tracking dashboard puts phone calls next to the campaigns, keywords and pages that produced them, so a marketing team or agency can see which spend drives real sales conversations. This guide is for agencies reporting calls to local and service clients, and for in-house teams whose phones bring in more revenue than their forms. It covers the KPIs, the sources, why call counts never match between tools, a worked cost-per-qualified-call example and how to choose between a reporting app and a custom Data Studio build.

Quick answer
What should a call tracking dashboard include?
A call tracking dashboard should show total and qualified calls by source and campaign, answered and missed calls, first-time callers, call duration, cost per qualified call and, where possible, calls that became sales. Call data comes from tools such as CallRail or CallTrackingMetrics, spend from the ad platforms, and outcomes from the CRM.
- Report qualified calls and cost per qualified call, not total call volume.
- Call counts differ between call tracking, Google Ads and GA4 because each uses different rules.
- Missed calls belong on page one, because they look like weak marketing when the problem is staffing.
- Joining calls to ad spend and CRM outcomes is the work that makes the dashboard useful.
What is a call tracking dashboard?
A call tracking dashboard is one report that answers three questions about inbound phone calls: where did they come from, were they worth anything, and what did they cost? Call tracking software assigns a unique number to each source, campaign or visitor, logs every call and passes the source along. The dashboard takes that log and sets it against ad spend and sales outcomes.
The pages that rank for this phrase today are mostly product pages. DashThis, AgencyAnalytics and Databox each sell a ready-made call tracking dashboard inside their own reporting app, and AgencyAnalytics lists integrations with CallRail, CallTrackingMetrics, WhatConverts, WildJar, Twilio and CallSource. Those pages list the same widgets: total calls, average duration, calls by source and a call log. They say little about how a call becomes a qualified lead, why numbers disagree between tools, or how to put a cost on each useful call. That is what this guide covers.
We build these dashboards in Data Studio (formerly Looker Studio). It is free for creators and viewers, connects natively to Google Ads, GA4 and Google Sheets, and the finished report sits in an account you own rather than inside a monthly subscription.
Which KPIs belong on a call tracking dashboard?
Group call KPIs by stage: volume, handling, quality and value. A fall at each stage points to a different team. Fewer calls is a marketing problem. More missed calls is a staffing or routing problem. Many short calls from one campaign is a targeting or ad copy problem. Fewer sales from the same number of qualified calls is a sales problem.
| Stage | KPI | What it tells you |
|---|---|---|
| Volume | Total calls by source, campaign and keyword | Which channels make the phone ring |
| Volume | First-time callers vs repeat callers | New demand vs existing customers calling back |
| Handling | Answered rate and missed calls by hour and weekday | Whether calls are lost before anyone speaks |
| Handling | Average time to call back missed callers | How fast the team recovers lost calls |
| Quality | Qualified calls (by duration, tag or score) | Calls that were real sales conversations |
| Quality | Qualified call rate by campaign | Which campaigns attract buyers rather than browsers |
| Value | Cost per call and cost per qualified call | What each useful conversation costs by channel |
| Value | Calls to sale and revenue from calls | Which spend produces paying customers |
What counts as a qualified call?
A qualified call is one your business would count as a genuine sales enquiry. There is no universal rule, so the dashboard has to state the definition and apply it the same way every month. Most teams use one of three methods, and the best reports combine two.
Duration is the simplest. Google Ads, for example, counts a call from an ad as a conversion once it passes a minimum length, and Search Engine Journal reported in 2018 that the default is 60 seconds, which advertisers can change. Duration filters out wrong numbers and hang-ups but also counts long calls from existing customers and suppliers.
Tags are more accurate. Staff or the call tracking tool mark each call as new lead, existing customer, spam, job seeker or sale. Some call tracking tools also offer automatic tagging or scoring, which still needs spot checks. Tags take discipline, so the dashboard should show the share of calls left untagged, because a report built on half-tagged calls is not reliable.
CRM outcomes are the most useful. When the caller's number or a call ID is matched to a CRM record, the dashboard can report calls that became opportunities and sales. This is the step most call tracking dashboards skip, and it is the one that tells you where to spend.
Where does call data come from, and how does it reach Data Studio?
A call tracking dashboard usually draws on four kinds of source: the call tracking platform, the ad platforms, GA4 and the CRM. Each reaches Data Studio by a different route.
CallRail offers its own Data Studio connector. Its 2020 guide to phone call dashboards describes three default data sources, Calls Summary, Forms Summary and Calls Time Series, with fields such as source, total calls, average duration, missed calls, first-time callers and qualified calls. Other platforms are covered by partner connectors from vendors such as Supermetrics, Coupler.io and Windsor.ai, or by scheduled exports. Vendor prices change, so check them directly.
Data Studio blends are limited to 5 sources and equality joins only, and a blend lives inside one report. For a call dashboard that joins calls, ad spend and CRM outcomes across many clients or locations, we combine the data first in Google Sheets or BigQuery and point Data Studio at one clean table with shared keys: date, channel, campaign and location.
- Call tracking platform: native or partner connector, or a daily export of the call log.
- Google Ads and Microsoft Ads: spend, clicks and the platform's own call conversions.
- Meta and other social ads: spend by campaign through a partner connector.
- GA4: sessions and landing pages for website visitors who later called, where the call tool passes data to GA4.
- CRM: opportunities and closed deals matched by call ID or caller number, written as aggregated counts.
- Mapping table in Sheets: tracking number, source label, campaign and location, so every system uses the same names.
Why do call numbers differ between CallRail, Google Ads and GA4?
They differ because each system counts a different thing. A dashboard that puts the three numbers side by side without explanation will lose the client's trust in the first meeting, so explain the rules on the page.
Google Ads counts calls as conversions only when they pass its minimum duration and only for the call conversion actions you set up, such as calls from ads or website call conversions. It credits the conversion to the date of the ad click, not the date of the call. The call tracking platform logs every call, including repeat callers, short calls and calls from offline sources such as print or vehicle signs. GA4 sees a call only if the call tool sends an event to it, and then applies its own attribution model.
The fix is a definitions panel and one source of truth for each metric. We normally use the call tracking platform for call volume and handling, the ad platforms for spend, and the CRM for sales. Platform-reported call conversions appear on the paid media page as a cross-check, with a note on why they differ.
How do you calculate cost per qualified call? A worked example
Cost per qualified call is the spend on a channel divided by the qualified calls it produced in the same period. It puts search, social and local listings on equal terms, judged on conversations that matter rather than on rings.
Take a hypothetical law firm in one month. These are illustrative numbers, not benchmarks. It spends $8,000 on Google search ads and $4,000 on Meta ads. Search produces 200 calls, of which 90 are tagged as new qualified enquiries. Meta produces 160 calls, of which 40 are qualified, because many callers are existing clients or out-of-area.
On cost per call, Meta looks better: $25 a call against $40 for search. On cost per qualified call the picture reverses: about $89 for search ($8,000 divided by 90) and $100 for Meta ($4,000 divided by 40). Add CRM outcomes and the gap may widen or close: if 18 search callers and 6 Meta callers sign, cost per signed client is about $444 for search and about $667 for Meta. A report that stopped at total calls would have moved budget the wrong way.
In Data Studio these are calculated fields such as SUM(spend) / SUM(qualified_calls), built on a table where spend and calls already share the date, channel and campaign keys. A CASE statement on the call tag field groups tags like 'new lead', 'New Lead - Hot' and 'NL' into one qualified flag before the division.
How should a call tracking dashboard be laid out?
Four or five pages cover most teams. The first page answers the question a manager asks first: how many useful calls did we get, what did they cost, and how many did we miss? Put a date control, a channel filter and a location filter on every page.
Keep personal data out of the shared report. A call log with caller numbers and recordings is useful to the sales team inside the call tracking tool, but a client-facing dashboard rarely needs it. Show aggregated counts by source and tag, and link to the call tool for detail.
- Summary: total calls, qualified calls, missed calls, cost per qualified call and sales from calls, against target.
- Sources: calls and qualified call rate by channel, campaign and keyword, with spend alongside.
- Handling: answered rate and missed calls by hour and weekday, with call-back time.
- Outcomes: calls to opportunities and sales by source, from the CRM.
- Definitions: how a qualified call is defined, which source owns each metric, and why platform numbers differ.
How do agencies run call tracking dashboards for many clients?
Build one master template with fixed field names and copy it for each client, swapping the data sources. Data Studio has no built-in client management for agencies, so the process matters as much as the design: a tracking number mapping sheet per client, a checklist for connector credentials, and a scheduled email delivery per client.
Choose data source credentials with care. Owner's credentials let a client open the report without access to your call tracking account, which is what most clients expect. Viewer's credentials suit internal reports where each person should only see data they already have rights to.
Agree the qualified call definition with each client in writing before launch. A dental practice and a removals firm judge a good call very differently, and the agreed rule should appear on the definitions page. Agencies that want reports under their own brand usually pair this with white-label reporting.
Should you use a reporting app or build a custom call tracking dashboard?
A reporting app is the right choice if you want a ready template, a client login and no data work, and your clients only need call volume, duration and source. DashThis, AgencyAnalytics and Databox all offer that, and the call tracking tools have their own built-in reports.
A custom Data Studio build makes sense when you need qualified calls and cost per qualified call across channels, CRM outcomes joined to calls, several locations or many clients on one consistent template, or data that already lives in BigQuery. It also makes sense when you want to stop paying per client for a reporting seat.
Do not buy a custom dashboard if nobody tags calls and you have no plan to start. The dashboard will only report volume and duration, which the call tracking tool already shows for free. Fix the qualification process first.
| Need | Reporting app | Custom Data Studio build |
|---|---|---|
| Call volume, duration and source | Yes, ready template | Yes |
| Cost per qualified call across all channels | Partly, depends on integrations | Yes, calculated in the data layer |
| Calls joined to CRM sales | Limited | Yes, via Sheets or BigQuery |
| Ownership of the report | Inside the vendor's app | In your Google account |
| Running cost | Monthly subscription, often per client | Connector fees, BigQuery usage, optional Pro licences |
What mistakes make call tracking reports misleading?
Most misleading call reports count correctly but count the wrong thing. These are the issues we check first when we review an existing report.
- Treating every call as a lead, including existing customers, suppliers, spam and job seekers.
- Hiding missed calls, so a short-staffed Saturday looks like a failing campaign.
- Putting Google Ads call conversions next to call tracking totals without explaining the different rules.
- Letting tags drift, so the same type of call is labelled four different ways.
- Using one tracking number for several channels, which makes source attribution impossible.
- Showing caller numbers and recordings in a report shared outside the business.
How Greenwolf Tech Labs builds call tracking dashboards
We start with a free review of your call tracking setup, number mapping, tags, ad accounts and CRM. Then we agree the qualified call definition, build the mapping table and data layer in Sheets or BigQuery, design the pages in Data Studio, and reconcile call totals against the call tracking platform before handover.
Our team has delivered 100+ projects for 200+ clients, and our marketing dashboards bring Google Ads, Meta, LinkedIn, GA4 and Search Console into one view. We quote a fixed price after the review, and the reports and data sources are transferred to accounts you own.
FAQ
Frequently asked questions
What is a call tracking dashboard?
It is a report that shows inbound phone calls by source, campaign and keyword, alongside spend and outcomes. A good one reports qualified calls, missed calls and cost per qualified call, not just call volume. It draws on call tracking software, ad platforms and the CRM.
Can I connect CallRail to Data Studio?
Yes. CallRail offers its own Data Studio connector with default data sources for calls summary, forms summary and calls over time. Partner connectors from vendors such as Supermetrics and Coupler.io also support it. To join calls with ad spend and CRM sales, most teams combine the data in Sheets or BigQuery first.
Why do Google Ads call conversions not match my call tracking total?
Google Ads counts only calls that pass its minimum duration for the conversion actions you set up, and credits them to the click date. The call tracking platform logs every call on the day it happens, including repeat and offline callers. Both can be right, so the dashboard should explain the difference.
What is a good qualified call rate?
There is no reliable cross-industry benchmark, because each business defines a qualified call differently. Track your own rate by campaign over time and act on changes. A campaign whose qualified rate falls while volume rises is usually attracting the wrong audience.
How long should a call be to count as a lead?
Google Ads uses a 60-second default for call conversions, which advertisers can change. Duration is a rough filter, so pair it with tags or CRM outcomes. A 30-second call that books an appointment is worth more than a ten-minute call from a supplier.
Should a client-facing call report include call recordings?
Usually not. Recordings and caller numbers are personal data, and the people reading a marketing report rarely need them. Show aggregated counts by source and tag in the dashboard and keep recordings inside the call tracking tool with its own access controls.
Do clients need a paid licence to view a Data Studio call dashboard?
No. Data Studio is free for creators and viewers. Data Studio Pro costs $9 per user per project per month and applies only to creators, editors and managers in Pro workspaces, so clients who view reports never need one.
Keep reading
Related pages
Get started
Tell us what your reporting has to do
Describe the dashboards you need, who reads them and where the data sits. We reply within one business day with an approach, the connectors involved and a fixed-price plan.
- Free 30-minute reporting review
- Fixed quote before any work starts
- Everything built and owned in your Google account
Prefer email? info@greenwolftechlabs.com
Get a free proposal
Two lines is enough to start.