They will never match
Search Console counts clicks from search results. Analytics counts sessions, by its own rules and its own consent state.
Different tools, different definitions, different totals.
A filled reconciliation
Brightwater Dental, September 2026.
source measure value denominator
search impressions 1,860 n/a
search clicks 41 impressions
search click rate 2.20% 41 / 1860
analytics sessions 118 n/a
analytics sessions from search 71 all sessions
analytics engaged sessions 61 118 sessions
analytics generate_lead events 9 118 sessions
form inbox stored enquiries 7 n/a
the gap, explained
41 search clicks, 71 sessions attributed to search.
Three reasons, all expected:
1. a click that never ran the tag, because consent was declined
2. a session counted twice, from a return visit
3. attribution windows that do not line up with a calendar month
what to report
- search clicks from search console, as measured
- sessions from analytics, with consent named
- stored enquiries from the inbox, as the floor
what not to report
- an average of the two click or session figures
- a conversion rate dividing inbox enquiries by sessions
Why the inbox is in the table
It is the one number that survives a consent decline. It is a stored record on your own server, not a tag firing in a browser.
Acceptance: the reconciliation is honest when
- each number names its source and its window
- both periods are the same length
- the gap between sources is explained, not averaged
- consent’s effect is named on the analytics rows
- no ratio mixes a numerator from one source with a denominator from another
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Averages look sensible | Two different definitions were merged | Report each source separately |
| Sessions exceed clicks by 3x | Consent blocks the tag for most visitors | Name the consent rate |
| Events exceed stored enquiries | Phone clicks, or a second form | Name the difference |
| A month looks very different | A shorter period, or a timezone shift | Write both ranges and both timezones |
| A client compares to their own dashboard | A different date range | Agree the range before explaining |
Limits
This page describes our own connectors, not another product’s features.
Both sources can be missing. A report with one connected says so rather than filling the gap with an estimate.