Data sampling means that a report is calculated from a subset of the available data and the result is extrapolated. Google defines it for Analytics as analyzing a subset of data to find meaningful information in a larger data set. In SEO it mostly shows up in Google Analytics.
When does GA4 sample?
Sampling can happen in standard reports, explorations and custom requests. Some third-party guides state that standard reports are never sampled. Google gives a threshold of 10 million events per query for standard properties. For Analytics 360 properties the limit is up to 1 billion events, with a default of 100 million for faster results.
A data quality icon shows when a report is sampled and what percentage of the data was used. A higher percentage means a more accurate estimate. Filtering by country, for example, can trigger sampling in Explore reports even when more data is requested, because filtered queries are processed differently.
| Aspect | Google Search Console | Google Analytics 4 |
|---|---|---|
| Visibility in Search | Impression: a link to the site was seen (or potentially seen) in Search, Discover or News | no own data; once linked, GA4 shows Search Console metrics in dedicated reports |
| Visit from Search | Click: for most result types, any click that sends the user to a page outside Google Search, Discover or News | records the visit on the site (session, events); clicks from Google Search only through the Search Console link |
| Session | no such metric | Session: starts with a page or screen view when no session is active and times out after 30 minutes of inactivity by default |
| Page views | no such metric | Views: number of web pages or app screens users saw, repeated views included |
| Data source | Google's data on how the site appears in Google Search | events sent by the Google tag (JavaScript) on the site; visits without JavaScript enabled are missing |
| Delay | data usually available in 2–3 days; the newest data can be preliminary | processing can take 24–48 hours; Search Console data appears in GA4 48 hours after collection |
| Privacy | anonymized queries: very rare queries are omitted from the table but included in chart totals | data thresholds: rows with demographic data or search query information may be withheld when there are too few users; not adjustable |
| Completeness (this term) | data truncation: only the most important rows are stored and shown, the table shows up to 1,000 rows; the most complete list comes from the bulk data export | sampling: if a query exceeds the event quota (10 million events for standard properties), a subset is used and scaled up |
Search Console clicks and GA4 sessions count different things, so their numbers differ. Google lists privacy, processing, time lag, time zones (Search Console counts days in Pacific Time) and JavaScript among the reasons. The two help pages give different delays (2–3 days in the Search Console Help, 48 hours in the GA4 Help on the integration). Sources: Search-Console-Hilfe: Impressionen, Position und Klicks; Search-Console-Hilfe: Leistungsbericht – Fehlerbehebung und Datenabweichungen; Search-Console-Hilfe: Leistungsbericht – Dimensionen und Datengruppierungen; Search-Console-Hilfe: So werden Klicks und Impressionen gezählt (vorläufige Daten); Analytics-Hilfe: [GA4] Analytics-Sitzungen; Analytics-Hilfe: [GA4] Dimensionen und Messwerte; Analytics-Hilfe: Datenaktualität; Analytics-Hilfe: [GA4] Datengrenzwerte; Analytics-Hilfe: [GA4] Stichprobenerhebung; Analytics-Hilfe: [GA4] Search Console-Integration; Analytics-Hilfe: [GA4] Datenerfassung für Websites einrichten. Last checked: .
What can reduce it?
Google suggests shortening the date range. Using fewer filters and splitting a large question into several queries also lowers the number of events per query (assessment).
Example
A twelve-month report by landing page and country exceeds the event limit and is sampled. Running it quarter by quarter keeps each query below the limit. (Invented example.)
Sources
Last updated: