CallRail review 2026: call tracking priced off your site traffic, not your campaigns
In the price list, CallRail looks like a $50/month subscription. In practice you are renting phone numbers, and how many you need is set by your site’s peak hourly traffic divided by four. That is the thing to know before you pay: the bill scales with site visitors, not with campaigns or ad spend. This CallRail review works through the vendor’s published figures and Google’s help pages: what Google Ads measures for free, which five meters CallRail bills against, why the pricing page contradicts itself, what the integration writes into your ad account, which setting silently kills conversion reporting, and who should not buy this at all.
What this CallRail review covers, and what Google Ads already does for free
Before comparing prices, it is worth knowing what you would be paying extra for. Google Ads does part of this job itself, at no cost, and plenty of advertisers buy a platform without ever switching the native feature on.
Native call reporting in Google Ads
Google’s built-in feature is call reporting, and the help page states its scope exactly: “Measure the performance of your call assets, location assets, and call ads with call reporting.” It is managed at the account level.
The mechanism is Google forwarding numbers — Google’s property, defined as “a unique phone number from Google.” The billing logic matters: “Google Ads doesn’t charge advertisers for users who manually dial a Google forwarding number. Advertisers are only charged when the Google forwarding number shown in the ad is clicked on.” A forwarding number can be toll-free, local-equivalent or local, and “whenever possible” it shares the area code of your business.
These numbers carry their own clocks. The number is shown within roughly 30 minutes of viewing the ad — up to about two hours in certain markets. After a first call it keeps connecting to the business for 60 days, and each new call resets that window. It is not permanent either: the help page says it “may vary over time” and “can change or be reassigned.”
The four call conversion types Google records itself
Google lists four: calls from ads (call ads, call and location assets); calls to a number on your website, where the visitor clicks your ad and then dials the forwarding number Google swaps onto the page; clicks on a number on a mobile site, with a blunt caveat — “we can only track these clicks, not the phone calls themselves”; and imported call conversions from an outside system.
Minimum call length is set by the advertiser: “every call that lasts at least that long is counted as a conversion,” while “calls shorter than this duration won’t be counted.” The default and the allowed range are not stated anywhere — the first of several documentation gaps we will flag.
Where the native feature stops
The limits are explicit. Display Network call assets are excluded outright: “Call assets targeting the Display Network don’t support Google forwarding numbers or tracking calls as conversions.” A forwarding number cannot be used outside call reporting and website call conversion tracking. And phone trees that play audio before the call connects are declared incompatible with the whole mechanism.
Availability is a closed list of thirty countries, including the United States, Canada, the United Kingdom, Germany, France, Italy, Spain, Poland, India, Japan, Brazil and Australia. Denmark, Hungary and the UK carry the footnote “*Toll-free number equivalent to a local number”; India and Japan carry “**On some calls, Caller ID shows a Google number, not the user’s number.”
From each call Google surfaces time, duration, campaign and ad group, plus the caller’s number for calls over 15 seconds, except in India. What it does not do: see calls from organic or other channels, assign a number per visitor, or tie a call to a search term. That gap is what the third-party layer is sold into.
Four CallRail plans, one shared telephony allowance
The pricing page lists four plans plus a separate product:
- Lead Tracking — 50 per month, “plus additional usage.”
- Lead Tracking Complete — 95 per month, “plus additional usage.”
- Lead Conversion — 150 per month, “plus additional usage.”
- Lead Conversion Complete — 195 per month, “plus additional usage.”
- AI Voice Assistant — “Starts at $95/month*.”
The included telephony allowance is identical on all four plans: 5 local numbers, 250 local minutes (transcription included) and 25 text messages, with SMS marked “Available after trial.” The difference between the $50 plan and the $195 plan is not call volume but features — form submissions and conversation analysis minutes.
A yearly toggle promises “Save up to 10% with a yearly plan,” but no annual figures appear. The numbers 50/95/150/195 carry no currency marker; dollars show up only in the API section.
Coverage is limited to four countries: “CallRail is available in the United States, Canada, the UK and Australia.” The UK and Australia have their own pricing pages. If your traffic targets anywhere else, the platform will not issue local numbers for it — so it cannot perform its core function at all.
A pricing page that contradicts itself
The most uncomfortable finding here is not the price but its uncertainty. The pricing page renders its plan table more than once, and the figures do not match between renderings. None is marked as current, and the page carries no last-updated date — only “Copyright © 2011-2026 CallRail, LLC” in the footer.
| Line item | Version 1 | Version 2 | Version 3 |
|---|---|---|---|
| Extra local minute | $0.06 | $0.05 | $0.05 |
| Extra toll-free minute | $0.09 | $0.08 | $0.08 |
| Extra analysis minute | $0.05 | not shown | $0.04 |
| Included transcription minutes | not shown | 250 / 250 / 10,000 / 10,000 | 250 / 250 / 10,000 / 10,000 |
| Included analysis minutes | N/A / N/A / 10,000 / 10,000 | not shown | N/A / N/A / 2,500 / 2,500 |
The gap between 10,000 and 2,500 included analysis minutes is fourfold on the most expensive plan. The gap between $0.06 and $0.05 per minute is $200 a month at 20,000 minutes. Even the Voice Assist footnote exists in two editions — “$1/call after 50 Voice Assist calls over 15 seconds” in one, “after 55” in the other.
The practical takeaway: do not build a budget off the published table. Before you pay, get written confirmation of the included allowances and the overage rates for your specific plan — and keep the email, because the FAQ states plainly that “we may change our fees at any time by posting a new pricing structure to our Site or in your account and/or sending you a notification by email.”
Overage rates and five independent meters
There are five meters, and any one can overflow on its own:
- Local numbers — $3 each, on every plan.
- Local minutes — $0.05 or $0.06 each (see the discrepancy above).
- Toll-free numbers — $5 each, minutes at $0.08–0.09.
- Text messages — $0.03 each.
- Form submissions — $0.02 each, Complete plans only.
- Transcription and analysis minutes — $0.025 per transcription minute on Tracking plans, $0.04 on Conversion plans; analysis minutes $0.04–0.05.
Minutes are not billed as used: “Minutes are calculated by rounding each call up to the nearest minute and then summing the minutes.” A hundred thirty-second calls bill as a hundred minutes, not fifty — for advertising that produces many short calls, that roughly doubles the telephony line.
Go over the allowance and nothing stops and nothing auto-upgrades — you are simply invoiced: “We’ll continue to track your leads, but additional minutes and numbers not included in the chosen plan will be billed in addition to your base fee. These additional fees are not refundable under any circumstances but you can always upgrade your pricing plan as your business grows.” The phrase “not refundable under any circumstances” deserves its own line in your checklist.
API access is a separate cost. It is included on all plans but metered in tiers: 0–1,500 calls per month free, 1,501–12,000 at $80 USD per month, 12,001–300,000 at $200 USD per month, billed on the previous period’s usage. If you plan to pull call data into your own dashboard or tracker, add $80–200 to the subscription.
The arithmetic that matters: numbers are sized by your peak hour
Here is where real budgets diverge from expectations by multiples. To see a call at the level of an individual visitor — a hard requirement for the Google Ads integration — you do not need one number per campaign. You need a pool of numbers that swap dynamically on the site, and the vendor publishes the sizing formula.
The formula and its bounds
The knowledge base states the rule word for word: “The number of peak hourly visitors divided by four equals the size of your pool.” The worked example in the same article: a peak of 100 hourly visitors means a pool of 25. A second article restates it as “a quarter of the peak hourly traffic reported in Google Analytics, with a minimum of four numbers,” and a third as “one phone number per concurrent visitor (with a minimum of four numbers).”
The peak comes from Google Analytics — an hourly chart over the previous two weeks, or over peak season for a seasonal business. The floor is four numbers, and it is not a formality: “Lower amounts have been found to negatively impact attribution quality.” The self-service ceiling is 300 numbers; beyond that the vendor directs you to support.
What happens when the pool is too small
You will not see an error. The stated consequence is this: “if your pool is too small, two of your website visitors might see the same phone number on your website,” and then “we’d combine their separate sessions under the person who contacts you first.” Two distinct visits merge into one and attribution breaks silently. What a visitor sees when every number in the pool is already assigned is not stated anywhere.
What that costs
Every pool number is a number on the invoice: “if you choose a pool with 30 visitor tracking numbers, then you will have 30 numbers total on your invoice.” Five are included; the rest are $3 each. Running the published rates, with no estimates of our own:
| Peak visitors per hour | Pool needed | Numbers over allowance | Monthly number fee | Lead Tracking base + numbers |
|---|---|---|---|---|
| 16 | 4 (minimum) | 0 | $0 | $50 |
| 100 | 25 | 20 | $60 | $110 |
| 400 | 100 | 95 | $285 | $335 |
| 1,200 | 300 (maximum) | 295 | $885 | $935 |
Minutes, transcription and SMS are not in that table at all — numbers only. Hence the headline: the $50 subscription exists for a site whose peak is under 16 visitors an hour. On a site with meaningful paid traffic, the plan fee stops being the largest line.
One more cost driver is Local Swap, which shows a number matching the visitor’s area code. US and Canada only, requires the JavaScript snippet, matches location by IP, and adds at least two numbers per area code. It is also irreversible: “Local Swap will be locked and cannot be deactivated for the website pool,” and to shrink the pool you must deactivate and rebuild it. Every batch raises the invoice.
What the integration writes into your Google Ads account
This is the section that matters in any review of an external tool: which fields of your account it takes over.
Conversion actions that appear on their own
Activating the integration creates conversion actions: “Phone Call” for a single type, or “First Time Phone Call” and “Repeat Phone Call” if you split first-time and repeat callers, plus “Form Capture” for forms. All use the source “Import from clicks.” The vendor recommends — but does not set for you — marking these as primary so they reach reports and automated bidding.
The setting that stops data cold
You can edit the other conversion fields, but two are off limits: renaming the conversion or changing its source stops data from being sent. The object in your account looks like yours, but it belongs to the integration, and routine tidying of the conversions list cuts off the call feed with no warning.
Manager accounts
MCC is supported: the dropdown shows every manager account you can access, you pick one opted into cross-account conversions, and the platform rolls the integration out across the accounts that need it. But one limit is explicit: “Connected accounts cannot set up their own conversions.” A client account inside the hierarchy loses autonomy here — worth knowing if you work through rented access or several contractors. The mechanics are covered in our guide to cross-account conversion tracking in Google Ads.
The swap precedence trap
The most expensive misconfiguration looks entirely sensible. Create a dedicated source number called something like “Google PPC” and it takes precedence over the “All Website Visitors” pool — and, as the knowledge base itself puts it, “your calls would not show as conversions in Google Ads.” The number works, calls are recorded, in-platform reports fill up, and the ad account shows nothing. You verify it in the Number Assignment Table.
Requirements without which nothing reports
The list is short, but every item is blocking.
Auto-tagging. Required, and listed as a prerequisite for both calls and forms. Without it there is no gclid on the final URL, the platform cannot recognise the call as coming from Google Ads, and it is never sent as a conversion. Conversions are posted using gclid, wbraid and gbraid; enhanced conversions are not needed. For how those identifiers and tracking templates behave, see our breakdown of GCLID, GBRAID and WBRAID.
Visitor-level tracking. Without a number pool and the JavaScript snippet the integration does not work: calls to source trackers do not report. The snippet goes on every page before the closing body tag, and the number on the page must be visible and written as “111-222-3333,” “111.222.3333” or “(111) 222-3333.”
Time. Any activation or change “can take up to 24 hours to register,” and the first call conversion after setup sometimes takes 24–48 hours. For manual imports Google advises waiting at least three hours. Do not judge the setup on day one.
Keywords. To see the search term inside the platform, the vendor recommends adding the ?keyword={keyword} parameter to your Google Ads tracking template by hand. It is not on by default. And one more documented limit: “Keywords will not be passed for Organic traffic.”
What the integration does not do
Read this list before paying — half of the market’s expectations do not survive it.
- No backfill. The integration “cannot be applied to previous calls and forms” — only interactions after activation or update are captured.
- Incompatible with pay-for-conversions. Lead activity is an offline event, and Google requires offline events to be removed before that bidding model can be used. The strategy itself is covered in our piece on pay-for-conversions bidding.
- Ad asset calls need a separate feature. Calls from call assets require Call Details Forwarding, configured on its own.
- It never lands in Google’s “Calls from Ads” conversion. Platform calls arrive as their own imported action, not inside Google’s native call-from-ad reporting.
- Manual import is capped at 90 days. Only gclids “within the past 90 days” are accepted, and “once manually uploaded, conversions can’t be deleted.” Duplicates are skipped only on a full match of gclid, timestamp and action name. Mechanics: our guide to offline conversion import.
- White-label accounts restrict rights. Only administrators can activate the integration there.
The vendor also publishes why conversions can be missing despite a correct-looking setup: the wrong account is connected; you are looking in the wrong part of the interface; calls land on source trackers rather than the pool; the integration was activated too recently; pool numbers are not swapping because the snippet is missing; no qualifying calls have happened since setup; the integration’s own triggers block sending (the documented example is a “> 5 minutes” condition when every call runs two minutes); auto-tagging is off; the goal is secondary, so conversions appear only under “All Conversions” and are excluded from automated bidding; the goal is not an account-default; or an ad blocker is stopping the authorisation window.
Dynamic number insertion versus Google’s phone number verification
This is where the external tool and the platform’s own rules collide head-on, and sales material almost never mentions it.
Google requires you to prove the number in your ad and warns directly: “Verify your domain ownership to prevent ad disapproval for an unverified phone number.” Then comes the sentence that is the whole problem: “Google’s automated verification system can’t verify the phone number by scanning your website’s source code.” The automated check cannot find the number in the source precisely because dynamic insertion writes it in with a script after the page loads.
Two fixes are named: link Google Search Console to Google Ads (the recommended route), or install the Google tag directly in raw HTML. Do neither and you risk a disapproval for an unverified phone number while your call tracking works perfectly. Plan domain verification alongside the pool, not after it.
What the public documentation does not say
An honest CallRail review has to list the gaps, and here there are many — several of them financial.
- No last-updated date on the pricing page or any knowledge-base article we worked through — no way to tell which table version is current.
- No statement of how many users or companies each plan includes.
- No currency marker on 50/95/150/195; dollars appear only in the API section.
- No actual annual prices behind the promised “up to 10%” discount.
- No word on whether US and Canada prices differ, or on taxes and fees above the listed price.
- No stated duration for how long a number stays held for one visitor — only “one visitor at a time” and “we free up that phone number” once browsing ends.
- No description of what a visitor sees when every pool number is in use.
- No minimum Google Ads permission level for connecting the integration.
- No attribution window for the automatic integration; the 90 days apply to manual import only.
- No default value or allowed range for minimum call length — that gap is in Google’s help page, not the vendor’s.
- No explanation of how a number inside an image gets swapped, even though an image is listed as an acceptable placement.
- Nothing at all on the effect of number swapping on SEO, contact-data consistency, or your business profile listing.
Two cancellation facts belong here as well. There is no long-term contract and you can cancel any time — but numbers are released at the end of the billing cycle, and “once your phone numbers are released, they cannot be recovered.” Nor can you pause: “It’s not possible to temporarily disable an account.” For a seasonal business that is a choice between paying for numbers out of season and losing them permanently.
Who should wait, and who should skip it
CallRail is a mature product, but it solves a narrow problem and prices in proportion to traffic rather than revenue. Signs the purchase is premature:
- Your traffic is not US, Canada, UK or Australia. The platform issues no local numbers elsewhere, so availability settles the question before features do.
- Fewer than a few dozen calls a month. At that volume, switch on native call reporting and a sensible minimum call length instead: it is free and covers calls from ads and calls to the swapped number on your site.
- No site with meaningful traffic. All the value of visitor-level tracking is in tying a call to a visit; without a pool it is ordinary telephony with recording.
- Calls are not your main channel. If leads arrive through forms, the platform becomes an expensive way to collect form submissions at $0.02 apiece.
- Basic conversions are not fixed yet. Until ordinary conversion tracking and auto-tagging work in the account, an external layer only adds confusion.
If calls are your main channel and the geography matches, budget it with the formula above: peak hour divided by four, minus the five included numbers, times three dollars, plus minutes rounded up per call, plus transcription, plus the API tier if you export data. That total — not the number at the top of the pricing page — is the real price.
The line this blog does not cross
We review tools that help advertisers measure results honestly and avoid overpaying. Swapping a number on your own site to attribute your own calls is exactly that, and Google supports it directly through forwarding numbers and domain verification. We do not write about ways to mislead the platform — swapping the landing page shown to review, hiding site content from inspection, or masking who the advertiser is. A tool sold as a way around review is not a measurement tool, and it will not appear here.
Other tool reviews in the same vein: the Channable feed management review and the ClickCease review. For the topic without a product attached, see call tracking and call campaigns in Google Ads. If what you need is working ad access for a difficult vertical rather than a measurement tool, we offer Google Ads agency accounts and media buying services. Primary sources for this article: Google’s call reporting documentation, its page on Google forwarding numbers and the CallRail pricing page.
FAQ
What does CallRail actually cost per month?
The base runs from 50 for Lead Tracking to 195 for Lead Conversion Complete, with usage billed on top across five meters. Every plan includes five local numbers, 250 local minutes and 25 text messages. Beyond that: $3 per number, $0.05–0.06 per local minute, $5 per toll-free number, $0.03 per text, $0.02 per form submission on Complete plans. The total depends on your number pool, which depends on site traffic.
Why is pool size based on traffic rather than campaign count?
Because a number is held by a visitor, not by a campaign: one number per concurrent visitor. The vendor publishes the rule verbatim — peak hourly visitors divided by four equals the pool size, with a minimum of four numbers and a self-service maximum of 300.
Do I need CallRail if Google Ads already counts calls?
Native call reporting is free and covers call assets, location assets, call ads and calls to the forwarding number swapped onto your site. What it does not give you is a call tied to an individual visitor and a search term, or calls from organic and other channels. If you need those, the external layer makes sense; if not, it is redundant.
Which conversion actions appear in Google Ads after connecting?
Either “Phone Call” or the pair “First Time Phone Call” and “Repeat Phone Call,” plus “Form Capture” for forms. All use the source “Import from clicks.” Renaming a conversion or changing its source stops data from being sent, so those two fields must be left alone.
Does the integration work with an MCC manager account?
Yes. You select a manager account opted into cross-account conversions and the platform rolls the integration out across the accounts that need it. One limit applies: connected accounts cannot set up their own conversions, which is worth weighing if you work through rented access or several contractors.
Why are conversions missing when tracking clearly works?
The most common documented causes: the wrong account is connected; calls land on a source tracker rather than the pool; auto-tagging is off; the goal is secondary or is not an account-default; the integration’s own duration triggers filter calls out. And one specific trap — a source number that takes precedence over the pool, in which case calls never appear as conversions in the ad account at all.
Does dynamic number insertion interfere with Google’s number verification?
Yes, and Google says so outright: its automated verification system cannot verify the phone number by scanning your site’s source code. The fix is to prove domain ownership by linking Google Search Console to Google Ads, or to install the Google tag in raw HTML. Do it alongside the pool launch, or you risk a disapproval for an unverified phone number.
What happens to my numbers if I cancel?
There is no contract and you can cancel any time, but numbers are released at the end of the billing cycle and cannot be recovered afterwards. Pausing an account is not possible at all. For a seasonal business that means either paying for numbers out of season or losing them for good.