Event Logs
| Field | Value |
|---|---|
| Audience | public |
| Page type | reference |
| Area | sg-dashboard |
| Updated | 2026-05-14 |
How event logs work in SG-Dashboard Analytics — raw event records, filtering, retention.
Event Logs in SG-Dashboard Analytics is the raw-event surface that complements the rollup view. Where the parent Analytics page shows aggregated trends, Event Logs surfaces the underlying event records — the individual visits, conversions, or operational events the rollup is built from. This page is the Reference definition of the Event Logs sub-page.
What is this for?
Read this page when you want the structural definition of event-log surfacing — what raw events are visible, how filtering works, and what retention applies.
Good use cases
- You hit a "what events happened in the last hour?" question and need raw visibility.
- You are diagnosing a specific user session and need event-level detail.
- You are explaining to a stakeholder what raw events SGEN exposes.
- You are designing internal SOPs around incident-response visibility.
What NOT to use this for
- Aggregate analytics — open the parent Analytics page or Reports.
- Per-step procedures — open the relevant Guide.
- Per-release shipped change — open What's New or Changelog.
How this connects to other features
- Analytics — parent Reference area; rollup view.
- Reports — scheduled report deliveries.
- SG-Dashboard Overview — parent surface.
Definition
Event Logs in SG-Dashboard Analytics is the raw-event surfacing layer. Each event entry carries timestamp, event type, source site, identifying metadata, and any structured payload the event source attached.
The defining property is raw. Event Logs surfaces individual events; the parent Analytics surface aggregates them. The two views complement each other.
Purpose
The purpose of this page is to define event-log surfacing as a Reference layer. It explains what events appear, how filtering scopes the view, and how retention affects what is available historically.
Scope
This page covers Event Logs at the Reference level.
The page covers:
- The raw events the surface exposes.
- The filter and search model.
- Retention.
- The boundary against aggregated views and per-site detail.
- Per-step filtering procedures — Guides.
- Custom event taxonomy — out of scope.
- Per-release shipped change — What's New or Changelog.
Events surfaced
The Event Logs surface exposes the events relevant at the account tier.
Visit events
Page-view and session-start events from the connected analytics integration.
Conversion events
Form-submission, store-checkout, signup events as configured per site.
Operational events
Cross-site operational events (deploy completions, scheduled-process outcomes) where they have analytics relevance.
Account · Analytics · Event logs
Recent events
| Time | Site | Type | Detail |
|---|---|---|---|
| 14:32:11 | marketing | visit | page=/pricing · referrer=organic |
| 14:31:48 | shop | conversion | order #1247 · USD 89.00 |
| 14:31:22 | marketing | visit | page=/ · referrer=direct |
| 14:30:55 | blog | visit | page=/post-12 · referrer=social |
| 14:30:14 | marketing | deploy | build #482 complete · 1.2s |
Filter and search
The Event Logs surface supports filtering on the standard dimensions.
Per-site filter
Scope to one site or to a subset of the account's portfolio.
Event-type filter
Scope to visits, conversions, operational events, or a subset.
Time window
Standard windows (last hour, last day, last 7 days, custom).
Search
Free-text search against the event payload metadata for targeted retrieval.
Retention
Event-log retention is plan-aware. Higher-tier plans typically retain more history; the baseline retention covers the operational window most operators need for diagnosis.
Constraints and boundaries
Event Logs is a Reference area for raw event surfacing. It is not a substitute for the aggregated Analytics view or for full forensic logging.
Use this Reference for:
- Diagnosing recent events at the account tier.
- Confirming what raw events the surface exposes.
- Aggregate analytics — Analytics parent.
- Forensic logging — out of scope.
- Per-step procedures — Guides.
Public boundary
This page is intentionally public-safe. It does not expose event-payload internals or protected operational identifiers.
Examples
Example 1 — Operator diagnoses a recent conversion drop
The operator opens Event Logs, scopes to the last hour, filters to conversion events, sees that conversions dropped at a specific timestamp. The raw view supports the diagnosis the rollup view alerted them to.
Example 2 — Stakeholder asks "did the deploy affect traffic?"
The platform lead opens Event Logs, scopes to the deploy timestamp ± an hour, surfaces the visit events around the deploy boundary, confirms there was no immediate drop. The raw view answers the structural question.
Example 3 — Operator confirms an integration event surfaced
A connected integration fired an event; the operator opens Event Logs filtered to operational events to confirm the event surfaced in the raw log.
Documentation guidance
Use this page as the structural definition for the Event Logs surface. Procedural detail belongs in Guides; per-release behavior change belongs in What's New or Changelog.
Reading order
Open this page when raw event detail is needed. Pair with the parent Analytics page when the question shifts from raw events to aggregate trends.
Related reading
- Analytics — parent Reference area.
- Reports — scheduled reports sub-page.
- SG-Dashboard Overview — parent surface.
Vocabulary cross-reference
- Event is one record in the log.
- Event type is the category (visit / conversion / operational).
- Time window is the range the surfaced events cover.
- Filter is the scoping mechanism (per-site / per-type / per-time).
- Retention is the historical window of available events.
Maintenance discipline
When event-log behavior changes across releases (new event type, new filter dimension, new retention rule), update this Reference and log the change in Changelog. The page stays valuable because the raw-vs-aggregate split stays clear.
Related reading
| Topic |
|---|
| Analytics |
| Reports |
| SG-Dashboard |