{
  "slug": "web-analytics-events",
  "name": "Events (total and average)",
  "aliases": [
    "Total events",
    "Average events"
  ],
  "definition": "The count of analytics events in the period, and their average per row.",
  "category": "Web analytics and conversions",
  "type": "raw measure",
  "unit": "events",
  "direction": "neutral",
  "verification": "review",
  "aggregation": "The total sums the events column across rows; the average takes an unweighted mean of the same column.",
  "grain": "One number per date range, or one row per breakdown value.",
  "dimensions": [
    "country",
    "device",
    "page",
    "keyword",
    "source_medium",
    "intent",
    "category"
  ],
  "requiredFilters": [
    "date_range"
  ],
  "sources": [
    "web-analytics"
  ],
  "reports": [
    "search-to-revenue-report"
  ],
  "skills": [],
  "verbs": [
    "web_analytics_overview",
    "conversions_overview",
    "pop_significance"
  ],
  "rungs": [
    "R5"
  ],
  "levers": [],
  "questions": [
    "How many events did we record?"
  ],
  "caveats": [
    "Neither measure carries a definition of what counts as an event; that is set in your analytics property and is not visible here.",
    "The average is unweighted across rows, so it is a per-row mean rather than a per-session or per-user rate.",
    "Whole-domain only today."
  ],
  "freshness": "loads nightly, a same-day question gets yesterday's number, labelled as yesterday's.",
  "failureModes": [
    "Reading the average as events per session.",
    "Comparing event counts across properties with different event configurations."
  ],
  "notSameAs": [
    {
      "slug": "conversions-count",
      "why": "Events are every recorded interaction; conversions are the subset your configuration marks as a goal. Reading an event count as an outcome count overstates results substantially."
    }
  ],
  "related": [
    "conversions-count",
    "sessions"
  ],
  "workflows": [],
  "lastVerified": "2026-08-04"
}