GA4 & Looker Studio · The Google Analytics Ecosystem

GA4 sits at the centre of Google's digital analytics ecosystem. Each surrounding tool serves a specific function that GA4 alone cannot perform:

Each tool connection is configured separately and serves a distinct analytical purpose. A fully connected ecosystem answers questions no single tool can: "Which organic search queries are driving users who later convert through email?" requires GA4 (for the conversion event and attribution) + Search Console (for the organic queries) data in the same report — available via Looker Studio's multi-data-source blending.

GA4 processes and stores event data, applies attribution models, generates standard reports, and provides the Exploration workspace for custom analysis. It is the single source of truth for on-site user behaviour data — everything else in the ecosystem either feeds data into GA4 or reads data out of GA4 for further processing or presentation.

GA4's two primary output channels are: the reporting interface (standard reports and explorations, accessible in the GA4 interface at analytics.google.com) and the API (the GA4 Data API, which enables programmatic access to GA4 report data from external tools including Looker Studio and BigQuery). Understanding that Looker Studio reads from the GA4 Data API — not from GA4's internal database directly — explains some of Looker Studio's limitations, particularly around data freshness and the metrics available in the connector.

Google Tag Manager is the data collection layer: it fires the GA4 tracking tag when specified user interactions occur (page loads, button clicks, form submissions, scroll depth, etc.) and passes event parameters to GA4. Without GTM (or direct gtag.js implementation), GA4 has no data to report on.

The GTM → GA4 data flow: a user interaction on the website triggers a GTM trigger; the trigger fires a GA4 Event tag; the tag sends an event with parameters to GA4 via the Measurement Protocol or browser-side Google tag (gtag.js). GA4 receives the event, processes it, and makes it available in reports within approximately 24 hours (standard processing latency) or in the Realtime report within seconds.

Server-side GTM (GTM server container) is an additional layer available for implementations that require server-side processing: instead of the browser sending events directly to GA4, events go to a server-side GTM container first, which then forwards them to GA4 (and other destinations). Server-side GTM improves data quality in privacy-constrained environments where browser-side tracking is blocked by ad blockers or browser privacy features.

Looker Studio (lookerstudio.google.com, formerly Google Data Studio) is Google's free business intelligence and data visualisation tool. It connects to hundreds of data sources (GA4, Google Ads, Google Search Console, BigQuery, Sheets, and third-party connectors) and enables building interactive, shareable dashboards and reports that non-GA4 users can view and interact with via a browser link — no GA4 access required.

Why use Looker Studio instead of GA4 directly?

• Shareable reporting without GA4 access. GA4 access requires adding users to the property with specific role permissions. A Looker Studio dashboard can be shared via URL with anyone — view-only access to selected data without GA4 property access. This makes Looker Studio the right tool for reporting to clients, executives, and stakeholders who need data without managing GA4 access.
• Custom branded dashboards. Looker Studio enables custom layouts, colour schemes, logos, and commentary text — producing branded client reports that look professional rather than standard GA4 report exports.
• Multi-source data blending. Looker Studio can combine data from GA4 + Google Ads + Search Console in a single dashboard or chart — cross-channel reporting that GA4 alone cannot produce.
• Scheduled email delivery. Looker Studio dashboards can be scheduled to email as PDFs — automating regular report delivery without anyone logging into GA4.

Add a GA4 data source in Looker Studio: Create → Data Source → Google Analytics → select the GA4 property → Connect. Looker Studio provides the Google Analytics connector which reads from the GA4 Data API. Once connected, GA4 dimensions (session source, page path, country, device, etc.) and metrics (sessions, conversions, engaged sessions, revenue) are available as chart fields.

GA4 connector limitations to know

• Sampling at large data volumes. The GA4 Data API (which Looker Studio uses) applies sampling for large queries — returning an estimated result based on a sample of sessions rather than all sessions. GA4 360 (the paid version) has higher sampling thresholds. For unsampled data, use the BigQuery export.
• Not all GA4 data is available. The GA4 Data API does not expose all GA4 data — raw event parameters, user-level data, and some exploration-specific dimensions are not available via the connector. These require BigQuery access to the raw export.
• Metric definitions may differ. Some metric definitions in the GA4 connector and in the GA4 interface can diverge slightly due to how the API aggregates data. Always verify key metrics in both GA4 and Looker Studio when first connecting a data source.

GA4 can export raw event-level data to Google BigQuery — a cloud data warehouse where the data can be queried with SQL. The BigQuery export provides access to data that the GA4 reporting interface and API do not expose: every individual event, all event parameters, raw user pseudonymous identifiers, and the complete session reconstruction capability that aggregate reporting suppresses.

When is BigQuery export necessary?

• Analysis requiring raw event-level data (e.g. building a custom session definition different from GA4's default).
• Joining GA4 data with first-party CRM data for customer-level analysis.
• Avoiding GA4 API sampling for high-traffic sites with large data volumes.
• Long-term data storage beyond GA4's 14-month retention limit.
• Building custom machine learning models on behavioural data.

Enable BigQuery export: GA4 Admin → Product Links → BigQuery Links → Link. A Google Cloud Platform account and a BigQuery project are required. GA4's daily export to BigQuery is free (up to 1M events/day in the free tier of BigQuery's storage).

Linking Google Search Console to GA4 (GA4 Admin → Product Links → Search Console Links) brings organic search data into GA4 reports. After linking, the Search Console reports appear under Reports → Acquisition → Search Console in GA4, showing which landing pages receive organic search traffic and (in limited form) which queries drive those sessions.

For more comprehensive cross-source analysis, Looker Studio's data blending feature can combine the GA4 connector (for on-site behaviour and conversions) with the Search Console connector (for queries, impressions, and positions) — matching sessions and conversions to the organic search queries that initiated them. This multi-source blending is the primary use case for combining the two data sources beyond GA4's native Search Console integration.

Linking GA4 to Google Ads (GA4 Admin → Product Links → Google Ads Links) enables two critical integrations: GA4 key events (conversions) can be imported into Google Ads as conversion actions for Smart Bidding; and Google Ads campaign cost, click, and impression data appears in GA4's Acquisition reports alongside session and conversion data.

The Google Ads integration in Looker Studio: the Google Ads connector provides campaign-level cost and performance data (impressions, clicks, cost, conversions) while the GA4 connector provides the on-site behaviour (sessions, engagement, goal completions). Blending these in Looker Studio by campaign name or UTM campaign creates a full-funnel view from ad spend to on-site conversion.

A complete analytics ecosystem setup, in order of implementation:

1. Install GTM container on the website (developer adds the two container snippet blocks).
2. Create GA4 property (Production + Development); deploy GA4 Configuration tag via GTM; verify data in Realtime report.
3. Configure Consent Mode v2 via CMP if site serves EU/UK audience.
4. Implement custom events and conversions via GTM based on the measurement plan.
5. Link Google Search Console to GA4 property.
6. Link Google Ads to GA4 property; import GA4 conversions into Google Ads; enable auto-tagging.
7. Enable BigQuery export if raw data analysis or long-term retention is required.
8. Build Looker Studio dashboards for stakeholder reporting — connecting GA4 data source and any other relevant sources (Ads, Search Console).

Authentic Sources