Install the widget on a website

Script, token and domain form one control

The code supplied by Wavize loads the widget with a signed public token. “Public” means it may appear in the browser; it does not mean it can be reused on any website. The token is tied to the registered domain.

Install the block without modifying its identifier, then test the page actually served to visitors. An editor may display the code without publishing it, and cache may continue serving the old version.

Do not share the wrong data
The widget token can be inspected in the browser. WooCommerce, PrestaShop, Shopify, Wix, Klaviyo or Mailchimp keys are secret and must never be pasted into HTML.

Prepare the correct domain

The domain entered during onboarding must match the public address where you test.

1. HTTPS and www variant

   Check the browser’s final redirect. If the site ends at www.example.com, do not test only example.com without confirming the allowed domain covers the final variant.

2. One token per allowed domain

   Do not copy code from one environment to another production or staging domain. Generate or select the matching token under Assistant > Installation.

3. Available subscription

   Public loading also depends on plan access. A correct script may remain invisible if the subscription is no longer active.

Place code for the platform

The method depends on the CMS, but the expected result is always the same: the script appears once on every intended page.

1. HTML site or tag manager

   Paste the block before the closing body tag or in a global slot executed after required consent. Avoid loading it in both the theme and tag manager.

2. WordPress / WooCommerce

   Use the plugin downloaded during onboarding, activate it and paste the token into its settings. JavaScript optimization must not delay or combine the script until it becomes invalid.

3. PrestaShop

   Install the module from Module Manager, open its settings and enter the token. Then clear Smarty/PrestaShop cache and CDN cache if applicable.

4. Shopify and Wix

   Shopify App Store normally manages the App Embed and connection. On Wix, use global custom code only if your Wix plan allows this injection type and apply it to all pages.

Publish and inspect the browser

Test in a private window to separate cache, consent and administrator-session issues.

1. Find the delivered script

   Open page source or the Network tab and search for Wavize. If absent, the problem occurs before calling Wavize: publishing, theme, tag or cache.

2. Read console and network

   A CSP error means the security policy blocks a script or connection domain. A 401/403 points to token, domain or access; an extension block often disappears without an ad blocker.

3. Check consent and overlap

   Accept the consent category required by your policy. If the button exists but is hidden, check position, z-index and overlap with cart, navigation or cookie banner.

Minimum post-publish test

Perform this test on desktop and a real phone.

• Opening — The button appears, opens the widget and does not distort the page.
• Conversation — A visitor message receives a reply and appears in the inbox.
• Proactive welcome — The campaign appears according to delay and cap, not on every refresh.
• Secondary page — A second page confirms installation is global.