Metric

A metric is a number. In GA4 it's any quantitative measurement — sessions, users, event count, engagement rate, revenue. If it can be counted, averaged, or expressed as a percentage, it's a metric. Its partner is the dimension, which is the descriptive label a metric gets broken down by. Every GA4 report is metrics arranged against dimensions: the numbers, sliced by the categories that explain them.

Why it matters

Metrics are what you actually watch when you ask whether your site is doing better or worse. But a metric on its own is rarely the whole answer — it's the starting point. The skill is choosing metrics that reflect your goal rather than vanity, and reading each one in context. A number that goes up isn't automatically good news until you know which metric it is and what's driving it.

A concrete example

Suppose users rose 20% last month. "Users" is the metric; "+20%" is its value. On its own that looks like a win. But pair it with the engagement-rate metric and you might find engagement dropped over the same period. Two metrics together tell a fuller story than one in isolation: more people arrived, but a smaller share of them actually engaged.

The common misreading

The classic error is comparing metrics that aren't comparable, or treating a rate as a count. Engagement rate is a percentage; sessions is a tally — adding or averaging them together produces nonsense. Another trap is fixating on a single headline metric while ignoring the ones that qualify it. A metric answers a narrow question well; it answers a broad one badly.