Key Google Analytics Metrics Every Marketer Should Know
Google Analytics 4 exposes dozens of metrics, and it's easy to feel like you need to track all of them to be doing your job properly. In practice, a much smaller set of metrics does almost all of the useful work — the rest are supporting detail you pull in only when a specific question calls for it. Knowing which handful actually matter, and what each one really measures, is worth more than memorizing the entire metrics glossary.
Traffic and Audience Metrics
Users — the number of distinct people who visited your site in a given period. GA4 distinguishes Total users (everyone) from New users (people visiting for the first time), which together tell you whether growth is coming from new audience or repeat visits.
Sessions — a period of continuous activity, ending after 30 minutes of inactivity by default. One user can generate multiple sessions across different visits.
Sessions per user — a rough proxy for how "sticky" your site is; a rising trend suggests people are coming back on their own.
Engagement Metrics
Engaged sessions — sessions that lasted 10+ seconds, included a conversion, or had 2+ pageviews. This replaced the old "bounce" concept with something more forgiving and, generally, more accurate.
Engagement rate — engaged sessions divided by total sessions. GA4's bounce rate is simply the inverse of this number.
Average engagement time — how long, on average, your site was actually in the foreground of a user's browser or app — a meaningfully better signal than the old "time on page," which kept counting even if a tab was left open and ignored.
Events per session — a proxy for interaction depth; useful for comparing engagement across content types.
Acquisition Metrics
Session default channel group — GA4's automatic classification of where traffic came from (Organic Search, Paid Search, Direct, Referral, Organic Social, Email, and more).
First user source/medium — the specific source and medium that brought a user to your site for the very first time, useful for understanding what actually drives new audience versus what merely shows up alongside existing intent.
Conversion and Revenue Metrics
Conversions — the count of events you've explicitly flagged as representing business value (a purchase, a signed-up lead, a completed demo request).
Conversion rate — conversions divided by sessions (or users, depending on the report), showing what share of traffic actually completes a meaningful action.
Total revenue — the sum of purchase and refund event values, giving you a direct dollar figure tied to e-commerce tracking.
Average purchase revenue — total revenue divided by number of purchasers, a useful complement to raw revenue for understanding customer value, not just volume.
Metrics That Are Easy to Misread
- Pageviews alone say nothing about quality — a page can get significant traffic while converting nobody. Always pair it with engagement or conversion data before judging performance.
- Bounce rate / engagement rate shouldn't be compared blindly across channels — paid traffic, organic search, and direct navigation naturally carry different baseline engagement levels due to differing intent.
- Users vs. Sessions — a spike in sessions without a corresponding spike in users usually means existing visitors are returning more often, not that you're reaching a bigger audience.
Pulling These Metrics via the API
For a recurring marketing dashboard, it's often worth pulling this core metric set programmatically rather than screenshotting the UI each week:
npm install @google-analytics/data
const { BetaAnalyticsDataClient } = require("@google-analytics/data");
const analyticsDataClient = new BetaAnalyticsDataClient();
async function getCoreMetrics(propertyId) {
const [response] = await analyticsDataClient.runReport({
property: `properties/${propertyId}`,
dateRanges: [{ startDate: "28daysAgo", endDate: "yesterday" }],
dimensions: [{ name: "sessionDefaultChannelGroup" }],
metrics: [
{ name: "totalUsers" },
{ name: "sessions" },
{ name: "engagementRate" },
{ name: "conversions" },
{ name: "totalRevenue" },
],
});
response.rows.forEach((row) => {
console.log(row.dimensionValues[0].value, row.metricValues.map((m) => m.value));
});
}
getCoreMetrics("123456789");
This single query gives you the core marketing metric set broken down by channel, which is usually the first cut worth automating into a recurring report.
Building a Starter Dashboard Around These Metrics
If you're setting up reporting for a new site or client, a sensible starting metric set covers:
- Users and Sessions (trend over time, to spot growth or decline)
- Engagement rate (to judge traffic quality, not just volume)
- Conversions and conversion rate (the metrics tied closest to business value)
- Channel breakdown (to know where to invest more or less)
- Total revenue, if applicable (the ultimate outcome metric for e-commerce)
Everything else — landing page performance, specific campaign UTMs, funnel drop-off — is worth pulling in only once you have a specific question about one of these five.
Metrics Worth Knowing but Checking Less Often
A second tier of metrics is worth understanding even if you don't check them weekly:
- Views per session — how many pages or screens a typical session covers, a rough proxy for content depth and site navigation quality.
- User engagement duration — the underlying raw metric behind average engagement time, useful when you need total foreground time rather than a per-session average.
- Event count per user — useful for spotting unusually high-activity users, which can indicate either genuinely engaged customers or, in some cases, bot traffic worth investigating.
- Session conversion rate vs. user conversion rate — these can diverge meaningfully for businesses with long consideration cycles, where a single user converts only after several separate sessions.
Putting Metrics in Context With Benchmarks
Raw metric values mean very little without context. A 2% conversion rate might be excellent for a considered B2B purchase and mediocre for an impulse-buy e-commerce product. Rather than chasing generic industry benchmarks, the most useful comparison is almost always your own historical trend — is this month's number better or worse than the same period last year, or the trailing 90-day average — since that accounts for your specific audience, price point, and business model far better than a generic external number ever could.
FAQ about Key Google Analytics Metrics
What's the single most important GA4 metric for a marketer?
There isn't one universal answer, but conversions (and conversion rate) are the closest thing to a universal priority, since they tie directly to business value rather than raw traffic.
Why do my GA4 numbers not match my old Universal Analytics numbers?
GA4 uses a different session and engagement model, so metrics like bounce rate and sessions are calculated differently and won't match one-to-one, even for identical underlying traffic.
Is a high bounce rate always bad?
Not necessarily — a blog post that fully answers a reader's question in one page view can have a low engagement rate (high bounce) while still being a successful piece of content.
What's the difference between Users and Active users?
In GA4, "Users" typically refers to total users overall, while "Active users" specifically means users who had an engaged session — the platform's default user-counting metric in most reports.
Should I track vanity metrics like pageviews at all?
They're fine as a supporting metric for trend-spotting, but they shouldn't be the primary metric you report success against — pair them with engagement or conversion data.
How often should these core metrics be reviewed?
Weekly for fast-moving metrics like channel performance and conversions; monthly or quarterly for broader trend metrics like total users and engagement rate.
Conclusion
You don't need to master every metric Google Analytics exposes — you need a small, well-understood set that actually maps to business outcomes. Anchor your reporting around users, engagement, conversions, and revenue, and pull in the rest only when a specific question calls for it, and your analytics will stay a decision-making tool rather than a wall of numbers on your website dashboard.
