Overview
Third-party script monitoring with SiteWall
Learn how SiteWall connects dashboards, providers, JavaScript resources, relationships, sessions, and findings in one monitoring model.
Last reviewed September 12, 2026
Third-party script monitoring with SiteWall starts from browser observations rather than a static source-code list. SiteWall groups captured activity into providers, resources, relationships, sessions, and findings, preserving the project and time context needed to investigate what ran. Coverage reflects the pages, journeys, browsers, and conditions represented in available traffic.
Discover overview
Discover is the inventory and runtime visibility layer of SiteWall. Begin with the Dashboard or Exposure Map, identify a provider, inspect its resources and load flow, then open the resource and session records that show capabilities, destinations, timing, and captured activity.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| From website to providers | Confirm the URL or domain, provider association, first and last observation, and the project in which the entity was recorded. Open the linked detail record; a display name or enrichment label is not proof of ownership or approval. |
| Resources | Confirm the URL or domain, provider association, first and last observation, and the project in which the entity was recorded. Open the linked detail record; a display name or enrichment label is not proof of ownership or approval. |
| Capabilities | Compare the observed browser access with the resource’s expected function before allowing or restricting it. |
| Destinations | Trace the relationship from the loading resource to the observed destination or capability. Confirm required service endpoints and regional behavior in representative journeys before restricting access. |
Dashboard overview
The Dashboard summarizes the selected project’s client-side posture with counts, trends, scores, and action-oriented cards. Use it to choose a direction, then open the underlying provider, resource, session, issue, or anomaly before acting on an aggregate.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Scores | Use the value to prioritize review, then inspect the contributing findings and runtime evidence. A score or severity is a triage signal, not an approval decision or a confirmed incident. |
| Charts | Review charts in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| Summary metrics | Review summary metrics in the active project, follow the linked source record, and preserve its observation, interpretation, and owner decision context. |
| Role views | Confirm the active organization and project, the person or team accountable for the change, and the role required to perform it. Verify the resulting access or ownership state from a second authorized context when practical. |