CallRail Google Ads integration and your landing page Most breaks happen on the page, not in the settings.

How the CallRail Google Ads integration works

CallRail tracks calls and forms. Once its Google Ads integration is on, CallRail says it reports your Google PPC calls and form submissions to Google Ads as conversions.

Here is the chain, in CallRail's own terms:

1. Someone clicks your ad. Auto-tagging in Google Ads adds a click ID to the landing page URL.
2. The CallRail script runs on the page. With visitor tracking, CallRail captures the Google click ID for that visitor.
3. The number swaps. CallRail's dynamic number insertion replaces your number with a tracking number from the website pool.
4. The visitor calls. CallRail sends the click ID to Google Ads, and Google records the call as a conversion.

CallRail lists three must-haves: the JavaScript snippet on the website or landing page you track, visitor tracking, and auto-tagging in Google Ads. When you activate it, CallRail creates a "Phone Call" conversion (or "First Time Phone Call" and "Repeat Phone Call") and a "Form Capture" conversion, with the source "Import from clicks."

One rule trips people up. CallRail says only calls made to the website pool with a source of "Google Ads" report as conversions. Calls to source trackers do not.

Why the number does not swap

If the number on the page never changes to a tracking number, the call cannot be tied to the click. CallRail's own troubleshooting guide points at these causes:

• Script placement. CallRail says its swap script should sit as close as possible to the closing body tag.
• Wrong swap target. The swap target is the number CallRail looks for and replaces. If it is wrong, the number will not swap.
• Swap target format. If the number on the page is formatted differently than expected, CallRail has a guide to check the formatting.
• Caching plugins. CallRail says some plugins, like WP Rocket, can make the JavaScript snippet fail.
• Another tracking number wins. Other tracking numbers can override your website pool. CallRail has swap precedence rules for this.
• Click-to-call buttons. CallRail recommends a plain button tag with the number inside. It says it will not swap a number coded as the value of an input button.

Test the right way. CallRail says to test each page where the snippet is installed, because testing one landing page does not test the whole site. It also says to test on a computer that has not been to the site, or in a private window, so an old cached visit does not fool you.

Every page builder change is a risk

Landing pages change all the time. Someone switches templates, adds a caching plugin, or rebuilds the header. The snippet can fall off, or the number can end up inside an image or a different element. Nobody gets an error. Calls just stop showing up as Google Ads conversions. That is why a weekly check of the actual ad page beats a one-time setup.

Click ID problems on the landing page

The integration runs on Google's click IDs. CallRail says it posts conversions using gclid, wbraid, and gbraid. If the landing page damages the click ID, conversions fail even when the number swaps fine.

• Lowercase click IDs. CallRail says gclids are case sensitive and usually mixed case. If your site forces them to all lowercase, conversions will not upload. Look for a site setting that limits URLs to lowercase.
• Auto-tagging off. CallRail needs auto-tagging on in Google Ads for both calls and forms to report.
• Redirects. If the final URL redirects, make sure the full URL with the click ID arrives on the page where the CallRail script runs.

CallRail also lists account side causes: the consent setting for imported and uploaded data in Google Ads, the click date versus the call date, a short conversion window, and repeat callers not being counted.

Duplicate and missing conversions

CallRail is one more system reporting into Google Ads. That is useful, but it means two systems can count the same lead, or each can assume the other is counting it.

Calls from ads vs CallRail calls

Google's own "Calls from ads" conversion counts calls from call-only ads and call assets through Google forwarding numbers. CallRail says that conversion is separate from its integration, and CallRail calls only report to its "Phone Call" conversion. To track call ads and assets, CallRail points you to Call Details Forwarding, a separate feature in Google Ads.

Forms counted twice

If your landing page also has a Google Ads conversion tag on the form, and CallRail's "Form Capture" is turned on, the same form fill can report through both. Google reports every Primary action in the Conversions column. Look at your conversion actions and decide which one is Primary for forms. Set the other to Secondary, which Google reports only in the All conversions column.

Two tools changing one number

Google's website call tracking also swaps your page number for a forwarding number. If both Google's phone snippet and CallRail try to change the same number on the same page, it gets hard to know which call went where. Pick one tool per number.

Pay for conversions bidding

CallRail says its integration cannot be used with pay for conversions bidding, because its leads report as offline events.

What ClickMend checks on the page

ClickMend does not connect to CallRail and does not read your CallRail settings. It checks the page your Google Ad sends people to, the final URL, which is where the CallRail script has to run.

Every call tracking script, chat widget, and pixel is more code a phone has to load before the visitor sees your number. ClickMend gives the page a 0 to 100 score that blends Google PageSpeed Insights performance (40%), Core Web Vitals (25%), SEO basics (20%), best practices (10%), and accessibility (5%). It names unused JavaScript and other slow parts, so you can see which scripts are weighing the page down.

It also checks the Google Ads side of tracking on the page: is the conversion tag there, did it load, is the conversion ID a placeholder, is Google Tag Manager missing, is the conversion linker off.

The free scan shows the problems, 2 scans a week, no card. Paid plans show the fixes and add weekly monitoring with alerts when a page gets worse. For the Google side of phone tracking, read Google Ads call tracking. Then scan the landing page free.

Frequently asked questions