What We Offer
The dashboard shows page views by path, referrers by source, screen-resolution classes, and a daily visit trend — all for the date range you select.
Page views by path
The core metric on the board is page views, grouped by the URL path reported by the tracking script. Each time a tracked page loads and the script fires, one page-view event is recorded for that path on that date. At the end of any date range you select, the board shows a sorted list of paths and the total page-view count for each.
The path list is derived from what your pages actually report. If your site has consistent, clean URLs, the list reads like a table of contents for your content. If you have query strings or user-specific path segments, those may create many rows that differ only slightly. The help article on the tracking script covers how to normalize paths before they are sent if you want to group similar URLs together.
Page views by path tell you which content is working. A path near the top of the list has been loaded many more times than a path near the bottom. Over successive weeks, movement in that ranking reveals whether content is gaining or losing reach. That directional signal is usually the first thing site owners check.
Referrers
The referrer section of the board shows where traffic came from. When a browser navigates to your site from another page, it sends the URL of that originating page in the HTTP Referer header. The script reads that header, extracts the domain or source label, and records one referral hit for that source on that date.
Referrer data answers the question: which channels bring people to the site? A spike in referrals from a specific domain usually means someone linked to you, shared your content, or cited your work. A consistent stream from a search engine indicates organic search is delivering traffic. Direct traffic — visits with no referrer — covers bookmarks, typed URLs, and traffic from sources that strip the referrer header before sending.
The referrer count for a source is the number of times that source sent traffic in the selected date range. It is not a unique-visitor count from that source; it is a raw count of referral events. If someone follows the same link from the same source three times, the referrer counter for that source increments three times. That is the honest figure.
Resolution classes and device signals
The resolution class section of the board shows how visits are distributed across screen-width bands. Phone, tablet, and desktop are the primary classes, with the exact thresholds documented in the script reference. The class for each visit is determined at load time from the reported screen width, and one tally is added to the matching counter for that date.
This tells you the shape of your audience by device type. If 70% of visits arrive from phone-class screens, designing for small screens is not optional — it is the primary use case for your site. If desktop dominates, your readers may be professionals working at desks, which changes how you might format long-form content.
Resolution classes are less granular than a full device-type breakdown by operating system and model. They are also less invasive: no fingerprint is built, and the raw pixel value is not stored. The class label gives you the planning signal without the profiling risk. For most layout and design decisions, the class label is exactly the right level of detail.
Daily trends and the visits-by-day view
The board includes a daily visit trend that shows how total page views moved across the selected date range. Each bar or data point represents one day's total. Reading the trend over several weeks makes traffic patterns visible: weekday spikes, weekend drops, growth after a post goes live, decay as content ages.
The visits-by-day view is the best place to evaluate the effect of content publishing, external links, or other traffic-driving activities. If you published an article on a Wednesday and want to know whether it generated a traffic lift, the daily chart will show the before and after clearly. A sharp spike on the day of publication followed by a gradual return to baseline is the typical pattern for a piece that was picked up by an external source.
You can adjust the date range to zoom into a specific week or pull back to see several months at once. The board recalculates all figures for the selected range, so narrowing the window to a single week gives you the same page-view, referrer, and resolution data for just that period.
Troubleshooting
If the board shows fewer page views than you expected, confirm the script tag is present on all the pages you want to track. The script must load and execute on each page individually; it does not track pages where it is absent. If you are using a template system, check that the template that injects the script is applied to every page in scope.
If a referrer you expected to see is missing, the source may be sending traffic with a stripped or masked referrer. Many email clients, messaging apps, and privacy tools remove the referrer header before the browser makes the request. Those visits arrive with no referrer and are counted in the direct bucket.
If the resolution class breakdown looks dominated by a single class in a way that feels wrong, check the script placement. The script should execute after the page layout is stable so it can read an accurate screen width. If it fires before layout, the reported width may not reflect the actual device class.