Content Viewing Tracker
Content Viewing Tracker helps WinnerWare measure which content users actually read and turns that activity into reusable top-viewed content experiences.
Overview
This module is useful when teams want to understand which content is getting attention and expose that activity back to users or administrators as a ranked list.
It combines two practical capabilities:
- track views for selected content types
- display the most-viewed items through widgets or dashboard cards
Key Features
- Adds a Content Viewing settings area.
- Lets administrators choose which content types should be tracked.
- Records view totals for supported content items.
- Adds a Top Viewed Content Items widget.
- Adds a dashboard version of the same top-viewed widget when dashboard support is enabled.
How It Works
After administrators choose which content types should be tracked, the module records views when a published content item is displayed in its main detail view.
Those view totals can then be reused in a widget that lists the most-viewed items. Editors can control how many items appear and how long the ranked results should be cached.
Configuration
| Admin display name | Feature ID | Notes |
|---|---|---|
| Content Viewing Tracker | CloudSolutions.Content.ViewingTracker | Enables view tracking, tracking settings, and top-viewed widgets. |
Settings location
- Settings -> Content Viewing
Permission
| Permission | Purpose |
|---|---|
| Manage Content Viewing Settings | Lets administrators manage which content types are tracked. |
Content viewing settings
| Setting | Purpose |
|---|---|
| Content Types | Selects the content types whose published detail views should be tracked. |
Top-viewed widget fields
| Field | Purpose |
|---|---|
| Total Visible Items | Sets how many top-viewed items appear in the widget. |
| Total Minutes to Cache | Sets how long the widget result should be cached before recalculating. |
Usage
Use this module when teams want to highlight popular content, monitor engagement trends, or add a quick "top viewed" experience to a landing page, knowledge area, or admin dashboard.
In the current solution, the dashboard widget pattern is already used in knowledge-focused setup content.
Example setup
One clear setup pattern is:
- open Settings -> Content Viewing
- choose the content types that should count views
- create a Top Viewed Content Items widget or dashboard widget
- set the visible item count and cache duration for that widget
- place the widget where teams want users or administrators to see popular content
Developer Notes
- Tracking is limited to published detail views of the selected content types.
- The module stores both total view counts and per-view records.
- Per-view records also capture optional source, query, and utility markers when they are present in the request.
- The content admin list can be filtered with a
viewed-atterm for date-based view analysis.