Reference
Metrics, report contents, and glossary
Look up metric meaning, report contents, product boundaries, and canonical SiteWall terminology.
Last reviewed September 12, 2026
Metric catalog
Metric definitions must state entity, numerator and denominator, aggregation method, selected project, time window, update cadence, and empty-state meaning. Dashboard and feature metrics prioritize navigation; compare only like-for-like scopes and do not infer complete absence from a zero value.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Available metrics | Review available metrics in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| Aggregation | Review aggregation in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| Windows | Compare the first, last, and event timestamps with the investigation or reporting window. These values describe SiteWall observations for the active project and do not establish activity outside the captured period. |
| Limitations | Review limitations in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
Apply the reference
- 1.
Open a representative source record
Use the project selector to choose the website you intend to review, then open Metrics in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Read the field with its context
Interpret the value with its entity type, project, observation window, state, and source link. Do not compare values collected under materially different conditions as if they were equivalent.
- 3.
Carry the definition into the workflow
Use the field to navigate or prioritize, then make the operational decision in the provider, resource, session, finding, policy, or evidence workflow that owns it.
Report contents
Generated reports should identify the product and framework view, organization and project, monitored domain or page scope, generation time, observation period, readiness or coverage context, findings, actions, evidence records, decisions, gaps, and limitations. Contents vary with available project data.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Report sections | Follow the indicator to its source records and preserve the project, monitored pages, observation period, generation time, reviewer, and known gaps. Keep SiteWall’s browser-side evidence separate from organizational evidence and the reviewer’s compliance conclusion. |
| Source records | Follow the indicator to its source records and preserve the project, monitored pages, observation period, generation time, reviewer, and known gaps. Keep SiteWall’s browser-side evidence separate from organizational evidence and the reviewer’s compliance conclusion. |
| Generated time | Compare the first, last, and event timestamps with the investigation or reporting window. These values describe SiteWall observations for the active project and do not establish activity outside the captured period. |
| Scope | Keep the selected project, monitored pages, traffic paths, and observation period attached to the result. |
Apply the reference
- 1.
Open a representative source record
Use the project selector to choose the website you intend to review, then open Legal & Compliance in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Read the field with its context
Interpret the value with its entity type, project, observation window, state, and source link. Do not compare values collected under materially different conditions as if they were equivalent.
- 3.
Carry the definition into the workflow
Use the field to navigate or prioritize, then make the operational decision in the provider, resource, session, finding, policy, or evidence workflow that owns it.
Product boundaries
SiteWall records supported activity that occurs in monitored browser journeys. The quality of any conclusion depends on where SiteWall was installed, which traffic was captured, which pages and states were exercised, and the time period being reviewed.
How to interpret SiteWall records
Use the following table to understand how each area supports the task.
| SiteWall can help show | The record depends on | Do not conclude |
|---|---|---|
| Providers and resources observed in the browser | SiteWall loading and the relevant page or feature receiving traffic | An unobserved provider is absent from every possible journey |
| Browser capabilities and network destinations | The behavior occurring during captured runtime contexts | An untested state can never produce different behavior |
| Sessions and loading relationships | The page, user state, consent state, and conditional features exercised | One captured path represents every visitor or environment |
| Issues, anomalies, and metrics | Project configuration, available observations, processing, and selected time context | A signal proves malicious intent or business impact |
| Requirement- or control-aligned evidence | The source record, project, scope, time, and transformation context | SiteWall alone certifies compliance or provides a legal conclusion |
Scope a result before sharing it
- 1.
Name the project and website
State the organization, SiteWall project, domain, and environment represented by the record.
- 2.
Name the tested coverage
List the pages, journeys, consent choices, user states, regions, devices, and conditional features included in the review.
- 3.
Name the time period
Include the observation window and, when relevant, the specific session or activity timestamp.
- 4.
Link the source record
Preserve the provider, resource, session, issue, anomaly, policy, or evidence record used to support the statement.
- 5.
State known gaps
Say what was not installed, tested, observed, or independently verified so readers do not treat a limited result as universal.
Use scope-aware language
Use the following table to understand how each area supports the task.
| Avoid | Prefer |
|---|---|
| No unknown scripts exist | No unknown scripts were observed in the tested journeys during this period. |
| This provider is malicious | This provider produced a finding that requires investigation. |
| The website is compliant | The attached records support review of the specified requirement within the stated scope. |
| This resource only uses these permissions | These permissions were observed in the available traffic. |
| The policy cannot affect the website | The policy was validated against the listed journeys; remaining gaps are documented. |
Glossary
Use this glossary when a label in SiteWall or the documentation is unfamiliar. Definitions describe how the term is used in SiteWall; they do not replace your organization’s legal, compliance, or incident-response definitions.
Website and data context
Use the following table to understand how each area supports the task.
| Term | Meaning in SiteWall |
|---|---|
| Organization | The account or business context that contains users and projects. |
| Project | The boundary connecting a monitored website with its observations, configuration, policies, findings, and evidence. |
| Provider | A service or organization associated with one or more observed client-side resources. |
| Resource | An individual client-side file or asset observed in a monitored browser context. |
| Session | A captured browser visit or journey that groups relevant runtime activity. |
| Observation window | The time range used when interpreting activity, counts, changes, or evidence. |
Behavior and relationships
Use the following table to understand how each area supports the task.
| Term | Meaning in SiteWall |
|---|---|
| Browser capability | A supported browser API or category of access associated with an observed resource. |
| Network destination | A host, domain, or endpoint involved in observed browser communication. |
| Load flow | The connected path between the website, providers, resources, destinations, and browser capabilities. |
| Direct loading | The website or first-party context introduced an entity without another observed third party in between. |
| Indirect loading | Another observed provider or resource introduced the entity. |
| Observed use | Behavior captured in available traffic; it is not a guarantee of every future or untested behavior. |
| Exposure Map | The interactive graph used to explore observed loading and behavior relationships. |
Findings and monitoring
Use the following table to understand how each area supports the task.
| Term | Meaning in SiteWall |
|---|---|
| Issue | A detected condition presented for review and lifecycle handling. |
| Anomaly | A detected change or deviation from established observed behavior. |
| Severity | The product’s indication of how urgently a finding may deserve review; it is not a final statement of business impact. |
| Status | The current lifecycle or policy state shown for a record. Interpret it with the record type and project context. |
Policies and evidence
Use the following table to understand how each area supports the task.
| Term | Meaning in SiteWall |
|---|---|
| Policy | An operator decision that allows, restricts, inherits, or blocks supported behavior. |
| Global policy | The broad project default used unless a more specific override applies. |
| Provider policy | A policy applied to the supported scope associated with one provider. |
| Resource policy | A narrow policy applied to an individual observed resource. |
| Inheritance | Use of a broader policy because no more specific override is configured. |
| Derived permissions | A proposed permission set based on supported capabilities observed for a resource or scope. |
| Evidence | A scoped technical record that may support a requirement, control, investigation, or review. |
| Provenance | The source, project, entity, time, and transformation context explaining where evidence came from. |
| Readiness | A product state used to organize review progress; it is not a certification. |
| Scope | The boundaries of a statement or record, including project, domain, journeys, entities, and time. |