Skip to main content
This document lists all events collected by the Meridian web frontend and sent to the platform analytics pipeline (POST /v1/events). For architecture and ingestion details, see Platform Analytics (Event Pipeline).

​
Admin Exclusion

When the excludeAdminUsersFromTracking config is enabled (default: true), users with the admin role are excluded from all tracking. No events are sent for admin users in this case. Configure this in Feature Admin → Beacon → Analytics.

​
Session & System Events

​
Event Pages & Actions

​
Page Views

​
Event Actions

Event Workspace tabs: overview, agenda, jobs, analytics, edit, registrations, checkin, equipment, communications

​
Referrer Attribution (all events)

Because document.referrer does not update on client-side SPA navigation, the app tracks the previous pathname on every route change and injects it into context.referrer for all analytics events (track and screen). The analytics SDK automatically uses this SPA referrer when available, falling back to document.referrer for external links and new tabs. This provides accurate referrers for any page view or event without per-page logic. The backend derives normalized sources from context.referrer for event analytics: To add new sources, extend the backend aggregation’s path-matching logic in eventAnalyticsRoutes.js. The raw context.referrer is available for custom analytics or downstream consumers.

​
Organization Pages & Actions

​
Page Views

​
Org Actions

​
Mobile App Landing Page

The Mobile Landing page (/mobile) promotes the Meridian mobile app and tracks install-related actions.

​
Page Views

​
Mobile Landing Actions

​
Event Envelope

All events conform to the event envelope schema. Key fields:
  • event — Event name (e.g. screen_view, event_registration)
  • ts — Client timestamp (ISO 8601)
  • event_id — Unique id for idempotency (UUID)
  • anonymous_id — Device-scoped persistent id
  • user_id — Set when user is logged in
  • session_id — Session identifier
  • platform — web
  • app — meridian
  • context — screen, route, referrer, locale, timezone
  • properties — Event-specific payload (no PII)

​
Adding New Events

To add new events:
  1. Use analytics.track('event_name', { ...properties }) for actions
  2. Use analytics.screen('Screen Name', { ...properties }) for page views
  3. Keep event names in snake_case
  4. Avoid PII in properties (email, name, phone, etc. are stripped)
  5. Update this document when adding new event types

Platform analytics

Philosophy, ingestion API, envelope schema, and storage in analytics_events.

Referrer sources

How URLs map to source buckets for dashboards and aggregations.

Mobile analytics

Mobile SDK usage, batching, and parity with web event names.

Atlas event analytics

Product-facing analytics built on the same event taxonomy.

Event check-in

Flows that emit registration and check-in related events.

Web client best practices

Where analytics.track / screen are wired in the Meridian web app.