Segmentation, Calculated Metrics, and Virtual Report Suites
Segments, calculated metrics, and virtual report suites are the reusable building blocks of analysis. A segment is a container of visitor, visit, or hit conditions combined with AND/OR logic and sequential rules. Understand container scope: hit-level segments behave differently from visit- or visitor-level segments, and a segment applied at the wrong scope returns misleading numbers.
Calculated metrics combine existing metrics with operators (add, subtract, multiply, divide) and functions (count, sum). They can be formatted (percent, currency, time) and shared. Watch for division by zero handling and whether a metric is participating or non-participating.
Virtual report suites apply a segment and optional context-aware settings (custom calendar, time zone) on top of a base suite, without duplicating data. They are ideal for regional or brand-level views.
Traps
- Assuming a virtual report suite copies data - it is a filtered view of the base suite.
- Building a visitor-scoped segment when the question needs hit-level logic, inflating counts.
- Forgetting that calculated metrics inherit segment context and can produce unexpected zeros.
- Confusing segment stacking (multiple segments AND together) with OR logic.
Rule of thumb
Build the segment at the narrowest scope that answers the question, then widen only if needed. Test a segment against a known total before publishing.
Worked example: "Revenue per visit" = revenue ÷ visits, formatted as currency. Applied inside a virtual report suite scoped to mobile traffic, it yields mobile-only efficiency without rebuilding reports.