Google Ads call conversions stopped importing through the CallRail integration.
Hi Guys,
Our Google Ads call conversions stopped importing through the CallRail integration. The break is consistent across two separate Google Ads accounts we have, both of which use CallRail, and both stopped sending data on around 27 May.
The integration still shows as Active and everything else looks fine, connected to the correct Google Ads account, with "Send calls as conversions" enabled and the first-time/repeat caller split selected. I would really appreciate if someone could help me troubleshot this issue.
0
Comments
Hi,
I’ve run into something similar before across multiple Google Ads accounts, so here are a few things I’d check.
Since it stopped on approximately May 27 across two different accounts, I’d first suspect either a Google Ads API/integration issue or a change in one of the conversion settings rather than anything campaign-specific.
Here’s my troubleshooting checklist:
✅ Verify that CallRail → Google Ads still shows Active and that “Send calls as conversions” is enabled.
✅ In Google Ads, make sure the imported CallRail conversion actions haven’t been changed to Secondary or removed from the Conversions column used for bidding.
✅ Confirm the conversion actions are still set to Include in “Conversions” if you’re optimizing campaigns using Max Conversions or tCPA.
✅ Check whether the GCLID is still being captured on new calls. If Google Click IDs aren’t making it into CallRail, conversions can’t be imported.
✅ Verify your website’s CallRail JavaScript snippet is still loading correctly. If the website was updated around that time, the DNI script may no longer be firing.
✅ If you’re using GTM, confirm nothing changed with your Google Tag, GTM container, or consent settings around May 27.
✅ Look in the CallRail activity logs to see whether calls are still being tagged as Google Ads traffic or if they’re now showing as Organic, Direct, or Unknown.
Because it happened on two separate Google Ads accounts at almost the exact same time, I’d lean toward one of these possibilities:
* A Google Ads API/import issue
* A CallRail integration issue
* A website tagging or GCLID capture problem
* A Google Ads account authorization/token that needs to be refreshed
If everything above checks out, I’d open a ticket with CallRail Support and mention that the issue began around May 27 across multiple Google Ads accounts. That timing may help them determine whether it aligns with any backend changes or known incidents.
One final question: Are the calls still appearing correctly inside CallRail but simply not importing into Google Ads, or are the calls themselves no longer being attributed to Google Ads inside CallRail? That answer usually narrows down where the problem exists.
Hopefully that helps. Let us know what you find—I’d be interested in the root cause since this affects optimization and automated bidding.
Please sign in to leave a comment.