Turning the entire site into an operating picture
Site Intelligence combines audience, server, security, communications, workflow, and operational evidence so staff can understand how the whole platform is being used and where it needs attention.
From a visit count to a site-wide operating picture
A single page-view total says very little. Site Intelligence now treats every authoritative site source as part of the picture: first-party traffic, web-server and application logs, identity and access events, security scans, queue failures, notification delivery, Contact Center activity, CEMP intake, ICS-214 entries, operational audits, and approved external analytics. Each source remains visible when it is active, quiet, unavailable, or awaiting configuration.
Current conditions belong beside history
Every major number is presented with context. Administrators can compare the current seven-, thirty-, or ninety-day period with the equivalent prior period, then move from a top-line number into the pages, sources, campaigns, or technology behind it. That distinction matters. A traffic increase is only useful when staff can see what changed, where it occurred, and whether the change supports an operational or communications objective.
Use the evidence the platform legitimately receives
Public, governmental, operational, and voluntarily supplied data should be used when it improves awareness, service delivery, accountability, or reliability. Server and access logs are operational evidence, not merely files to acknowledge. NextGenEM should retain source fidelity and useful attribution instead of creating unnecessary blind spots. Special handling is reserved for genuinely sensitive information such as PII, protected health information, credentials, security secrets, and restricted case material.
Signals that lead somewhere
The dashboard is deliberately built for drill-down. Traffic changes open the trend that produced them. Source totals lead to acquisition details. Page rankings open a focused current-versus-historical view. Campaign and automated-traffic signals lead to the evidence behind the count. The purpose is not to decorate Systems Command with analytics; it is to shorten the distance between noticing a change and understanding what deserves attention.
How staff can use the evidence
Communications staff can connect outreach with visits and responses. Training staff can identify the resources people use after a campaign. Program owners can see how public and signed-in workflows perform. Technical staff can move from response-time changes into server, PHP, scheduler, queue, and application logs. Leadership can review adoption and service health from one source-aware picture.
A deliberate data-governance posture
The site-wide standard is usefulness with controlled handling—not automatic omission. Authorized staff should receive the operational detail needed to do their work. Collection, retention, and display decisions should be revisited when they were based only on an unnecessarily restrictive privacy assumption. Access controls, auditability, and safeguards remain mandatory for PII, protected health information, credentials, security secrets, and other legally or operationally restricted records.