Add the supplied allyWay snippet through the header or footer HTML settings for your HubSpot-hosted website. Choose the intended domain and page scope, preserve the snippet’s loading settings and required initialization, and avoid duplicate copies in settings and templates. Save your settings and publish any page or template changes, then test the live website. Check blog settings and individual page overrides separately. No dedicated allyWay HubSpot app or CRM connection is required.

Website-wide code requires HubSpot’s Website settings permission, or a person with that permission who can add the snippet. Individual page changes require the corresponding Edit and Publish permissions. Custom header and footer code availability depends on your HubSpot subscription and content type; confirm that the required setting is available before starting. Content-editing access alone does not guarantee access to website-wide code. Check domain defaults, page overrides and blog templates so the snippet loads on every intended page. Websites hosted outside HubSpot need the snippet in their own website platform.

The snippet loads asynchronously. Preserve its loading settings and check performance on your published website after installation, especially if you already use several external scripts. Avoid inserting the same snippet in both website settings and the page template. Test with your current optimization, security and consent settings; do not disable protections to make the script run.

allyWay works on website pages where its snippet loads and security settings permit it. Test menus, theme modules, landing pages and dynamically loaded forms on the published website. A snippet on the surrounding page cannot adjust content inside an external iframe. Embedded forms must be reviewed according to how they render; no universal form or theme compatibility is promised. Test the complete contact, signup or booking flow, including externally hosted steps.

allyWay is developed in Europe and processes data in line with the GDPR. The widget does not set tracking cookies on your visitors’ devices. HubSpot’s consent controls and your other scripts have their own behavior: adding code to a header or footer does not automatically ensure that every script follows your consent choices. Review the actual integration with your privacy settings and test both accepted and declined consent without bypassing visitor choices.

No single tool can do that. allyWay fixes supported issues, offers visitor controls and monitors website content. Your theme, modules, pages and forms still need review. Which legal obligations apply depends on your business and services. Read about the European Accessibility Act for context.

Remove only the allyWay snippet from the website settings, page settings or templates where it was added. Check all affected domains and blog settings, save your changes and publish any changed pages or templates. Test the live website and leave unrelated scripts and modules in place. Your pages, blog content and CRM records stay unchanged.