Guide
Inspect providers
Review a provider, its resources, load flow, activity, and historical incident context in one workflow.
Last reviewed September 12, 2026
Providers overview
The Providers page lists third-party vendors and services detected for the active project. Search by name, filter by loading type, compare resource impact and last activity, and open a row for the provider profile. Direct providers were loaded by the page; indirect providers were introduced by another third-party resource.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Search | Narrow the current project’s records before interpreting totals or opening a detail view. |
| Filters | Narrow the current project’s records before interpreting totals or opening a detail view. |
| Status | Read the state together with its timestamps and owner action; a workflow state does not erase the original observation. |
| Impact | Compare the same resource across representative sessions, pages, and time windows. Treat load and execution timing as investigation context; correlate it with deployments and browser conditions before assigning cause. |
| Activity | Read active state, resource count, and last activity together, then open the related inventory or session record for detail. |
Inspect a provider profile
A provider profile brings identity, activity dates, associated resources, load relationships, and known incident context together. Use About for orientation, Inventory for the resource list, Load Flow for observed dependencies, and Past Incidents for contextual review.
Procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Providers in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Define the observation window
Record the page or journey, browser and consent state, test time, and active filters. Note the visible counts before narrowing the view so an empty filtered result is not mistaken for missing collection.
- 3.
About
Use the provider description and enrichment for orientation, then confirm identity through the observed resources, domains, and official website when available.
- 4.
Dates
Compare First seen and Last seen with the investigation period; these dates describe SiteWall’s observations for this project.
- 5.
Activity
Read active state, resource count, and last activity together, then open the related inventory or session record for detail.
- 6.
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.
- 7.
Confirm the record against known traffic
Refresh the view, remove unintended filters, and compare the provider, resource, relationship, or session with the page and journey you exercised. Follow the linked detail record before drawing a conclusion.
- 8.
Record the scoped observation
Preserve the record link, project, page or journey, filters, observation window, reviewer, and the next record to inspect. State untested conditions as coverage gaps.
Review provider inventory
Open Inventory on a provider profile to review only the resources associated with that provider. Search or filter the list, compare performance, API access, security score, and status, then open View Details for the resource that needs investigation.
Trace a provider load flow
Open Load Flow on a provider profile to trace observed relationships among the root site, the provider’s resources, network requests, and browser APIs. Select a node to focus its connected path and confirm important relationships in the corresponding resource or session record.
Review provider history
Past Incidents adds known provider incident context to the current provider record. Read severity, description, date, and source, then compare the incident period and affected service with your own observed resources. Historical context does not prove your project was affected.