When GA4 sessions disagree with Google Ads clicks, Google's troubleshooter says: "It's important to understand that these are different metrics, and some level of discrepancy is expected" (Clicks and Sessions Discrepancy for Google Ads and Google Analytics: Troubleshoot). This is the measurement check inside the complete guide to Google Ads fraud, run before you read any gap as fraud.
How we checked this. No ad-account test was run. Sources are Google help pages read on 16 November 2026, plus a redirect check on our own landing page.
What do Google Ads clicks and GA4 sessions each count?
A click is an interaction with the ad, counted whether or not the page loads, while a session is a period of activity on your site, started by a tagged page view and, by default, ended by 30 minutes of inactivity. One visitor can therefore make two clicks and one session, or one click and several sessions.
On the ad side, "A click is counted even if the person doesn't reach your website, maybe because it's temporarily unavailable" (Click: Definition), and a click on the "phone number of a text ad" counts too.
In GA4, "By default, a session ends or times out after 30 minutes of user inactivity," and the session_start event "carries the information that determines the attribution of the session, such as the gclid" (About Analytics sessions). The gclid is the click ID that auto-tagging adds to your landing-page URL; manual tagging means adding UTM parameters yourself.
Google's example: "If a user clicks your ad twice within 30 minutes without closing their browser, Analytics may register this as one session, even if they left and returned. Google Ads, however, would count two clicks."
Sessions are not users, since one returning user can start several sessions. Google's engaged session is one that "Lasts longer than 10 seconds", "Has a key event" or "Has 2 or more screen or page views" (Engagement rate and bounce rate), so engaged sessions run lower than sessions.
GA4's own "Google Ads clicks" metric is imported, not measured: "This dimension is populated automatically when you link Google Ads and Analytics" (Analytics dimensions and metrics).
Compare like with like before you read the gap
Compare whole days in matching time zones, campaign by campaign, starting 48 hours after you linked Google Ads to GA4. Linked data takes up to 48 hours to appear and is never filled in for earlier days.
- Time zones. Google Ads reports in the account time zone (Fix missing data and discrepancies), and GA4 in the property time zone (Set up Analytics for a website and/or app).
- Link date. The troubleshooter says "Data will not populate retroactively", and Google adds that long ranges "may include periods during which your accounts were not linked".
- 48 hours. "Google Ads data will be in your Google Analytics reports within 48 hours." (Connect Google Ads to Google Analytics). In GA4's Google Ads dimensions, "(data not available)" "might also appear if data is still processing", and the troubleshooter says to allow 24 to 48 hours.
- Estimated sessions. GA4 properties "use a statistical estimate of the number of sessions" (Comparing metrics: Google Analytics vs. Universal Analytics), so expect small differences.
GA4 does not restart sessions at midnight, unlike Universal Analytics: "Sessions aren't restarted at midnight," says Google's metrics comparison. Midnight is not a cause of the gap.
Why does Google Ads show more clicks than GA4 sessions?
Google Ads shows more clicks when one visitor clicks twice in one session, never loads the page, leaves before the tag runs, or is never recorded by GA4.
- Repeat clicks. "A user might click your ad multiple times in a short period," says the troubleshooter. Check: none needed.
- Leaving before the tag loads. Google describes a visitor who "leaves the landing page before the tracking code executes". Check: page speed and an early tag.
- No page load. Unavailable pages and phone-number clicks still count. Check: uptime, and read call-heavy campaigns apart.
- Tag missing or not loading. Google asks you to ensure "the page is loading for all possible users and IPs, and the tracking code is installed correctly". Check: the tag on every final URL.
- Browser preferences. Some users "might have JavaScript or images turned off", or use "the Analytics opt-out browser add-on". Check: none, and do not estimate it.
- Declined consent. Google says "Analytics will be missing data for users who decline consent" (Behavioral modeling for consent mode). Check: your consent mode and reporting identity.
- Server-side URL rewrite. Some sites "serve error pages when you include those parameters". Google gives no direction; our reading is that an error page without the tag loses the session. Check: step 5 below.
- Redirects. When a redirect drops the gclid, Google's fix is: "Ensure your Google Tag (for Google Analytics) fires before any redirects occur." Check: step 5 below.
- Demand Gen and YouTube. Google says "differences between clicks and sessions can be more pronounced" there, without a direction. Compare them separately.
- Known bots. "In Google Analytics properties, traffic from known bots and spiders is automatically excluded," and you cannot "see how much known bot traffic was excluded" (Known bot-traffic exclusion). Our reading: a known-bot click Google Ads did not filter stays a click with no session. Check: none; for what the filter misses, see bot signals inside GA4.
In basic consent mode, "Google tags are completely blocked from firing" for users who decline, so their ad clicks produce no GA4 session. In advanced consent mode, "the Google tags send cookieless pings" (About consent mode). GA4 then models the missing user and session data only when the property is eligible, which needs "at least 1,000 events per day with analytics_storage='denied' for at least 7 days" among other criteria, and shows modeled data only under the Blended reporting identity.
Our verdict: fix tags, redirects, consent setup and load speed first. Unfiltered invalid clicks can also land here, so traffic quality comes last. For the causes that do cost money, see why your Google Ads budget gets wasted.
Why can GA4 show more sessions than Google Ads clicks?
GA4 shows more sessions than clicks when visitors return, when they come back through bookmarked ad links, and when Google filtered invalid clicks from Google Ads that GA4 still recorded.
Google calls this the good case: "Having more sessions than clicks is actually an indication of positive engagement."
- Returning users. Google says "you can expect to see more sessions than clicks" and to "cross-segment the campaign by User Type". A later direct visit keeps the campaign, since "The attribution model for sessions stays the non-direct last click attribution model".
- Bookmarks. With a bookmarked gclid URL, "Google Ads doesn't record the clicks and advertisers are not charged", while Analytics records the visits.
- Filtered invalid clicks. "Google Ads automatically filters certain clicks from your reports, while Analytics reports on all the resulting sessions," says the troubleshooter. Filtered clicks "are filtered out of your campaign metrics and removed from your billing" (Invalid clicks: Definition).
Filtering lowers clicks and leaves the session, so invalid traffic that Google catches pushes sessions up relative to clicks, not down. Reading the Invalid clicks and Invalid interactions columns is covered in how to check invalid clicks in Google Ads.
Why are Google Ads clicks missing from GA4 or showing as organic, direct or (not set)?
Google Ads traffic is missing from GA4, or lands under organic, direct or (not set), when the accounts are not linked, auto-tagging is off, privacy parameters such as WBRAID or GBRAID are used, the link settings are wrong, or the gclid is lost before the tag fires.
- Auto-tagging off. The traffic "may be attributed to Google Organic", which can show "as organic, direct, or (not set)".
- WBRAID and GBRAID. Google Ads dimensions "may display as '(not set)' if using WBRAID or GBRAID." Google's fallback, under "Turn on manual tagging", is UTM parameters alongside auto-tagging, such as
?utm_source=google&utm_medium=cpc&utm_campaign=DemandGenCampaignName. - Link settings. Check the Import and Export Settings the troubleshooter names. Unlinked traffic with a gclid "will still appear in reports by default with a source/medium of google/cpc", while new Google Ads dimensions "will appear as (not set)", says Google's linking page.
- Google's missing-data causes. "Google Ads account and Analytics property are not linked", "Auto-tagging is not enabled" and "Google Ads GCLID parameter lost in redirects" (Missing Google Ads data in Google Analytics property).
These sessions are filed under the wrong channel, not missing, so compare total landing-page sessions too. To trace single clicks, match GCLIDs click by click in the Click view report.
How to reconcile Google Ads clicks and GA4 sessions, step by step
Work from reporting mechanics to tagging to visitor behavior, and only then read what is left.
Work through these steps in order:
- Pick complete days ending yesterday or earlier, and compare whole weeks if the time zones differ.
- Find the link date in the Date linked column of your Google Ads links, then drop earlier days and the first 48 hours.
- Compare campaign by campaign, using what Google calls the "Google Ads campaigns report" in GA4. Use Sessions, not Users or Engaged sessions. That is our rule of thumb, not Google's.
- Add the Invalid clicks and Invalid interactions columns in Google Ads.
- Test each final URL with Google's
?gclid=TesTER-123parameter and confirm it survives the page load. - Confirm auto-tagging is on and the tag fires on every landing page before any redirect, then check organic, direct and (not set) for those pages.
- Check which consent mode runs and whether you read the Blended reporting identity.
- Check the campaign's Returning users metric (Google's troubleshooter calls this cross-segmenting by User Type), and read Demand Gen, YouTube and call-heavy campaigns separately.
- Track the gap per campaign over time. Our rule of thumb, not Google's: a change that survives steps 1 to 8 is the one worth a closer look.
Google's test for step 5 starts in Google Ads, on its missing-data page: "In the page menu on the left, click Landing pages," copy a URL, "Attach the test parameter ?gclid=TesTER-123 to the URL and press Enter," then check it "remains in the URL in its original form".
On 16 November 2026 we ran step 5 from the command line on our own Google Search page, and the parameter survived every redirect. That request does not run the tag, so Google's browser test still applies.
The causes behind each step, and which way each pushes the numbers:
| Cause | Effect on the numbers | What to check |
|---|---|---|
| Different metrics (repeat clicks in one session) | More clicks | No fix needed; Google expects this |
| The server delays (visitor leaves first) | More clicks | Page and tag load speed |
| Page never loads; phone-number clicks | More clicks | Hosting uptime; report call clicks separately |
| Tag missing or not loading | More clicks | Tag on every final URL |
| Browser preferences | More clicks | Not measurable; do not estimate |
| Declined consent (basic mode blocks the tag) | More clicks | Consent mode; Blended reporting identity |
| Server side URL rewrite; redirects | More clicks or misattribution | Final URL with ?gclid=TesTER-123; tag before redirects |
| Demand Gen and YouTube | Either; Google gives no direction | Compare those campaigns separately |
| Known bots excluded by GA4 | More clicks | None; GA4 shows no count |
| Invalid clicks filtered from Google Ads | More sessions | Invalid clicks and Invalid interactions columns |
| Users return during a campaign | More sessions | Returning users metric (Google: User Type) |
| Users return to your site via bookmarks | More sessions | None; Google Ads does not count or charge these |
| Auto-tagging off; WBRAID or GBRAID; link settings | Filed as organic, direct or (not set) | Auto-tagging; UTM fallback; link settings |
| Not linked yet, or within 48 hours of linking | Missing Google Ads data (campaign shows as (not set)) | Date linked; skip the first 48 hours |
| Time zones; estimated sessions | Day-level mismatch | Whole days, matching time zones |
Sources: the Google pages above. Google states a direction for repeat clicks, server delays, tag and browser problems, returning users, bookmarks and filtered invalid clicks. The other effects are our reading.
Does a gap between clicks and sessions mean click fraud?
No, not on its own: on a related page Google says discrepancies with other tracking "don't necessarily mean" invalid activity, and in our reading invalid clicks can push the gap either way.
Google says this about gaps between Google Ads and web logs or third-party tracking tools: "While these discrepancies may be significant and at times surprising, they don't necessarily mean that there was some sort of invalid activity with your ads." (Differences between Google Ads and third-party data). The same reasoning applies to GA4: a gap is not a finding.
Our reasoning, not a measurement: filtered invalid clicks raise sessions relative to clicks. Unfiltered bots that click and never run the tag would widen the gap on the clicks side. Bots that load the page and run the tag show as sessions and close it. So the gap's size cannot separate fraud from setup. Bot clicks show up in click-level behavior, as how bot traffic hits Google Ads campaigns explains.
Read a change in the gap by campaign, network, device and hour. If one campaign moves alone, check its sessions for the bot signals linked above.
Where ClickFortify fits
ClickFortify does not reconcile Google Ads clicks with GA4 sessions. It adds a third view: each visit that loaded your landing page, scored for fraud.
ClickFortify scores each visit that loads the landing page on 100+ device, network and behavior data points, so the visits it scores will not equal Google Ads clicks or GA4 sessions. Like GA4, it cannot see clicks that never load the page, call assets or Google lead form assets, so validate those leads in your CRM. ClickFortify never filters or edits conversions in Google Ads.
Flagged sources are added to Google Ads IP exclusions automatically, at IP level. Every block keeps a click record (timestamp, IP, device and network data, behavior on the landing page, the gclid when present). You can use that record in an invalid-click credit request through Google's Click Quality Form. ClickFortify does not file the request for you and cannot promise Google will grant a credit. See ClickFortify for Google Search for the setup.
The verdict on Google Ads clicks vs GA4 sessions
The gap between Google Ads clicks and GA4 sessions is a measurement question first. Once Google's documented causes are ruled out, a change in it is a reason to look at click-level evidence, not a finding. If that evidence points to invalid clicks, the Google Ads click fraud response plan covers what to do next.
Meta Ads has the same kind of gap between link clicks, counted on the ad, and landing page views, counted after the page loads: see Meta link clicks vs landing page views. For every related guide, see all Google Ads click fraud guides.




