Google Search Console (GSC) and Piano Analytics measure overlapping but distinct phenomena, so their numbers will never match exactly. This article explains the systematic reasons and provides a reconciliation flow when the gap looks too large.
What each tool measures
|
|
Google Search Console |
Piano Analytics |
|---|---|---|
|
Counts |
Impressions and clicks in Google's search interface |
Visits arriving on your site with a Google referrer |
|
Source of truth |
Google's logs |
Your site's tagging firing on landing pages |
|
Sampling |
Aggregated, with privacy thresholds |
No sampling; no approximation when Eco Mode is off |
|
Time zone |
Pacific Time (PT) |
Your site's configured time zone |
|
Source detection |
Inherent (it's Google's own data) |
Inferred from the referrer header |
A "click" in GSC fires when a user clicks your result in Google's search interface. A "visit" in Piano Analytics fires when the visitor's browser successfully loads the landing page and the Piano SDK sends its first event. The gap between these two events is where most of the discrepancy lives.
The four most common causes of GSC > Piano
#1: The visitor never reaches your page
A GSC click is registered before the page loads. If the visitor:
-
Hits "Back" before the page finishes loading,
-
Loses connectivity,
-
Has the Piano SDK blocked by an ad blocker, browser extension, or corporate firewall,
-
Has JavaScript disabled,
…GSC counts the click but Piano Analytics doesn't count a visit.
Expected impact: 5-15% of GSC clicks typically don't materialize as Piano visits.
#2: Referrer stripped at the browser
Some search-result clicks arrive without a recognizable Google referrer — particularly from:
-
Browsers configured with strict referrer policies
-
AMP-served search results (Google's AMP cache may rewrite the referrer)
-
Some mobile in-app browsers (Chrome on Android, in some configurations)
When the referrer is stripped, Piano Analytics records the visit but attributes it to Direct Access or another source — not to Search engines. GSC still has the click in its data; Piano just doesn't see "Google" as the source.
Expected impact: highly browser-dependent, can be 5-30% on certain mobile traffic shares.
#3: Time-zone misalignment
GSC reports use Pacific Time by default. Piano Analytics uses your site's configured time zone. For a daily reconciliation, the two "day" definitions don't align — visitors who clicked late in the GSC day may appear in Piano's next day.
#4: Different "click" definitions
GSC counts a click as a single user action; if a user clicks twice on the same search result, GSC may register two clicks (depending on the time gap). Piano Analytics counts one visit. The ratio of clicks to visits will therefore exceed 1:1 even with everything else perfectly aligned.
Keywords data
GSC's most valuable feature — the queries that drove the click — is not available in Piano Analytics. Piano can identify Google as the source but cannot see the search keyword (Google has not passed keywords in the referrer for years, except via Google Ads). For keyword-level analysis, GSC remains the canonical source — or import GSC data into Piano via Measurements if you want both sources in one analysis.