Reference → Reports — SG-Dashboard Analytics

Reports

Field	Value
Audience	public
Page type	reference
Area	sg-dashboard
Updated	2026-05-14

How analytics reports work in SG-Dashboard — scheduled, on-demand, report-shape inventory.

Reports in SG-Dashboard Analytics is the surface that delivers structured analytics packages — scheduled or on-demand — to operators at the account tier. Where the Analytics rollup view is real-time browsing and Event Logs is raw history, Reports is packaged delivery. This page is the Reference definition of the Reports sub-page.

What is this for?

Read this page when you want the structural definition of report generation and delivery — what report shapes exist, how scheduling works, and how on-demand generation differs from scheduled cadences.

Good use cases

You need a packaged report for a stakeholder review.
You are scoping recurring reporting cadences for an operations rhythm.
You hit a "where is the weekly report?" question and want the model laid out.
You are designing internal SOPs around report-cadence ownership.

What NOT to use this for

Step-by-step report procedures — open the relevant Guide.
Per-release shipped report change — open What's New or Changelog.
Custom event taxonomy — out of scope.
Real-time browsing — Analytics parent or Event Logs.

How this connects to other features

Analytics — parent Reference area.
Event Logs — raw event view (complement to packaged reports).
Reporting Automations — automation layer that drives scheduled report delivery.
SG-Dashboard Overview — parent surface.

Definition

Reports in SG-Dashboard Analytics is the structured delivery surface for analytics packages. Each report has a defined shape (what metrics it covers), a scope (per-site or account-tier), and a delivery mode (scheduled or on-demand).

The defining property is packaged. Reports deliver pre-shaped analytics rather than open-ended browsing.

Purpose

The purpose of this page is to define report generation and delivery as a Reference layer rather than as a configuration walkthrough. It explains report shapes, scheduling, on-demand, and how the surface pairs with the broader Reporting Automations framework.

Scope

This page covers Reports at the Reference level.

The page covers:

The report shapes the surface supports.
Scheduled vs on-demand delivery.
The report inventory at the account tier.
The boundary against real-time browsing and against custom-event work.

The page does not cover:

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

Report shapes

The platform supports report shapes that match common operator review cadences.

Traffic summary

Per-site or account-tier traffic over a defined window. Includes top pages, top referrers, conversion summary.

Portfolio rollup

Account-tier rollup across every site under the account. Comparative views, top-performers, total-portfolio metrics.

Conversion summary

Form-submission, store-checkout, signup conversions over a defined window.

Custom report

Operator-configured report combining metrics from across the available shapes.

Account · Analytics · Reports

Reports inbox

Weekly traffic summary · PortfolioScheduledDelivered 1h ago · weekly cadence · 4-page PDF

Conversion summary · marketing.exampleScheduledDelivered 1h ago · weekly cadence · 2-page PDF

Custom · Q2 stakeholder reviewOn-demandGenerated 2d ago by jerome@sgen.com

Monthly portfolio rollupScheduledDelivered 4d ago · monthly cadence

Scheduled vs on-demand

Reports are delivered in two modes.

Scheduled

Driven by Reporting Automations. The report runs on a defined cadence (daily, weekly, monthly). Notification Logic delivers the report when each cadence boundary completes.

On-demand

Operator-triggered for ad-hoc review or stakeholder request. The report generates immediately and lands in the inbox.

The reports inbox

The Reports surface presents an inbox view — most recent reports first, with delivery mode and cadence visible per entry.

Browse

Default reverse-chronological. Filters by report shape and by cadence.

Open

Click into a report to view the full content. Reports are downloadable as PDF.

Constraints and boundaries

Reports is a Reference area for the packaged delivery surface. It is not a substitute for real-time browsing or for raw event diagnosis.

Use this Reference for:

Understanding the report shapes available.
Confirming the scheduled-vs-on-demand model.
Reasoning about report delivery cadence.

Do not use this Reference for:

Real-time analytics browsing — Analytics parent.
Raw event detail — Event Logs.
Per-step procedures — Guides.

Public boundary

This page is intentionally public-safe. It does not expose report-engine internals or protected operational identifiers.

Examples

Example 1 — Account owner reviews weekly portfolio rollup

The owner opens the Reports inbox every Monday, opens the weekly portfolio rollup, scans for notable changes. The Reference frames what the report covers; the operational inbox delivers it.

Example 2 — Stakeholder needs an ad-hoc Q2 summary

The operator triggers an on-demand custom report for the Q2 review window. The report generates and lands in the inbox; the operator downloads as PDF for the stakeholder meeting.

Example 3 — Operator changes the weekly cadence

The operator opens cadence management, switches the weekly traffic summary cadence from Monday to Friday. The next delivery happens Friday; future runs follow the new cadence.

Documentation guidance

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

Reading order

Open this page when scoping packaged report delivery or troubleshooting missing-report questions. Pair with Reporting Automations for the cadence-driving automation layer.

Vocabulary cross-reference

Report is a structured analytics package.
Report shape is the defined metric set the report covers.
Scheduled delivery is automated cadence-driven generation.
On-demand generation is operator-triggered ad-hoc generation.
Reports inbox is the surface that lists delivered reports.

Maintenance discipline

When report behavior changes across releases (new shape, new cadence option, new on-demand surface), update this Reference and log the change in Changelog.

Guides

Reference

Changelog

Roadmap