Search Console measures activity in Google Search; GA4 records measured site interactions. Their totals differ for valid reasons. Use the combined view to find patterns, then investigate each system at its source.
Set up comparable views
- Add Search Console and GA4 as separate data sources. Start with separate charts: clicks/impressions from Search Console; sessions/key events from GA4.
- Align date range, country, device, and the closest available page dimension. Label the source and metric on every chart; show each system’s totals independently.
Join only at a defensible grain
- If you blend by date and landing page, normalize host, path, query parameters, redirects, and date timezone first. Test one-to-many matches before charting.
- Do not attribute a query to a GA4 session with an invented key. Record exclusions, freshness, and source scopes; describe differences as a diagnostic signal, not a tracking failure.
Example and expected result
- Synthetic join check: GSC has
/pricingwith 100 clicks across 2 query rows; GA4 has 80 sessions across 3 campaign rows. If the blend keeps query and campaign dimensions, joining only on page can create up to 6 rows and repeat totals. Keep source scorecards separate; aggregate both inputs to the same URL and period before comparing. Record row counts and totals before and after the blend. - If blended totals differ from source totals, inspect date range, URL normalization, aggregation and join keys. A blend cannot prove query-to-session attribution; report clicks and sessions as separate metrics. For daily charts, account for Search Console’s Pacific Time day boundary and GA4’s property timezone; use longer windows if they differ.