Guide
Verify delivery and route findings
Trace notification delivery and connect findings to an owned investigation or remediation workflow.
Last reviewed September 12, 2026
Understand alert delivery
Alert delivery has three separate states: the finding met the policy condition, SiteWall attempted or completed delivery, and a person received or acknowledged the message. Use the policy log and destination history together; do not infer acknowledgement from a successful send state.
What to review
Use the following table to understand how each area supports the task.
| Area | How to use it |
|---|---|
| Evaluation window | 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. |
| Status | Read the state together with its timestamps and owner action; a workflow state does not erase the original observation. |
| Receipt | Confirm the enabled policy, finding type, count threshold, evaluation window, destination configuration, and destination owner. Verify policy evaluation, SiteWall delivery status, destination receipt, and human acknowledgment as separate events. |
| Acknowledgment distinctions | Read the workflow state with its timestamps, affected entity, and owner action. Acknowledging or closing a record changes review status; it does not remove the underlying observation or prove remediation. |
Route findings into your workflow
Route each finding to a named owner and escalation path. Keep the SiteWall project and record link in the message, define severity and response expectations in the receiving workflow, record the final disposition in the system of record, and preserve enough context to return to the original evidence.
Procedure
- 1.
Open the correct project and page
Use the project selector to choose the website you intend to review, then open Integrations in the left navigation. Confirm the organization, project, and monitored domain before interpreting a record or changing a control.
- 2.
Record the current delivery configuration
Note the enabled policy, finding type, count threshold, destination, destination owner, and latest delivery outcome. Protect recipient addresses, webhook values, and credentials in accordance with your secret-handling process.
- 3.
Ownership
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.
- 4.
Test evaluation and delivery
Generate a controlled qualifying issue or anomaly condition. Confirm the policy evaluation and SiteWall delivery outcome, then verify receipt and link access in the destination independently.
- 5.
Document destination ownership
Record the policy condition, approved destination, owner, test event, SiteWall delivery status, destination receipt, and credential-rotation or removal process.