Google Ads clicks and Analytics sessions do not match
Google Ads and Analytics count different things, so their clicks and sessions do not match. Some gap is expected. Invalid-click filtering and session grouping account for part of it. A gap with far fewer sessions than clicks points to a tracking problem: auto-tagging off, a redirect dropping the campaign parameters, or the tag missing on a landing page. Check those in that order before changing the campaign.
At a glance
- Where it shows
- In the Google Ads campaign reports and the Analytics acquisition reports, when the two totals are compared.
- What stops
- Nothing stops. The numbers disagree, so a decision based on either total can be wrong.
- How serious
- Moderate. A campaign can look better or worse than it is, depending on which total is used.
What it means
Google's help page says there are a number of reasons Google Ads and Analytics may report different numbers of clicks and sessions. The first is that they measure different things. Google Ads tracks clicks, and Analytics tracks sessions and users.
Google Ads filters some clicks it treats as invalid, while Analytics reports on all the sessions that result. Two clicks on an ad within 30 minutes can register as one session in Analytics, while Google Ads counts both clicks. A small gap in either direction is not a fault by itself.
What actually triggers it
Auto-tagging turned off
Paid visits lose their Google Ads label in Analytics and show as organic, direct or (not set). The sessions exist, but the paid traffic sits in other rows.
A redirect on the landing page
A redirect can stop the Analytics code from running and strip campaign parameters such as the gclid from the address.
The tag missing from some landing pages
Google's page says that if the landing page for an ad isn't tracked, the campaign information isn't passed to Analytics. Check every landing page the ads use, not only the home page.
Visitors who block scripts or use an Analytics opt-out
Visitors who block JavaScript or images, or who use an Analytics opt-out add-on, may not be reported by Analytics at all.
Visitors who leave before the tracking code runs
Google's page describes a user who leaves before the tracking code executes. The click is recorded, but no session is.
Fix it in this order
- Check that auto-tagging is on in the Google Ads account. Without it, paid traffic is spread across other rows in Analytics.
- Open the landing page each ad uses. Check that the Analytics tag runs there and that no redirect removes the campaign parameters.
- Compare the same date range in both products. Data for dates before a link is not backfilled, so an earlier start can show a gap that is not a fault.
- If Analytics still shows far fewer sessions than clicks after those checks, go to the tag checks rather than changing bids.
Some gap remains after every check. Judge the campaign on the platform where the decision is made, and write down which total was used.
Often confused with
More Analytics sessions than Google Ads clicks
Google's page says more sessions than clicks can be a sign of positive engagement, from returning visitors and from bookmarked addresses that carry the click ID. That is not a leak in the tracking.
Google Ads account and Analytics property are not linked
When Google Ads data is absent from Analytics altogether, the link is the first thing to check. A gap between two totals that both exist is the case on this page.