Describe both populations
State what triggers each observation: click, page load, session or order. A person may click and leave before site measurement starts. Multiple clicks can belong to one journey. Do not assume the reports should reconcile one for one.
Align reporting filters
Compare countries, devices, pages, dates and timezones. Check hostnames and included subdomains too. Canonical grouping in search data and raw URL grouping in site reports can move volumes between rows without changing the total population.
Test collection behaviour
Check an ordinary arrival, the consent choice and internal navigation. Blockers, JavaScript errors and lost parameters can affect measurement. Consent-based collection may not represent every visitor; preserve the person’s choice rather than bypassing it.
Connect diagnosis to an action
Use reports to find pages worth investigating, then inspect the actual journey. Keep definitions and incidents in a shared sheet. An unexplained gap is a diagnostic question, not immediate proof of fraud or disappearing traffic.
- Define
- Align
- Test
- Reconcile
Worked example
Reconciliation sheet: date / page / clicks / sessions / orders / consent / incident. Start with ten representative pages, expanding the checks if a common cause becomes apparent.
Check before moving on
These checkboxes are not saved.
Sources & method
Sources reviewed on 1 October 2026. Worked calculations use explicitly hypothetical inputs.
Topic provenance: Interpréter les données d’Analytics et de Webmaster Tools (2010-02). Search Engine Feng Shui. Byline retained in the publication feed: fhouste.
This guide is newly written in 2026. It does not reproduce the earlier text and is not attributed to its historical author.
Clicks and sessions: reconcile them without inventing lost visitors
A Search Console click and an Analytics session count different events. This fictional case prepares a reproducible comparison; it does not describe your accounts or a measured loss of visitors. Keep both metrics with their definitions.
- Define the scope: the same site and landing pages, Google Web search, a complete period and explicit filters. Record each export’s time zone; the same displayed date can cover different hours.
- Retain the original exports before transforming them. Record how canonical URLs, parameters and redirects are handled. Joining different URL strings can manufacture a discrepancy.
- Compare trends and important pages first. Then investigate consent, measurement triggering, blockers and navigation. These are hypotheses to test, not missing visitors established by subtraction.
- Select one page and an authorised test journey, then check the events actually received with the responsible team. Document the result without changing production settings merely to force equality.
Diagram text: Export A · fictional: 1,200 Google Web clicks; seven complete days; defined scope; Export B · fictional: 900 sessions within the documented Analytics scope; Descriptive calculation: A numerical gap of 300; not proof of 300 people lost
| Field | Example or check |
|---|---|
| Export A · fictional | 1,200 Google Web clicks; seven complete days; defined scope |
| Export B · fictional | 900 sessions within the documented Analytics scope |
| Descriptive calculation | A numerical gap of 300; not proof of 300 people lost |
| Hypothesis to test | A page fails to trigger measurement after consent; status: not tested |
| Test record | URL, time and time zone, consent choice, expected step, observed result and remaining limit |
Do not publish “25% of visitors lost” from 300/1,200. A click is not a person, and sessions have their own measurement rules. If you cannot align the scopes, show the two series separately and state exactly what remains incomparable.