Free tool by Clarvivo · no login
Upload matching Google Ads and GA4 exports to see whether your click-to-session gap is a normal metric difference or a tracking problem worth investigating.
Export both sources over the same dates and timezone. We compare clicks with GA4 sessions; they are different metrics, so a small gap is normal.
This tool answers: Is the Google Ads click-to-GA4-session gap large enough to investigate?
Enable JavaScript to run the check — the diagnosis itself is free and needs no account.
Google Ads reports clicks. GA4 reports sessions. They will never match, and they aren't supposed to: a click can bounce before the page loads, be blocked by an ad blocker, be refused by the consent banner, or happen twice within one session. Small differences are normal.
Large differences aren't. When GA4 records half the sessions Google Ads says it sent, something between the click and the page view is failing: a slow or broken landing page, a redirect that drops gclid, a missing GA4 tag, or a Google Ads to GA4 link that isn't attributing traffic to google / cpc.
This analyzer compares the two exports over the same dates and tells you whether the gap is within the range where you should just record a baseline, or large enough to investigate.
These answer the questions this one tends to raise.
So you can trust the result — and your developer can verify it.
The Google Ads file needs a Clicks column. The GA4 Traffic acquisition export needs Session source / medium and Sessions, for the same dates and timezone.
We sum sessions from GA4 rows whose source identifies Google and whose medium is cpc or paid search, such as google / cpc. Google organic traffic is not counted.
If GA4 sessions differ from clicks by more than 50%, we flag it with likely causes. Below that, we report the sessions-per-click ratio as a baseline to watch.
Clarvivo connects paid clicks, sessions, and actual revenue in one auditable view.
Connect Google Ads to revenue