BigCommerce

Add Inclusify to your BigCommerce store using the Script Manager.

Register the domain first

Add your domain in the Inclusify panel before you paste the script tag. Bundles are built per registered domain, and an unregistered one fails silently: the script URL still returns HTTP 200, but what it serves is a single console.log saying the domain is not registered. There is no error to find and no widget appears.

Installation Steps

1

Open Script Manager

In your BigCommerce admin, go to Storefront Script Manager.

2

Create Script

Click Create a Script.

3

Configure Script

  • • Name: Inclusify Widget
  • • Location on page: Footer
  • • Select pages where script will be added: All Pages
  • • Script category: BigCommerce requires one of Essential, Functional, Analytics or Targeting Advertising. It decides whether your consent banner blocks the script, so pick the one that matches your own consent policy.
  • • Script type: Script
4

Add Script Content

Paste the widget code in the script content area:

HTML
<script src="https://app.inclusifyapp.com/w/YOUR-DOMAIN.com.js" async></script>

Replace YOUR-DOMAIN.com with your actual domain.

5

Save

Click Save. Script Manager injects the tag server-side, so it is on the next page BigCommerce renders.

Notes

  • • Script Manager targets Stencil storefronts, which is every current BigCommerce theme. Legacy Blueprint stores have no Script Manager - add the tag to the theme’s footer.html instead.
  • • No checkout script access required
  • • Widget loads on all storefront pages

Verify the installation

  1. Open the storefront in a private window and confirm the accessibility icon appears.
  2. In Script Manager, check that the script's status is Active and its page scope is All Pages.
  3. Test a category and a product page — Script Manager scopes can be set per page type.

Widget bundles are served from a CDN and cached for a few hours. If you changed widget settings in the panel and the site still shows the old configuration, wait for the cache to expire or load the script URL directly with a cache-busting query string (`?v=2`) to confirm the new version is being served.

Troubleshooting BigCommerce installs

The script does not run on checkout.
BigCommerce restricts checkout scripts. In Script Manager set the location to Checkout explicitly; on plans without checkout script access this is not available.
Nothing appears on a Blueprint theme.
Script Manager targets Stencil storefronts. On legacy Blueprint themes, add the tag to footer.html through the theme file editor instead.
The script is saved but missing from the page source.
Check that the script type is set to Script rather than Google Analytics or another integration preset, which BigCommerce renders differently.
The widget shows on the storefront but not on a custom-domain preview.
Preview URLs run through a different host. Test against the live storefront domain.

BigCommerce questions

Do I need to edit theme files?
No. Script Manager is the supported path for Stencil themes and survives theme updates, which a footer.html edit does not.
Which themes are supported?
All Stencil themes through Script Manager. Blueprint themes are legacy and need the manual footer.html approach.
Where should the script be placed?
Footer, applied to All Pages. The tag is async and does not need to run before rendering.
Will it survive a theme change?
Yes. Script Manager entries are stored at the store level, not in the theme, so switching or updating themes leaves them in place.

Related