Analytics and Reporting Workflow

How analytics flows from ingest to operator-facing report — end-to-end path.

The Analytics and Reporting Workflow is the cross-product process for analytics data — from the moment events are captured (per Lead and Tracking Workflow + integration ingest) through aggregation in SG-Dashboard Analytics through scheduled report generation and operator delivery. This page is the Reference definition of the end-to-end analytics flow.

What is this for?

Read this page when you want the structural definition of how analytics data moves through SGEN — from raw event capture to operator-facing report.

Good use cases

• You are scoping analytics workflows for an operations rhythm.
• You are explaining to a stakeholder how SGEN's analytics path works end-to-end.
• You hit a "where does our weekly report come from?" question and want the model laid out.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• Per-release shipped change — open What's New or Changelog.
• Custom event taxonomy work — out of scope.

How this connects to other features

• Workflows Overview — parent Reference area.
• Lead and Tracking Workflow — sibling that captures the events this workflow surfaces.
• Analytics — the rollup view this workflow feeds.
• Reports — the packaged delivery surface this workflow ends at.
• Google Analytics 4 — primary ingest source.

Definition

The Analytics and Reporting Workflow is the cross-product process from event capture to report delivery. It pulls together the integration ingest layer (typically GA4), the platform's aggregation layer (SG-Dashboard Analytics), and the report-delivery layer (Reports + Reporting Automations).

The defining property is end-to-end. The workflow covers raw event → aggregate trend → packaged delivery as one continuous path.

Purpose

The purpose of this page is to define the analytics-and-reporting end-to-end flow as a Reference layer. It explains the four stages (ingest, aggregation, report generation, delivery) and how they pair with the underlying primitives.

Scope

This page covers the workflow at the Reference level.

The page covers:

• The ingest stage (where raw events come from).
• The aggregation stage (rollup views).
• The report generation stage (scheduled or on-demand).
• The delivery stage (notification + inbox).

• Per-step analytics setup — Guides.
• Custom event taxonomy — out of scope.
• Per-release shipped change — What's New or Changelog.

The four stages

Stage 1 — Ingest

Raw events are captured by the integration layer (GA4 by default for traffic events; other integrations for other event types). Events flow into the platform's analytics surfaces.

Stage 2 — Aggregation

SG-Dashboard Analytics aggregates per-site events into rollup views. The rollup is real-time browsable.

Stage 3 — Report generation

Reporting Automations runs scheduled report generation on defined cadences. On-demand reports also generate at this stage when operators trigger them.

Stage 4 — Delivery

The generated report lands in the Reports inbox. Notification Logic delivers the alert; the operator opens the report.

Where each stage lives

• Stage 1: Integrations layer (GA4 + other ingest sources).
• Stage 2: SG-Dashboard Analytics + per-site SG-Admin Analytics.
• Stage 3: Reporting Automations (Automation Reference area).
• Stage 4: SG-Dashboard Analytics → Reports inbox + Notification Logic.

Constraints and boundaries

This Reference covers the cross-product analytics flow.

Use this Reference for:

• Understanding the end-to-end analytics path.
• Routing analytics-related questions to the correct stage.

• Step-by-step procedures — Guides.
• Custom event taxonomy — out of scope.
• Per-release shipped change — What's New or Changelog.

Public boundary

This page is intentionally public-safe.

Examples

Example 1 — Weekly traffic report arrives Monday morning

Stage 1: GA4 captures traffic across the week. Stage 2: aggregation updates the rollup. Stage 3: Reporting Automations generates the weekly traffic report on Monday cadence. Stage 4: Reports inbox + email notification deliver to the operator.

Example 2 — Operator triggers on-demand report

Stage 1 + 2 are continuously running. Stage 3 fires on operator action; Stage 4 delivers immediately.

Example 3 — Stale report indicates upstream issue

The weekly report shows stale numbers. The operator walks the workflow stages, identifies that the issue is upstream at Stage 1 (GA4 connection unhealthy), and proceeds to the GA4 Reference for diagnosis.

Documentation guidance

Use this page as the structural definition for the end-to-end analytics flow. Per-stage detail lives in the corresponding stage References.

Reading order

Open this page when scoping analytics operations or troubleshooting end-to-end analytics questions.

Related reading

• Workflows Overview — parent Reference area.
• Lead and Tracking Workflow — capture sibling.
• Analytics — Stage 2 surface.
• Reports — Stage 4 surface.
• Google Analytics 4 — Stage 1 ingest.
• Reporting Automations — Stage 3 automation.
• Form Submission Workflow — upstream capture workflow.

Vocabulary cross-reference

• Ingest is the stage where raw events arrive in SGEN.
• Aggregate is the stage where per-site events feed account-tier rollups.
• Generate is the stage where reports are produced from aggregated data.
• Deliver is the stage where the report reaches the operator.

Maintenance discipline

When the analytics-and-reporting workflow changes across releases (new ingest source, new aggregation surface, new report generation rule, new delivery channel), update this Reference and log the change in Changelog.

Related reading