Maryland Analytics Maryland Analytics The Maryland Analytics Program (MAP) enables state agencies to make data-driven decisions that improve digital services. Managed by the Maryland Digital Service (MDDS), the public dashboard at analytics.maryland.gov highlights aggregate traffic to state websites, helping agencies better understand demand for public digital services.
The dashboard uses data collected from a wide range of public-facing informational and transactional websites. It is updated regularly to reflect near real-time activity while maintaining privacy and performance.
To ensure clarity and relevance, this dashboard only includes:
This filtering removes low-traffic or misconfigured data and focuses on meaningful patterns across public digital services. As a result, this dashboard reports aggregate analytics traffic instead of individual visitor behavior.
This dashboard reports aggregate traffic for public Maryland websites. It gives agencies a broad, privacy-preserving view of demand, performance, bandwidth, and traffic patterns.
These numbers should be read as aggregate service usage, not as a list of individual people. analytics.maryland.gov reports request counts, visit counts, bandwidth, and traffic breakdowns; it does not collect or store personally identifiable user records.
| Metric | What it means | How this dashboard uses it |
|---|---|---|
| Request | One HTTP request for a page, file, image, script, API call, or other web asset. A single page load can create many requests. | Used as the main measure of total traffic. When this dashboard says “requests,” it means total request count. |
| Visit | The dashboard's closest session-like metric. A visit usually begins when someone reaches a site from a different website or from a direct link. One visit can include more than one page view. | Used as the privacy-preserving replacement for GA-style users and sessions. It is a useful trend metric, not a person count. |
| Page view | A successful HTML page response. Page views are narrower than requests because they do not count every image, script, file, or API request. | The dashboard labels broad traffic as requests instead of page views because requests capture more than HTML pages. |
| Data served | The total amount of response data served for public web traffic. | Used to show bandwidth demand by hostname, page, download, and AI crawler traffic. |
| Location | An aggregate geographic grouping for traffic, currently reported at the country level when available. It is not a street address, GPS location, or individual visitor location. | Used to understand broad demand patterns across regions while keeping the dashboard focused on aggregate public-service usage. |
| User | A person-level analytics concept often used by browser-based tools such as Google Analytics. | Not collected or stored by this dashboard. analytics.maryland.gov gives aggregate traffic data, not user profiles. |
We do not collect or store personally identifiable information (PII). All analytics are aggregated and anonymized to protect the privacy of Marylanders.
Note: Not all of Maryland’s state government websites are represented in this dashboard. Only sites that participate in the program.
Quality Assurance reflects the credibility and usability of a website. It includes checks for broken links, outdated content, page speed, and whether only secure, approved domains are used.
Accessibility ensures that everyone, including people with disabilities, can access and use digital services. The dashboard reports accessibility based on adherence to standards such as WCAG and WAI-ARIA.
SEO measures how well content is structured and presented so that it can be discovered in search engines like Google. It includes factors like mobile responsiveness, content quality, and technical structure.