Analytics (SG-Admin)
| Field | Value |
|---|---|
| Audience | public |
| Page type | reference |
| Area | sg-admin |
| Updated | 2026-05-14 |
The SG-Admin Analytics module — per-site surface for traffic, conversions, operational signals.
The Analytics module in the admin is the per-site surface that surfaces ingest from connected analytics integrations (typically GA4 + GSC) inside the platform. Where SG-Dashboard Analytics rolls up across every site, the admin module shows one site's view. This page is the Reference definition.
What is this for?
Read this page for the structural definition of per-site analytics surfacing.
Good use cases
- You are scoping site-level analytics review cadences.
- You are explaining to a stakeholder how SGEN surfaces analytics inside per-site administration.
- You hit a "where do I see this site's traffic?" question.
What NOT to use this for
- Step-by-step procedures — open the relevant Guide.
- Account-tier rollup — open SG-Dashboard Analytics.
- Per-release shipped change — open What's New or Changelog.
How this connects to other features
- SG-Admin Overview — parent surface.
- SG-Dashboard Analytics — account-tier rollup.
- Google Analytics 4 — primary ingest source.
Where to find it
Open SG-Admin for the active site. Analytics appears in the sidebar under the general reporting group. The module is available to users with Admin or Editor access; read-only users can view but not export.
Definition
The SG-Admin Analytics module is the per-site analytics surfacing surface. It consumes data from connected integrations (GA4, GSC, others) and presents per-site views — traffic trends, top pages, top queries, conversion summary, audience segments.
The defining property is per-site scope. The module shows the active site's data only.
Purpose
Define the admin Analytics module as a Reference layer.
Scope
Covers per-site analytics surfacing. Does not cover account-tier rollup (SG-Dashboard Analytics) or per-step procedures.
What the module shows
Traffic (visits, unique visitors, session duration), conversions (form submissions, store transactions, custom-event conversions), top pages (by traffic, by conversion), top referrers, search performance (where GSC is connected), audience signals.
Site · Your Site · Analytics · Last 28 days
Per-site view
92k
Visits
+11%
31k
Unique
+8%
3.4
Avg session
+0.2
892
Conversions
+14%
| Top page | Visits | Conv |
|---|---|---|
| / | 32k | 247 |
| /pricing | 18k | 187 |
| /blog/post-1 | 12k | 62 |
Constraints and boundaries
Per-site Analytics is a Reference area. Account-tier rollup is separate (SG-Dashboard Analytics). Custom event taxonomy is out of scope.
Public boundary
Public-safe.
Examples
Example 1 — Editor reviews weekly site performance
Editor opens Analytics, scopes to last 7 days for the active site. The module shows 18k visits (+6%), 4.2k unique visitors, 312 form conversions. Top page is /product-tour with 4.1k visits and 87 conversions. Editor flags the product tour as a high-performing asset.
Example 2 — Operator diagnoses a traffic drop
Operator scopes to the 14-day window covering a reported traffic drop. Referrer view shows organic traffic down 31%; direct traffic is flat. Top referrer changed from a specific blog partner to none (partner delinked the referring post). Operator escalates to content team to restore the link arrangement.
Example 3 — Stakeholder asks for site-specific analytics
Stakeholder needs to confirm the last-quarter conversion tally for the active site. Operator opens Analytics, scopes to the quarter, reads 892 conversions at a 2.8% conversion rate, exports. Stakeholder compares against account-tier rollup in SG-Dashboard Analytics and confirms the numbers align.
Documentation guidance
Use this page as the structural definition for per-site Analytics surfacing.
Reading order
Open this page when scoping per-site analytics. Pair with SG-Dashboard Analytics for account-tier rollup.
Related reading
Vocabulary cross-reference
- Per-site scope — this module shows one site only. Data from other sites under the same account is not included.
- Account-tier rollup — SG-Dashboard Analytics aggregates traffic, conversions, and signals across every site under the account.
- Ingest — the data pipeline from connected integrations (GA4, GSC) that feeds the module.
- Conversion — a tracked goal completion: form submission, store transaction, or custom-event trigger.
- Top page — a page ranked by visit volume or conversion count within the selected time window.
- Referrer — the source URL or channel that brought a visitor to the site.
Scope notes
Per-site Analytics covers the active site only. Comparative reporting across multiple sites lives in SG-Dashboard Analytics. Custom event taxonomy (naming conventions, event parameters) is defined at the integration level and is out of scope for this Reference. Per-integration setup lives in the Integrations Reference area.
Operators using this module for a compliance audit should note that raw log data and user-identity signals are not surfaced here — the module shows aggregated traffic and conversion data only.
Maintenance discipline
When per-site Analytics changes across releases — new metric, new time window option, new integration source — update this Reference. Note whether the change affects only per-site scope or also the account-tier rollup (if both, update both References).
Related reading
| Topic |
|---|
| SG-Admin |
| Analytics |
| Google Analytics 4 |