CallRail Not Sending Conversions to Google Ads? The 5 Breaks (Checked in Order)

You are running Google Ads, CallRail is recording calls, and yet Google Ads shows zero call conversions. The money is going out, the phone is ringing, and the reporting says nothing is working. I have walked into this exact mess for clients in five states, and the fix is almost always one of five specific breaks. Check them in the order below and you will find the problem in under 30 minutes.

How CallRail conversions are supposed to reach Google Ads

Before you can fix a broken chain, you need to know what the chain actually looks like. Most of the confusion I see with callrail not sending conversions to google ads comes from people not knowing which handoff failed. There are four handoffs, and any one of them can go dark without an error message anywhere.

The click, the swapped number, the call, the export

Here is the real path a call conversion has to walk:

1. The click. Someone clicks your Google Ads ad. Google appends a click ID (called GCLID) to the landing page URL.
2. The number swap. CallRail's JavaScript loads on your landing page, reads the GCLID, and swaps your static phone number for a tracking number tied to that click.
3. The call. The visitor calls the swapped number. CallRail records the call, the source, and the GCLID together.
4. The export. CallRail sends that call, plus the GCLID, to Google Ads as an imported conversion. Google Ads matches the GCLID back to the original click and credits the ad.

Four steps. Any one of them silently fails and you get zero conversions on the Google Ads side while CallRail still shows a happy list of calls.

Why every link in that chain can fail silently

This is the part that drives owners crazy. CallRail keeps recording calls. Google Ads keeps spending. Neither system throws a warning that the handoff between them died. The account link can de-authorize, the swap script can get stripped by a funnel builder, the import can be paused, and nothing turns red anywhere. You have to go check.

This week: open both CallRail and Google Ads side by side before you touch anything else, so you can compare what each one thinks is happening.

Break 1: the CallRail to Google Ads link silently de-authorized

This is the number one cause of callrail conversions not showing in google ads and almost nobody talks about it. If you check nothing else, check this first. It takes 90 seconds and it is the single most common reason the whole thing goes quiet.

Password changes and permission changes kill it

The CallRail to Google Ads connection is an OAuth handshake. It sits on a token tied to whoever authorized it. If that person:

• changed their Google password
• had their two-factor reset
• lost admin access to the Google Ads account
• left the company and had their Google account disabled
• revoked third-party app access during a security cleanup

...the link dies instantly. CallRail keeps trying to push conversions. Google Ads keeps rejecting them because the token is invalid. Neither side surfaces this in a way an owner would notice.

I had a solo attorney I work with in Philadelphia call me in a panic because her cost per lead in Google Ads had "tripled overnight." Nothing had changed in the campaigns. What had changed: her office manager rotated the shared Google password two weeks earlier. The CallRail link had been dead for 14 days. Sixty-three call conversions never made it to Google Ads. On a $4,200 monthly spend, her reported cost per conversion looked like $340 when the real number was closer to $95.

Where to check the connection, on both sides

Check both ends. Do not trust just one.

In CallRail: Settings, then Integrations, then find Google Ads. The status should say Connected with a recent last-sync timestamp. If it says Reconnect, Reauthorize, or the timestamp is more than a few days old, that is your break.

In Google Ads: Tools, then Linked accounts, then Third-party app analytics. CallRail should appear as an active linked source. If it is missing or shows an error, that confirms it.

This week: log into CallRail and confirm the Google Ads integration shows a sync timestamp from the last 24 hours. If it does not, reauthorize with an account that has admin on Google Ads and will not have its password rotated.

Break 2: auto-tagging is off, so calls cannot be matched to ads

If break 1 is clean and you still have call conversions not tracking, this is your next stop. Auto-tagging is the setting that generates the GCLID in the first place. No GCLID, no match, no credit.

Why CallRail needs the click ID

CallRail identifies which Google Ads click drove a call by reading the GCLID from the landing page URL. Google Ads only appends that GCLID when auto-tagging is enabled at the account level. If auto-tagging is off, your ad clicks arrive at your landing page with no ID attached. CallRail has nothing to hand back to Google Ads. The call gets recorded as "direct" or "organic" and never counts as a paid conversion.

I have seen this happen when a marketing agency handed off an account and the new team turned auto-tagging off "to keep URLs cleaner." That one toggle wiped out call attribution on a $12,000/month ad account for six weeks before anyone noticed.

The two-minute check in Google Ads settings

In Google Ads: Admin, then Account settings, then Auto-tagging. The toggle should be ON. That is the whole check.

While you are there, click one of your own live ads (use a real search, do not preview). Look at the URL that lands on your page. You should see ?gclid= followed by a long string. If you see it, auto-tagging is working. If you do not, that is your break.

This week: confirm auto-tagging is ON and click one of your own ads to verify a GCLID is landing on your page.

Break 3: the number swap is missing on your landing pages

This is the sneakiest one and the second most common cause of the callrail google ads integration not working complaint. Your CallRail dashboard looks fine. Your integration is connected. Auto-tagging is on. And the calls still are not attributed, because they are being made to your static number, not the swapped one.

Funnel and landing page builders are the number one hiding spot

The CallRail swap script needs to run in the visitor's browser to replace the phone number on the page. Some landing page builders strip scripts, sandbox them, or load them so late that the visitor already saw the static number and dialed it before the swap ran.

The usual suspects I run into:

• GoHighLevel funnels. Custom JavaScript often has to be added in a specific "Tracking Code" area, not the general header. I have seen the script pasted into the wrong slot and never fire.
• ClickFunnels. Phone numbers hard-coded inside button elements sometimes will not swap without a text-based number on the page for the script to find.
• Unbounce. Script Manager needs the swap script set to run on the correct pages, not just the homepage.
• Wix and Squarespace. Header injection is limited on lower plans, and the script sometimes only loads on the homepage instead of every landing page.
• Instapage and Leadpages. Same story, scripts must be added per-page in some setups, not account-wide.

A plumber in NJ I worked with was spending $2,800 a month on Google Ads driving traffic to a GoHighLevel funnel. His CallRail dashboard showed 41 calls that month. Google Ads showed 4 conversions. The swap script was in the wrong container on his funnel, so 90% of his ad-driven callers dialed the static number that was hard-coded into the click-to-call button. His real cost per lead was $68. Google Ads was reporting $700.

How to check any page in 60 seconds

Open your landing page in an incognito window. Look at the phone number displayed. Now do this:

1. Open the same page with a URL that has a fake GCLID: yourpage.com/?gclid=test123
2. Wait two seconds for scripts to load.
3. Look at the phone number again. It should have changed to a CallRail tracking number.
4. Also check the click-to-call button by hovering over it or inspecting it. The tel: link should have swapped too, not just the visible text.

If either the visible number or the click-to-call link did not swap, that page is not tracking. This is the exact callrail number swap not working failure mode you need to catch.

This week: run the fake-GCLID test on every landing page your ads point to, including thank-you pages if they show a phone number.

Break 4: the conversion import is misconfigured in Google Ads

Assume the first three checks passed. Calls are landing, they have GCLIDs, CallRail is sending them. Now the question is what happens when they arrive at Google Ads. This is where import call conversions google ads settings quietly filter your data.

The call conversion action status

In Google Ads: Goals, then Conversions, then Summary. Find the conversion action CallRail is importing into. Check three things:

• Status. Must say Active. If it says Inactive, No recent conversions, or Removed, that is your break.
• Include in "Conversions". If this is set to No, the calls will import but will not count in your reporting or bidding.
• Category. Should be Phone call lead or similar. If it is set to something odd, some campaign types will not optimize toward it.

I once found an account where a well-meaning consultant had set "Include in Conversions" to No on the CallRail action while testing something and never turned it back on. Three months of call data was flowing in and being ignored by Smart Bidding.

Qualifying rules that filter everything out

Google Ads lets you set qualifying rules on imported conversions, things like minimum lead score or lead status. If someone set a rule that requires a field CallRail is not sending, every call gets filtered out at import. Check the conversion action for any qualifying rules and either remove them or confirm CallRail is passing the required data.

For a full walkthrough of every setting that can quietly kill call attribution, see the 8 places conversion tracking breaks. This one is number four.

This week: open your call conversion action and confirm Status is Active, Include in Conversions is Yes, and no qualifying rules are filtering the imports.

Break 5: duration and filter rules are eating your calls

Last stop. Everything is connected, tagged, swapped, and importing. And you are still seeing fewer conversions than you expect. This one is not a bug, it is a setting you or someone else made intentionally at some point and forgot about.

Minimum duration set too high

Both CallRail and Google Ads let you set a minimum call duration before a call counts as a qualifying conversion. The Google Ads default for imported call conversions is often 60 seconds. If you or CallRail have a rule set at 90, 120, or higher, every call shorter than that gets tossed.

This matters because some real leads hang up in 45 seconds after getting the info they need to book. If your service is one where callers ask a fast question and then request a callback or a text, you might be filtering out half your qualified leads.

An HVAC contractor in San Diego I helped had his minimum set at 120 seconds because "that filters out spam." It also filtered out 34% of his real emergency-service calls, which averaged 71 seconds because customers were panicking and wanted a truck dispatched fast. We dropped the minimum to 30 seconds and his reported conversion volume went up 41% overnight, from real calls that had always been there.

First-time-caller-only settings

CallRail also has a setting that only counts a caller as a conversion the first time they call. If you have repeat customers, or if a real lead calls twice before booking, the second call does not import. Depending on your business, that setting is either smart or catastrophic. For a dental office where the same patient calls three times to reschedule, it is fine. For a car dealership where a lead calls the sales line, then the finance line, then back to sales, you are throwing out signal.

This week: review both your CallRail conversion filters and your Google Ads conversion action rules. Write down every filter, ask whether it fits your actual business, and remove the ones that do not.

Prove the fix with one real call

After you have fixed whichever break you found, do not trust the dashboards until you see a fresh test call flow all the way through. This is the same discipline I use in how to test conversion tracking end to end, and it is worth 20 minutes.

Here is the test:

1. Open an incognito window on your phone.
2. Search Google for a keyword you know triggers your ad. Click your own ad (yes, it costs you a click, worth it).
3. On the landing page, wait two seconds. Confirm the number displayed is a CallRail tracking number.
4. Call that number. Stay on the line for at least 90 seconds so no duration filter kicks it out.
5. Hang up. Wait 15 to 30 minutes.
6. Check CallRail. The call should appear with the Google Ads source and a GCLID attached.
7. Check Google Ads. Within 3 to 24 hours, the conversion should appear on the campaign that served the ad.

If it shows up in both places, the chain is alive. If it shows in CallRail but not Google Ads, you are back to breaks 1 or 4. If it did not show a swap on the landing page, break 3.

This week: run one real test call and log the timestamps in CallRail and Google Ads so you can prove attribution end to end.

Catch the next break the day it happens

Here is the honest truth about all five of these breaks: they will happen again. Someone will rotate a password. A web developer will rebuild the landing page and forget the swap script. A campaign manager will edit the conversion action. The chain will die, and you will find out weeks later when the reports look bad.

What I do for clients is build a read-only daily check that reconciles CallRail against Google Ads and emails you the day the numbers stop matching. This is my Conversion Tracking Health Monitor. It watches for the exact five breaks in this article: link status, auto-tagging state, swap script presence on your landing pages, conversion import health, and filter drift. It is one of the setups I run under Apex Autobots, and the first build goes live in about a week.

You do not need me to build this. You can run the manual check monthly and catch most of these yourself. But if you are spending more than $3,000 a month on Google Ads and your revenue depends on phone leads, the math on catching a two-week outage the day it starts, instead of three weeks in, is not close.

This week: put a monthly recurring calendar reminder to run the five checks above, or reach out if you want me to automate it. Email aaarhontoulis@gmail.com or call (484) 602-6390.

What to do this week

Here is your ordered checklist. Do them in this sequence and you will find the break in under an hour.

1. Today: log into CallRail, go to Integrations, confirm the Google Ads link shows a sync timestamp in the last 24 hours. If not, reauthorize.
2. Today: in Google Ads, confirm auto-tagging is ON under Account settings.
3. Tomorrow: open every landing page your ads point to with ?gclid=test at the end and confirm the phone number and click-to-call link both swap to CallRail tracking numbers.
4. This week: in Google Ads, open your call conversion action and verify Status is Active, Include in Conversions is Yes, and no qualifying rules are filtering out calls.
5. This week: review minimum duration and first-time-caller settings in both platforms. Adjust to fit how your customers actually call.
6. This week: run one real test call from a fresh incognito ad click, and confirm it appears in both CallRail and Google Ads.

If you have run all six and calls are still not showing up, that is when I want to hear from you. Send me what you found, what you tried, and screenshots of both dashboards. Most of the time we can find the break in one call. Email aaarhontoulis@gmail.com or call (484) 602-6390 and I will help you sort it out.