Guides/add chat widget to website

Deploying Chat Widgets: Technical Implementation Guide

Step-by-step deployment guide for WhatsApp and Messenger widgets across Next.js, WordPress, and Shopify environments.

Step-by-step: add a chat widget

  1. Open a chat widget editor (example: /get-widget/whatsapp-chat).
  2. Customize colors, avatar, greeting, and button text.
  3. Click Save & Get Code.
  4. Paste the snippet into your website:
    • WordPress: Custom HTML block
    • Webflow: Embed element
    • Shopify: Custom Liquid
    • Plain HTML: paste before </body>
  5. Publish and test on mobile.

If you run into z-index conflicts, move the embed lower in the page or contact support.

Choose your channel

Step-by-step: build it in GizmoSauce and embed it

If you want a fast, reliable way to ship a add chat widget to website, this is the “no surprises” workflow.

1) Pick a widget and open the editor

Start in /widgets and choose a widget that matches your goal. For this guide, we’ll use WhatsApp Chat as the example.

Click Customize to open the editor: /get-widget/whatsapp-chat.

Editor overview wireframe

2) Configure Content, Layout, and Design

Most widgets follow the same structure:

  • Content: what the widget shows (sources, text, items)
  • Layout: how items are arranged (grid/list/cards, columns, spacing)
  • Design: colors, typography, radius, shadows

Use the preview toggles (desktop/tablet/mobile) to validate the mobile layout before you publish.

3) Save and copy the embed snippet

Click Save & Get Code to publish the widget config and copy your snippet.

Embed snippet wireframe

4) Paste into your website builder

In your website builder, look for an HTML/code block (often called Embed, Custom HTML, Code, or Custom Liquid). Paste the snippet, publish, then verify on the live URL.

Many platforms don’t execute scripts inside editor previews. If you don’t see the widget immediately, publish to staging/live and reload.

If you’re embedding multiple GizmoSauce widgets on one page, you typically only need one loader script per page. Duplicating loaders can cause flicker or redundant work.

Platform notes (WordPress, Webflow, Shopify, and HTML)

The same embed snippet works across builders—you’re mostly choosing where to paste it.

Platform embed block wireframe

WordPress

Use a Custom HTML block in the block editor (or an HTML module in Elementor). See the WordPress integration guide: /integrations/wordpress.

Webflow

Use an Embed element and publish to staging/live to verify (scripts can be limited in preview). Guide: /integrations/webflow.

Shopify

Use Custom Liquid (recommended) or add the snippet to your theme layout for site-wide widgets. Guide: /integrations/shopify.

Plain HTML / any framework

Paste the snippet into your HTML (often before </body>). If you use React/Vue/etc, avoid inserting the loader multiple times on re-renders.

Troubleshooting checklist (when it doesn’t show)

If your widget doesn’t appear, these are the fastest fixes:

  1. Hard refresh (Cmd+Shift+R / Ctrl+Shift+R) or try an incognito window.
  2. Confirm the snippet is pasted on the right page and in the right section.
  3. Check whether the builder strips script tags.
  4. Make sure you didn’t paste the loader script multiple times.
  5. If you use a cache/performance plugin, purge cache.

For a deeper checklist, see: /help/install-and-embed/embed-basics/embed-troubleshooting.

If you still can’t get it live, send us your page URL and we’ll help you debug: /support.

Performance, privacy, and safety (what “good” looks like)

A widget should help conversions without hurting UX. Here’s what to look for:

  • No layout shift (CLS): good widgets reserve space so content doesn’t jump.
  • Lazy loading: load only when visible (or when the user interacts).
  • Style isolation: avoids theme CSS breaking the widget.
  • Safe URL handling: blocks unsafe schemes like javascript: in links/media sources.

GizmoSauce applies URL sanitizing and isolates widget rendering to reduce common risks. If you add links or assets manually, stick to normal https:// URLs.

Want a deeper explanation? Start here: /help/security-and-troubleshooting/security/xss-and-safe-embeds.

FAQ

Do I need to paste code on every page?

For floating chat widgets, install once site-wide (footer or global scripts) so it shows on all pages.

Why doesn’t it show inside the builder preview?

Some builders sandbox scripts in the editor. Publish to a staging/live URL to see the widget run.

How do I avoid covering my cookie banner?

Test on mobile and adjust placement/offset. If needed, contact support for a positioning override.