Documentation
Problems on specific platforms
Get the widget showing on Wix, Squarespace, Webflow, Drupal, Magento, BigCommerce, HubSpot or a custom-built website – what each platform needs.
Updated October 28, 2026
Some website platforms have their own rules for custom code. If the widget doesn't show on Wix, Squarespace, Webflow, Drupal, Magento, BigCommerce, HubSpot or a custom-built website, check the points for your platform below. For causes on any website, see The widget doesn't show; for the installation itself, Install allyWay.
Look at your published site
The widget only appears on your published site, on the domain you added in allyWay. Check it there, in a private window:
- Not in the editor or preview: Wix runs custom code only on your published site. Webflow's Designer and preview don't show the widget either – where they run custom code, it's on a "….canvas.webflow.com" address, not your domain. Squarespace may show your site without your code while you're logged in and editing.
- Not on the platform's own address: if you added your own domain, the widget stays hidden on addresses like "….wixsite.com", "….squarespace.com", "….webflow.io" or "store-….mybigcommerce.com". That's normal.
Wix
Wix allows custom code only on a Premium plan with a connected domain.
- In Settings → Custom Code, check the allyWay entry: All pages and Body – end. Click Apply.
- If your site uses Wix's cookie banner, keep the allyWay code in the Essential category – in the Code Type tab of your custom code. Essential is the default, and it lets the code load for every visitor.
Squarespace
Code injection comes with the Core, Plus and Advanced plans and some older plans. On other plans, the field isn't available.
- Open Website → Pages → Custom code → Code Injection, check that the code is in the Footer field and click Save.
- On older Squarespace sites (version 7.0), you find Code Injection under Website Tools in the Pages panel.
- While you're logged in, Squarespace shows your site's built-in ".squarespace.com" address in the address bar. Log out, or use a private window, and visit your own domain.
Webflow
Webflow offers custom code only with a paid Site plan or Workspace plan, and it goes live only after you publish.
- Check that the code is in Site settings → Custom code → Footer code and click Save changes.
- Publish your site to your custom domain.
Drupal
The most common cause: the editor removed the code's script tag when the block was saved. Drupal's editor (CKEditor 5) can do that even in Full HTML with scripts allowed – for example when you switch from Source back to the normal view.
- Open the block, switch to Source and check that the code is still there. Save while Source is still open.
- If the code keeps disappearing, ask your developer to add it to the theme instead.
- Check that the block is shown on all pages: its visibility settings can limit it to certain pages, content types or roles.
- Clear the cache under Configuration → Performance.
Magento
- Check that the code is in Footer → Miscellaneous HTML of the store view your visitors see. Each store view can have its own footer settings.
- Flush the cache under System → Cache Management, and any full-page cache or Varnish.
- Each store domain is its own website in allyWay, with its own code – see Websites, domains and subdomains.
- Magento's own security settings may block scripts from other addresses. On checkout pages, its Content Security Policy stops scripts it doesn't allow (since Magento 2.4.7, on the payment pages). Ask your developer to allow allyWay's addresses – see Your visitors' privacy.
BigCommerce
- Open Storefront → Script Manager and check the allyWay script: location Footer, pages All pages, category Essential. With another category, visitors may have to accept cookies before it loads.
- On checkout pages, BigCommerce runs scripts only with Optimized One-Page Checkout and asks for an integrity hash (SRI) for every script there. allyWay's script changes with every allyWay update, so the widget may not appear on checkout pages.
HubSpot
- Check that the code is saved in Settings → Content → Pages → Site footer HTML for the right domain. A domain's own Site footer HTML replaces what's set under Default settings for all domains for that domain.
- Custom templates must include HubSpot's
{{ standard_footer_includes }}right before</body>– that's where HubSpot adds your site footer HTML. Without it, the code isn't added to the page. Your developer can check.
Custom-built websites
Your developer should check that the code is in the template every page uses, right above </body>, that the new version is deployed and caches are cleared, and that no Content Security Policy blocks allyWay. Static sites without a shared template need the code in every HTML file. With a site generator or framework, add it to the base layout, then build and deploy again.
The browser's developer tools show the exact reason:
Search the page source
Open the live page's source and search for "loader.js".
Check the Network tab
In the developer tools, open Network and check that
loader.js,widget.jsandconfig.jsonload.Read the reason
If
config.jsonsays"enabled": false, read its"reason".Check the Console
Look in the Console for Content Security Policy messages.
Check that it works
Open your published site on your own domain in a private window and look for the widget button. To see whether allyWay found your code, see Check that allyWay is installed. Still stuck? Get help from our team.