AccelerUpDocs
Monitor/Web analytics

Web analytics

GA4 sessions, real-time users and breakdowns, next to the operational data.

Monitor → Web Analytics brings Google Analytics 4 into AccelerUp.

Why here

During an incident, "are users still arriving" is a question the operational dashboards cannot answer, and switching tools to find out costs minutes when they are expensive.

A traffic collapse visible next to the error rate also settles the question every incident eventually asks: is this affecting real users, or only our monitoring?

Setup

Settings → Datasources → Google Analytics. Needs a service account with read access to the GA4 property. Stored as a google_analytics integration.

What is shown

KPIsSessions, users, engagement, conversions — with period-over-period deltas
TimeseriesEach KPI over the selected range
Real-timeUsers active now
BreakdownsCountry, device, host
FiltersCountry, device, host

Alerting on GA metrics

GA metrics can carry rules like any other source. Two things to know:

  1. GA data is delayed. Real-time is real-time; everything else lags. A rule with a tight window will alert on incomplete data.
  2. Traffic is seasonal. An absolute threshold on sessions fires every night. Use a change-based condition, or compare against a baseline.
Tip

The most useful GA alert is a collapse, not a threshold — "sessions fell more than 40% against the same hour last week". A tag that stopped firing and an outage look identical in the traffic graph, and both are worth knowing about immediately.

Event watchdog

A configured event that stops arriving raises an alert. A conversion event that silently stopped firing after a deploy is invisible in every dashboard — the number just gets smaller — and this is the check that catches it.

Where this behaviour lives: backend/internal/integration/ga4_client.go, frontend/src/app/web-analytics/. If the code and this page disagree, the code is right — please fix the page.

Part of Monitor — Everything that watches something and reports what it saw.