Periods, Coverage & Data Quality
Distinguish dashboard UTC days from explicit local-calendar statistics.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Dashboard periods
Dashboard analytics use UTC-day rollups. The calendar day on a visitor's device can differ from that reporting day. Period labels and date ranges must be read in the context of the displayed report.
Missing is not zero
An uncovered day is unknown, not proof of zero visitors or zero consent. A freshness timestamp shows the age of available data; it does not prove uninterrupted instrumentation. Browser restrictions, excluded routes, request failures and late installation can all affect coverage.
Visits and sessions
Recorded visits/impressions are not unique visitors or automatically grouped sessions. Analytics-provider sessions and ConsentEase banner impressions have different populations and definitions; their totals need not match.
API/MCP explicit ranges
The consent-stats route uses required inclusive from/to dates and an IANA timezone (Europe/Brussels by default). It groups by local day and ISO week and returns sparse buckets rather than inserting zero days. It is not a timezone selector for the dashboard.
Investigate discrepancies
Check the live install and network first, then exclusions, reporting timezone, action mapping, chosen period and data-quality warnings. Compare equivalent records before concluding a drop is caused by visitor behaviour. Do not optimise toward a rate without understanding how it was measured.