Pageviews still matter, but they are a poor stand-in for reader attention, loyalty, and commercial value. This guide gives publishers a practical way to compare content engagement metrics, choose the right set for their reporting model, and build a measurement stack that stays useful as formats, ad strategies, and privacy expectations change. Instead of treating every article as a traffic unit, you will see how to evaluate engagement through depth, quality, return behavior, and conversion signals using GA4’s event-based model and a publisher-focused reporting lens.
Overview
If you manage an editorial site, the easiest number to report is pageviews. It is also one of the easiest numbers to misread. A page can attract clicks because of strong search rankings, a timely headline, or accidental refreshes, while still failing to hold attention or move readers toward any meaningful outcome.
That is why content teams increasingly need pageview alternatives and better content performance KPIs. In GA4, this shift is easier to support than it was in older analytics models because GA4 uses an event-based structure rather than the session-heavy logic many teams were used to in Universal Analytics. As the source material notes, GA4 replaced UA and introduced a more flexible approach to tracking user behavior. For publishers, that matters because engagement is rarely one action. It is a sequence: landing, reading, scrolling, clicking related content, returning later, subscribing, or generating monetizable ad sessions.
A durable publisher analytics metrics framework usually includes five layers:
- Reach: how many people arrived
- Attention: whether they actually consumed content
- Depth: how far they moved into the site or article
- Loyalty: whether they came back
- Value: whether engagement supported subscriptions, registrations, leads, or ad revenue
The mistake is not tracking pageviews. The mistake is stopping there.
For most publishers, a healthy reporting baseline includes pageviews plus users, landing page sessions, engaged sessions, average engagement time, scroll depth, views per user, return rate, article recirculation, and at least one conversion signal. If you already use GA4, this is consistent with the broader move toward tracking user behavior through events and engagement rather than relying only on older session-era habits.
If you need a broader business-type view of GA4 reporting, see GA4 Metrics That Matter by Business Type: SaaS, Ecommerce, Lead Gen, and Publishers.
How to compare options
The best way to compare engagement metrics is not by popularity, but by what decision each metric helps you make. A useful metric should do at least one of three things: identify content quality, reveal audience behavior, or support monetization and growth decisions.
Use these criteria when evaluating any metric in your dashboard.
1. Does the metric reflect actual attention?
Many publisher dashboards over-reward traffic spikes and under-measure reading behavior. Metrics like pageviews and entrances tell you who arrived, but not whether the article did its job. By contrast, engaged sessions, average engagement time, and scroll milestones are more closely tied to attention.
In GA4, engaged sessions are especially useful because they help separate low-quality visits from sessions that showed some degree of activity or time investment. They are not a perfect proxy for reading, but they are a stronger starting point than raw visit counts.
2. Can the metric be compared across formats?
A text article, a photo story, a live blog, and a video page do not behave the same way. Good metrics should survive format changes. For example:
- Pageviews compare distribution, not quality
- Engagement time compares attention better across formats
- Scroll depth works well for long text, less well for short updates
- Recirculation rate works across most editorial formats
When a metric only works for one page template, label it clearly and avoid using it as a universal KPI.
3. Is the metric actionable for editors?
Some metrics are accurate but not useful in day-to-day publishing. Editors can respond to evidence that readers abandon articles early, fail to click related stories, or return mostly through direct and newsletter traffic. They cannot do much with an abstract aggregate if it is disconnected from content decisions.
A strong editorial metric usually maps to a specific action, such as:
- improve headline-to-body alignment
- rewrite intros that lose readers too quickly
- change related links placement
- increase internal linking from high-traffic evergreen pages
- build follow-up coverage around topics with strong recirculation and return visits
4. Is the metric resilient in a privacy-aware environment?
This matters more now than it did a few years ago. Consent choices, browser restrictions, and measurement gaps can affect user-based tracking. Metrics built from aggregated event behavior are often more stable than overly granular user-level assumptions. A privacy-aware publisher should prefer measurement that remains useful even when full identity resolution is unavailable.
For guidance on balancing insight and user trust, see Privacy-Conscious Tracking Strategies: Balancing Insights and User Trust and Consent Mode v2 Checklist: What to Verify in Your Analytics and Ads Setup.
5. Does the metric connect to business outcomes?
The final test is commercial relevance. If your monetization model depends on ad impressions, engaged pageviews and session depth may matter more than simple traffic totals. If your model depends on subscriptions, registration starts, or newsletter signups, then conversion-assisted content performance becomes essential.
In other words, the right metric set depends on what success looks like for your publication.
Feature-by-feature breakdown
Here is a practical comparison of the most useful content engagement metrics for publishers, including where each metric helps and where it can mislead.
Pageviews
Best for: measuring reach, content distribution, and ad inventory volume.
Limitations: pageviews say almost nothing about satisfaction or depth on their own. A high-pageview article may have weak engagement, poor recirculation, and little contribution to subscriptions or audience loyalty.
Use it when: you need a top-of-funnel traffic measure. Pair it with engagement and value metrics before drawing editorial conclusions.
Users and new users
Best for: understanding audience scale and acquisition mix.
Limitations: identity fragmentation, consent constraints, and cross-device behavior can affect precision. New users are useful directionally, but they do not guarantee quality readership.
Use it when: comparing acquisition sources, publication sections, or campaign-driven readership.
Engaged sessions
Best for: identifying visits that involved some meaningful level of interaction or attention.
Limitations: engaged sessions are still session-based abstractions. They indicate stronger quality than a raw session count, but they do not tell you exactly what the reader consumed.
Use it when: creating a publisher-friendly quality filter in GA4. This is one of the strongest default metrics for editorial reporting because it aligns with GA4’s event-based approach.
Average engagement time
Best for: estimating attention.
Limitations: time metrics can be noisy. A page left open in a tab does not always equal active reading, and a short article can still be successful with modest time spent.
Use it when: benchmarking similar content types against one another. Compare long-form to long-form, not long-form to a brief update.
Scroll depth
Best for: judging whether readers progressed through an article.
Limitations: reaching 90 percent scroll does not guarantee comprehension, and some templates trigger misleading scroll behavior on mobile devices.
Use it when: paired with engagement time and article length. A high scroll rate with very low engagement time deserves a second look.
Views per user
Best for: understanding breadth of content consumption.
Limitations: this can be inflated by navigation quirks or pagination. It also varies by traffic source and site architecture.
Use it when: evaluating content ecosystems and topic clusters rather than single-page performance.
Recirculation rate
Best for: measuring whether one article leads to another pageview within the site.
Limitations: definitions differ between teams. Some count any next page, others count only editorial clicks to another article. Standardize your definition before reporting it widely.
Use it when: improving internal linking, related content modules, and homepage or section page pathways.
Return frequency or returning users
Best for: assessing loyalty and habit.
Limitations: these metrics are more sensitive to identity and consent limitations than page-level event metrics.
Use it when: measuring audience development, newsletters, direct traffic strategy, and subscriber funnel strength.
Newsletter signups, registrations, and subscriptions
Best for: connecting content to owned audience growth and revenue.
Limitations: content influence is often assisted rather than last-click. A registration may happen after several visits, not on the first article viewed.
Use it when: your publication values audience ownership. This is where editorial analytics starts to connect cleanly with business outcomes.
Ad-relevant engagement metrics
Best for: publisher teams that depend on advertising yield.
Limitations: ad monetization often requires joining analytics data with ad server or revenue data. Page-level engagement alone is not enough.
Use it when: you can relate article type, session depth, and reader quality to revenue. This often requires better pipeline and reporting design; see Building an ETL Pipeline for Marketers: From Tracking to Trusted Data.
A practical scorecard
If you want one simple comparison, score every candidate metric across four questions:
- Does it show attention?
- Does it support editorial action?
- Does it work under privacy constraints?
- Does it connect to revenue or audience growth?
Metrics that score well across all four should be promoted to your main dashboard. Metrics that score well in only one area should remain diagnostic, not headline KPIs.
Best fit by scenario
Different publishers need different metric stacks. The right answer depends on your monetization model, content format, and reporting maturity.
Scenario 1: Ad-supported news or magazine publisher
Prioritize: pageviews, engaged sessions, average engagement time, recirculation rate, and ad revenue by content group if available.
Why: reach still matters because inventory matters, but ad-supported sites also benefit from readers consuming multiple pages per session.
Watch out for: overvaluing viral traffic that does not return or navigate further.
Scenario 2: Subscription or membership publisher
Prioritize: returning users, registration starts, newsletter signups, subscription conversions, article-assisted conversions, and engagement depth before paywall prompts.
Why: loyalty and conversion quality matter more than raw scale.
Watch out for: judging article value only by immediate conversions. Many high-value articles assist future subscriptions.
Scenario 3: SEO-led content publisher
Prioritize: landing page entrances, engaged sessions per landing page, scroll depth, recirculation to related content, and return visits from organic cohorts where available.
Why: search can deliver high traffic but uneven intent. You need to know which pages attract readers who stay and explore.
Watch out for: using rankings and clicks as proof of content quality without reading-behavior context.
Scenario 4: Newsletter-centric publisher
Prioritize: email-driven sessions, engagement time on newsletter traffic, return frequency, signup conversion rate, and article pathways after entry.
Why: owned audience channels are often stronger indicators of loyalty than platform traffic.
Watch out for: comparing newsletter visitors directly with social visitors without adjusting expectations.
Scenario 5: Small editorial team with limited analytics resources
Prioritize: one reach metric, two engagement metrics, one loyalty metric, and one value metric.
A simple starter dashboard might be:
- Pageviews
- Engaged sessions
- Average engagement time
- Returning users
- Newsletter signups or registrations
This setup is realistic, interpretable, and much stronger than a pageview-only report.
If you need help turning these into regular reporting, see How to Create Actionable Analytics Reports: Templates and Processes and Dashboard Design Best Practices: Templates and Examples for Marketing Teams.
When to revisit
Your engagement framework should not be fixed forever. Revisit it when the underlying inputs change, especially in these situations:
- When your monetization model changes: for example, when a site shifts from ad-led growth to subscriptions or memberships.
- When new content formats appear: video, live blogs, interactive graphics, or AI-assisted summaries can break old benchmarks.
- When analytics platform features change: GA4 reporting, event definitions, and integration capabilities evolve over time.
- When privacy policies or consent practices change: your measurement coverage may shift, which affects trend interpretation.
- When your editorial strategy changes: a move toward evergreen content, newsletters, or audience segmentation should lead to KPI updates.
The most practical way to maintain a durable system is to schedule a lightweight quarterly review and a deeper annual review.
Quarterly review checklist
- Confirm your key events still fire correctly in GA4 and Google Tag Manager
- Review whether scroll and engagement events match current templates
- Check if top-performing content by pageviews is also strong by engagement and value
- Update benchmarks by content type, not sitewide averages alone
- Remove metrics that create noise without changing decisions
For tracking QA, the most useful companion resource is GTM Container Audit Checklist: Tags, Triggers, Variables, and Governance.
Annual review questions
- Do our main KPIs still match how the business makes money?
- Which metrics do editors actually use?
- Which metrics are trustworthy enough for executive reporting?
- Where are privacy limitations affecting trend confidence?
- Do we need a better attribution or experimentation layer?
If you are optimizing layouts, paywalls, or article modules, connect your measurement review with testing discipline using A/B Testing Guide: Setting Up, Analyzing, and Reporting Experiments.
A practical next step
Open your current publisher dashboard and sort every metric into one of three categories: reach, engagement, or value. If one category dominates, your reporting is unbalanced. For most publishers, the fastest improvement is to keep pageviews, add engaged sessions and engagement time, define recirculation clearly, and connect at least one conversion or loyalty metric to content performance.
That shift will give your editorial team a clearer answer to the question that pageviews alone can never settle: not just whether people arrived, but whether the content was worth their time and valuable to the business.
