Metric Definition
Knowledge base views
Knowledge base views is the total number of times self-service help articles are viewed within a given period. It is the foundational volume metric for understanding how customers engage with your help content and a leading indicator of self-service adoption and support deflection effectiveness.
7 min read
What are knowledge base views?
Knowledge base views is a count of total page views across all published self-service help articles during a defined period. Every time a customer, prospect, or internal user loads a help article, it counts as one view. The metric captures both organic discovery (through search engines or in-app links) and directed traffic (from support agents sharing article links or automated ticket deflection prompts).
This metric matters because every knowledge base view represents a potential support ticket that was not created. When a customer finds the answer they need in an article, they do not submit a ticket. When they cannot find the answer, they escalate to a human agent. The ratio between knowledge base views and ticket volume is one of the most important indicators of self-service programme health.
Knowledge base views also reveal content demand patterns. Articles with high view counts address common customer questions. Articles with zero views either cover issues nobody encounters or are invisible to search. Tracking views by article, category, and time period helps support and content teams prioritise where to invest in documentation improvements.
It is important to distinguish between raw views and unique views. Raw views include repeat visits by the same user, which can indicate that the article was not helpful enough to resolve the issue on the first read. Unique views give a better picture of how many distinct users are seeking help. Both perspectives are valuable.
Knowledge base views without context can be misleading. A spike in views might indicate a product outage driving help-seeking behaviour, not improved self-service adoption. Always correlate view trends with ticket volume and product incident data to understand what is truly driving changes.
How to measure knowledge base views
While counting page views is straightforward, the way you segment and contextualise the data determines its usefulness. Most help desk and knowledge management platforms report views natively, but the real value comes from slicing the data by article, category, traffic source, and user type.
| Measurement variant | What it captures | When to use |
|---|---|---|
| Total page views | Every article load, including repeat visits by the same user | Understanding total demand on the knowledge base and server load |
| Unique views | Distinct users who viewed at least one article in the period | Measuring the reach of self-service content across the customer base |
| Views per article | Page views broken down by individual article | Identifying high-demand content and gaps where articles are missing |
| Views by traffic source | Page views segmented by origin: search engine, in-app widget, agent-shared link, or direct | Evaluating which discovery channels drive the most self-service engagement |
Knowledge base views in a metric tree
Knowledge base views decompose into the factors that determine how many customers find and consume self-service content. The tree reveals that views are a function of both content supply (how many articles exist and how relevant they are) and content discoverability (how easily customers can find them).
The tree shows that increasing knowledge base views is not simply about writing more articles. If discoverability is poor, even excellent content will go unread. If in-app help links point to the wrong articles, customers will not find what they need. And if the active customer base is shrinking, views will decline regardless of content quality.
When views plateau or decline, the tree guides diagnosis. Is the content stale and losing search ranking? Has a product change made existing articles irrelevant? Has the in-app help widget been deprioritised in a recent redesign? Each branch points to a different intervention and a different responsible team. Tracking the ratio of views vs tickets submitted helps you understand whether content is actually deflecting support requests.
Knowledge base views benchmarks
| Company stage | Typical monthly views per 1,000 customers | Key context |
|---|---|---|
| Early-stage SaaS (under 1,000 customers) | 200 to 500 | Limited content library. Self-service behaviour not yet established. Most support still flows through direct channels. |
| Growth-stage SaaS (1,000 to 10,000 customers) | 500 to 2,000 | Growing content library. In-app help widget deployed. Organic search begins driving meaningful traffic. |
| Mature SaaS (over 10,000 customers) | 1,500 to 5,000 | Comprehensive knowledge base. Multiple discovery channels. Self-service is the primary support channel for common issues. |
| Enterprise B2B | 800 to 3,000 | Lower volume per customer but higher complexity per article. Internal users and administrators drive significant share of views. |
Benchmarks for knowledge base views are highly dependent on product complexity. A simple single-purpose tool will generate far fewer help article views than a complex platform with multiple modules. Compare against your own historical trend rather than industry averages.
How to increase knowledge base views
- 1
Embed contextual help links within the product
Place links to relevant help articles at the exact point in the product where users are most likely to need them. A help link next to a complex settings page or a tooltip linking to a setup guide drives views from users who are actively trying to complete a task.
- 2
Optimise articles for search engines
Write clear, descriptive titles that match how customers phrase their questions. Use structured headings, meta descriptions, and schema markup. Organic search is typically the largest traffic source for mature knowledge bases, often accounting for 40% to 60% of total views.
- 3
Fill content gaps using ticket data
Analyse your most common support ticket categories and check whether a corresponding knowledge base article exists. If customers are submitting tickets for issues that could be self-served, the content gap is costing you both views and unnecessary ticket volume. Improving coverage directly supports first contact resolution by giving agents articles to share during interactions.
- 4
Keep content fresh and accurate
Stale articles lose search ranking and customer trust. Establish a review cadence for high-traffic articles, especially after product releases that change functionality. An article that describes an outdated workflow is worse than no article at all because it wastes the customer's time.
- 5
Promote the knowledge base during onboarding
Introduce new customers to the knowledge base as part of the onboarding flow. Customers who learn to self-serve early become habitual knowledge base users, increasing views and reducing their lifetime support cost.
Related metrics
Customer Satisfaction Score
CSAT
Product MetricsMetric Definition
CSAT = (Satisfied Responses / Total Responses) × 100
Customer satisfaction score measures how satisfied customers are with a specific interaction, product, or experience. Unlike NPS which measures loyalty, CSAT captures satisfaction at a moment in time, making it ideal for evaluating specific touchpoints in the customer journey.
Customer Effort Score
CES
Product MetricsMetric Definition
CES = Sum of All Effort Ratings / Number of Responses
Customer effort score measures how much effort a customer had to exert to accomplish a goal with your product or service. Research shows that reducing effort is more predictive of customer loyalty than increasing satisfaction, making CES a powerful complement to NPS and CSAT.
First Contact Resolution
Support effectiveness
Operations MetricsMetric Definition
FCR Rate = (Issues Resolved on First Contact / Total Issues Handled) × 100
First contact resolution measures the percentage of customer enquiries resolved during the first interaction without requiring follow-up contacts, transfers, or escalations. It is the single most influential metric for customer satisfaction in support operations.
Net Promoter Score
NPS
Product MetricsMetric Definition
NPS = % Promoters - % Detractors
Net Promoter Score measures customer loyalty by asking how likely a customer is to recommend your product or service. It is the most widely used customer experience metric, providing a single number that captures sentiment and predicts growth through word-of-mouth.
Connect knowledge base views to support cost reduction
Build a metric tree that links self-service content views to ticket deflection, support costs, and customer satisfaction so you can measure the true ROI of your knowledge base investment.
