Guide
Install SiteWall
Deploy the project-specific initialization code through your normal website release process.
Last reviewed September 12, 2026
Installation connects browser activity on the verified website to the active SiteWall project. The initialization code is project-specific: always copy it from the project you are deploying, and release it through the same review and rollback process used for other website changes.
Get the initialization code
- 1.
Select the verified project
Use the project selector near the upper-left of SiteWall. Confirm that the project name and domain match the website you are about to change.
- 2.
Open Realtime Monitoring
Select Realtime Monitoring in the left navigation. The page shows the installation state and the initialization code generated for the active project.
- 3.
Copy the generated code
Use the copy control in SiteWall. Do not retype identifiers, edit the generated values, or reuse code from another project.
Deploy the code
- 1.
Choose the shared loading point
Add the code to the approved application entry point or shared page template so it runs on the pages included in the project scope. Follow the placement guidance shown with the generated code.
- 2.
Review existing browser controls
Check Content Security Policy, consent conditions, tag-manager rules, script ordering, privacy extensions, and network controls that could prevent SiteWall from loading.
- 3.
Test in a non-production stage when available
Use your normal preview or staging process to confirm that the change renders correctly and does not interfere with navigation, authentication, forms, checkout, consent, or other critical functions.
- 4.
Release through normal change control
Record the change owner and recovery action, obtain the required approval, and deploy through your established release process.
Confirm the browser loads SiteWall
- 1.
Open an in-scope page
Load the exact hostname and route included in the project. Use a clean browser session if cached state or extensions could affect the result.
- 2.
Check the browser console and network activity
Confirm that the initialization code executes and that no browser error, CSP rule, consent state, tag rule, or network control blocks it.
- 3.
Run a website smoke test
Verify the critical interactions affected by the page: navigation, sign-in, forms, consent, checkout, embedded services, and layout.
- 4.
Keep the change recoverable
If the website behaves unexpectedly, use the documented rollback path and investigate before expanding the deployment.
Installation is ready for data validation when
Use the following table to understand how each area supports the task.
| Check | Evidence |
|---|---|
| Project | The open SiteWall project matches the deployed hostname. |
| Code | The deployed values match the code generated for that project. |
| Browser | No blocking console, CSP, consent, tag, or network error is present. |
| Website | The agreed smoke-test journeys still work as expected. |
| Recovery | The owner knows how to reverse or disable the change. |