Reference → Google Analytics 4

Google Analytics 4

How Google Analytics 4 connects into SGEN — site analytics ingest and dashboard surfacing.

Google Analytics 4 (GA4) connects into SGEN as the site-analytics ingest layer. Once configured, GA4 data feeds into the platform so account-level rollups appear in SG-Dashboard reporting and per-site analytics surfaces appear inside the admin Analytics. This page is the Reference definition of the GA4 integration — what it covers, where the data appears, and what the dependency posture looks like.

What is this for?

Read this page when you want the structural definition of the GA4 integration in SGEN — what role it plays in the platform's analytics layer, where the data lands, and what the operator should expect when the connection is healthy versus when it is unhealthy.

Good use cases

  • You are scoping site analytics for a new SGEN site and need to know how GA4 fits.
  • You are explaining to a stakeholder how SGEN handles connected analytics.
  • You hit a "is the analytics number correct?" question and want the model laid out.
  • You are designing internal SOPs around analytics handoff.

What NOT to use this for

  • Step-by-step GA4 setup procedures — open the relevant Guide.
  • GA4 product documentation — that lives in Google's documentation, not here.
  • Per-customer reporting customizations — internal-only or per-customer support.
  • Per-release shipped behavior change — open What's New or Changelog.

How this connects to other features

Definition

GA4 in SGEN is a connected analytics service. The platform pulls GA4 data into the SGEN administrative surface so operators see analytics inside the platform rather than only in the GA4 web app.

The defining property is direction. GA4 is a one-way ingest — analytics events generated by visitors flow through GA4's collection layer and into the SGEN surfaces that consume the data. SGEN does not push data back to GA4.

Purpose

The purpose of this page is to define the GA4 integration as a Reference layer rather than as a configuration walkthrough. It explains the connection model, where the data appears, what the dependency posture looks like, and how the integration pairs with the broader analytics surface.

Scope

This page covers the GA4 integration at the Reference level.

The page covers:

  • The connection role of GA4 in the SGEN analytics layer.
  • Where GA4 data appears in SG-Dashboard and SG-Admin.
  • The dependency posture (healthy connection vs unhealthy connection).
  • The boundary against GA4 product documentation and per-customer customizations.
The page does not cover:
  • Per-step setup procedures — Guides.
  • GA4 product detail — Google documentation.
  • Custom GA4 event configuration beyond platform defaults — per-customer scope.

Connection model

GA4 connects into SGEN through the platform's standard integration surface. The connection is account-tier (configured once at SG-Dashboard) and applies per-site (each site can use its own GA4 property).

Per-site property

Each SGEN site can be paired with a GA4 property. The pairing is configured in the per-site settings; the data flows through the GA4 property and into the per-site SGEN analytics surface.

Multi-site rollups

When multiple sites in an account each have GA4 properties paired, SG-Dashboard surfaces account-level rollups across the connected sites. The rollup is a portfolio view; per-site detail still lives at the per-site surface.

Site Settings · Integrations

Google Analytics 4

Connected

Where GA4 data appears

GA4 data lands in two operator-facing surfaces.

SG-Dashboard

Account-tier rollups across connected sites appear in the SG-Dashboard reporting surface. Operators running a portfolio see one place to scan multi-site analytics summaries.

SG-Admin Analytics

The per-site Analytics module inside the admin shows the per-site GA4 view. Operators working inside one site see that site's analytics without leaving the administrative surface.

Dependency posture

GA4 in SGEN depends on the GA4 property being healthy and the connection between the property and the SGEN site staying valid.

Healthy connection

Data flows from GA4 into SGEN at the expected cadence. Operators see fresh data in SG-Dashboard rollups and SG-Admin Analytics. Reports generate as scheduled.

Unhealthy connection

Data stops refreshing. The per-site Analytics surface shows stale data; rollups in SG-Dashboard reflect the same staleness. The connection panel surfaces the unhealthy state with a status indicator and a reconnect prompt.

Constraints and boundaries

GA4 is a Reference area for the connected analytics service. It is not a substitute for GA4 product documentation or for custom per-customer reporting work.

Use this Reference for:

  • Understanding the GA4 connection role in SGEN.
  • Confirming where GA4 data surfaces inside the platform.
  • Diagnosing connection-health questions at the structural level.
Do not use this Reference for:
  • GA4 product configuration — Google's documentation.
  • Custom event taxonomies beyond platform defaults — per-customer scope.
  • Step-by-step setup — Guides.

Public boundary

This page is intentionally public-safe. It does not expose GA4 credentials, exact API surfaces, or protected operational identifiers.

Examples

Example 1 — Operator confirms GA4 data is flowing

The operator opens the admin → Analytics, sees fresh GA4 data, confirms the connection is healthy. The Reference frames what fresh-data-flowing should look like; the operational surface confirms it.

Example 2 — Stakeholder asks "where does our analytics live?"

The platform lead opens this page (Where GA4 data appears section) and walks the stakeholder through the two surfaces — SG-Dashboard rollups and SG-Admin Analytics. The Reference gives a clear answer in the platform's vocabulary.

Example 3 — Connection goes unhealthy after a GA4 property change

A property-side change breaks the connection. SG-Admin Analytics shows stale data. The operator opens this page (Dependency posture section), confirms the unhealthy-connection symptom matches, and reconnects via the connection panel.

Documentation guidance

Use this page as the structural definition for the GA4 integration. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.

Reading order

Open this page when scoping site analytics or troubleshooting analytics-data-staleness questions. Pair with SG-Admin Analytics Reference for the per-site surface, and with SG-Dashboard Reporting Reference for the multi-site rollup surface.

Related reading

Vocabulary cross-reference

  • GA4 property is the Google-side configuration that defines a measurement scope.
  • Measurement ID is the per-property identifier used to pair the GA4 property with an SGEN site.
  • Healthy connection means data is flowing at the expected cadence.
  • Unhealthy connection means data has stopped refreshing or the connection state shows an error.
  • Multi-site rollup is the account-tier view that aggregates GA4 data across connected sites.

Maintenance discipline

When the GA4 integration changes across releases (new connection panel, new data surface, new measurement option), update this Reference and log the change in Changelog. The page stays valuable because the connection model stays small.

On this page