Reference → Reporting Automations

Reporting Automations

How reporting cadences and report-generation cycles are automated in SGEN.

Reporting Automations in SGEN is the category of scheduled processes whose purpose is to generate operator-facing reports on a recurring cadence. Daily traffic summaries, weekly portfolio rollups, monthly billing-adjacent summaries — every report that arrives without an operator manually requesting it falls inside this category. This page is the Reference definition of the category.

What is this for?

Read this page when you want the structural definition of SGEN's reporting-automation category — what reports the platform generates on a cadence, how scope works, and how the reports reach the operator.

Good use cases

  • You are scoping operator-facing reporting and need the automation model.
  • You are explaining to a stakeholder how SGEN handles automated portfolio reporting.
  • You hit a "the weekly report didn't arrive" 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 configuration procedures — open the relevant Guide.
  • Per-release shipped report additions — open What's New or Changelog.
  • The Schedule primitive itself — open Scheduled Processes.
  • Per-report metric definitions — corresponding Reference page where defined.

How this connects to other features

Definition

Reporting Automations in SGEN is the category of scheduled jobs whose purpose is to generate and deliver operator-facing reports. Each reporting automation has three parts: the scope (per-site or account-tier), the cadence (when it runs), and the delivery (how the report reaches the operator).

The defining property is recurring. Reporting automations run on cadences without per-cycle operator action; they exist to keep operators informed without requiring them to remember to pull the report.

Purpose

The purpose of this page is to define the reporting-automation category as a Reference layer. It explains the report shapes the platform generates, the scope and cadence model, and how delivery pairs with Notification Logic.

Scope

This page covers reporting automations at the Reference level.

The page covers:

  • The kinds of reports the platform generates on a cadence.
  • The scope model (per-site vs account-tier).
  • The delivery model (where the report lands, who sees it).
  • The boundary against per-report metric definitions and the Schedule primitive itself.
The page does not cover:
  • Per-step report configuration — Guides.
  • Per-report metric definitions — corresponding Reference page where defined.
  • Per-release shipped report additions — What's New or Changelog.

Report shapes

The platform supports several report shapes by default.

Per-site traffic summary

Daily or weekly summary of site traffic, sourced from the analytics integration layer (Google Analytics 4 by default). Per-site scope.

Multi-site portfolio rollup

Weekly or monthly rollup that aggregates traffic, conversion, and operational signals across every site under the account. Account-tier scope, surfaced in SG-Dashboard Reports.

Billing-adjacent summary

Monthly summary of billing-relevant signals — subscription state, capacity utilization, payment-related events. Account-tier scope.

Audit-log rollup

Weekly or monthly rollup of admin actions captured in the audit-log layer. Account-tier scope, surfaced for compliance and operational review.

Custom-report cadences

Custom cadences for reports that operators configure beyond the defaults. The shape is the same; only the metric set and cadence are customized.

Account · Reports · Inbox

Scheduled reports

Weekly traffic summary · marketing.examplePer-siteDelivered 1h ago · weekly cadence
Portfolio rollup · last 7 daysAccountDelivered 1h ago · weekly cadence
Monthly billing summary · AprilAccountDelivered 4d ago · monthly cadence
Audit-log rollup · last 7 daysAccountDelivered 6h ago · weekly cadence

Delivery model

Reporting automation delivery uses Notification Logic.

Notification with link

Notification Logic delivers an in-app or email notification carrying a link to the report artifact. The operator clicks through to the report.

Direct artifact in module

The report itself surfaces inside the admin Analytics (per-site reports) or SG-Dashboard Reports (account-tier reports). The notification is the announcement; the artifact is the destination.

Per-recipient routing

The recipient scope (operator, role, account) follows Notification Logic's recipient model. Reports go to the right operators without manual per-cycle distribution.

Constraints and boundaries

Reporting Automations is a Reference area for the recurring report-generation category. It is not a substitute for the Schedule primitive itself or for per-report metric Reference.

Use this Reference for:

  • Understanding the report shapes the platform generates on cadences.
  • Confirming scope and delivery for any reporting automation.
  • Diagnosing missing-report questions at the structural level.
Do not use this Reference for:
  • The Schedule primitive — Scheduled Processes Reference.
  • Per-report metric definitions — corresponding Reference page.
  • Step-by-step configuration — Guides.

Public boundary

This page is intentionally public-safe. It does not expose report-generation internals, exact metric formulas, or protected operational identifiers.

Examples

Example 1 — Weekly traffic summary arrives Monday morning

The per-site weekly traffic summary runs every Monday at 09:00 local. Notification Logic delivers an in-app notification with a link; the report itself lives in the admin Analytics for the operator to open. The cadence runs without operator action.

Example 2 — Portfolio rollup informs an account review

The account-tier portfolio rollup runs weekly. The account owner opens the rollup in SG-Dashboard Reports during a review meeting. The rollup aggregates across every site and surfaces top-line signals.

Example 3 — Stakeholder asks "what reports do we get automatically?"

The platform lead opens this page (Report shapes section) and walks the stakeholder through the default-scheduled set: per-site traffic summary, multi-site portfolio rollup, billing-adjacent summary, audit-log rollup, and any custom cadences the team has configured. The Reference grounds the conversation in the platform's reporting model.

Documentation guidance

Use this page as the structural definition for the reporting-automation category. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog. Cross-reference Scheduled Processes for the cadence primitive and Notification Logic for the delivery seam.

Reading order

Open this page when scoping operator-facing reporting or troubleshooting missing-report questions. Pair with Scheduled Processes for the cadence model and Notification Logic for the delivery layer.

Related reading

Vocabulary cross-reference

  • Reporting automation is a scheduled job that generates and delivers an operator-facing report.
  • Report shape is the type of report (traffic summary, portfolio rollup, billing summary, audit-log rollup, custom).
  • Cadence is when the report runs.
  • Scope is what the report covers (per-site or account-tier).
  • Delivery is how the report reaches the operator (notification + artifact).

Maintenance discipline

When reporting-automation behavior changes across releases (new report shape, new delivery channel, new cadence option), update this Reference and log the change in Changelog. The page stays valuable because the three-part shape (scope / cadence / delivery) stays small and consistent with the broader Schedule and Notification primitives.

On this page