The production widget snippet and working session path are pending. Keep the site unchanged until a released Threetone installation contract specifies its asset and access requirements.
Choose the scope
Squarespace’s code-injection guide distinguishes global header and footer injection from page-specific header injection. Global fields affect every page; a page’s settings under Advanced can restrict supported injection to that page. Choose a test page before planning a site-wide rollout. Follow the released widget’s placement instructions. Do not place visible interface HTML in a header field just because it accepts code.Prepare the change
1
Inventory existing code
Save a copy of the current injection and identify scripts already providing chat, consent, or analytics. Decide who will maintain the integration and restore the previous configuration if a test fails.
2
Review the released installation
Verify the script origin, version, loading behavior, allowed origins, and session authorization. Keep workspace API keys out of public page code. Use one installation location to avoid duplicate initialization.
3
Check the published page
Test outside the site editor after a supported installation is available. Visit the page directly, navigate to it from another page, and return using browser history. Check that the interface starts once and releases its resources when it ends.
Frequently asked questions
Is a Squarespace code-injection option proof that the widget works?
Is a Squarespace code-injection option proof that the widget works?
No. It provides a place to insert code. Asset loading, session access, browser behavior, and conversation execution must still be verified.
Should I install it globally for the first test?
Should I install it globally for the first test?
Start with the smallest supported scope and a clear rollback. Expand only after the published-page checks pass.