Have your developer integrate the supplied allyWay snippet website-wide through your site template or a suitable custom extension. Joomla provides the Web Asset Manager for script registration and loading. Preserve the complete snippet’s required attributes and initialization; registering a script URL alone is not always enough. Avoid duplicate copies, clear the relevant caches and test the published site. This page does not require or promise a dedicated allyWay Joomla plugin.

You need permission to manage the site template or extension code, or a developer who can handle installation and deployment. Article-editing access alone may not provide those permissions. Check your Joomla version and active template styles, including any assigned to specific menu items. Editors and text filters can remove script tags from content fields, so use a controlled template or extension integration rather than disabling filtering for all users. Keep Content Security Policy protections enabled and allow only the required script and connection sources. A headless website needs allyWay in its separate frontend.

The snippet loads asynchronously. Preserve its loading settings and check your website’s performance after installation, especially if you already use several extensions or external scripts. Test with your current page cache and JavaScript optimization settings; do not disable security protections to make it load.

allyWay works on published pages where its snippet loads and security settings permit it. Test menus, article and category layouts, forms, and content loaded dynamically by extensions. Different template styles and extension layouts need separate checks; no universal compatibility is promised. External iframe content cannot be adjusted by the surrounding page’s snippet. Review embedded booking tools, shop extensions and payment screens separately and test complete visitor journeys.

Yes. allyWay is made in Europe and processes data in line with the GDPR. The widget does not set tracking cookies on your visitors' devices.

No single tool can do that. allyWay fixes supported issues, offers visitor controls and monitors website content. Your templates, extensions, articles and user journeys still need review. Read about the European Accessibility Act for context.

Have your developer remove only the allyWay integration from the site template, custom extension or separate frontend where it was added. Check every affected template style, deploy the change, clear the relevant Joomla caches and test the published site. Leave unrelated extensions and scripts in place. Your Joomla articles, categories and media stay unchanged.