You find your snippet, your Website ID and the WordPress plugin in the app under Settings → Install. These steps show where each one goes on the most common website platforms. If you write your own code, the guide “Install the chat widget” covers the JavaScript side.
WordPress
With the IsTyping plugin (recommended)
The plugin adds the snippet for you, lets you hide the chat on chosen pages, and can tell your team which logged-in user is chatting.
- In IsTyping, open Settings → Install, choose WordPress and click Download plugin. You get a file called
istyping.zip. Do not unzip it. - In your WordPress admin, go to Plugins → Add New Plugin (called Add New before WordPress 6.4) and click Upload Plugin.
- Choose
istyping.zip, click Install Now, then Activate. - Go to Settings → IsTyping. Paste the Website ID and the App address shown on the Install page in IsTyping (each has a copy button), then click Save Changes.
- Optional: to show logged-in users as verified, choose Name and email, verified, paste the identity secret from the Install page and save. If you only want the chat, skip this.
Open your site in a private window: the chat button appears in the corner.
The plugin’s settings page also lets you show the chat to everyone, only to logged-in users or only to visitors who are
not logged in, and hide it on pages by ID or by address (for example /checkout). With WooCommerce you can also send
the customer’s order count and total spent. If your site uses a caching plugin, read “Does it work with page caching?”
in the plugin’s readme: when you identify logged-in users, their pages must not be served from a shared cache (that is
the default for caching plugins).
Without the plugin
If you would rather not install our plugin, use a plugin that adds code to every page. The free WPCode plugin is a common choice:
- Install and activate WPCode from Plugins → Add New Plugin.
- Go to Code Snippets → Header & Footer.
- Paste the snippet into the Footer box and click Save Changes.
If your theme is a classic theme and you work with theme files, you can instead paste the snippet into your theme’s
footer.php, just before <?php wp_footer(); ?>. Do this in a child theme; otherwise the next theme update removes it.
Shopify
- In your Shopify admin, go to Online Store → Themes.
- Next to your current theme, click the … button and choose Edit code.
- Under Layout, open
theme.liquid. - Find the closing
</body>tag near the end of the file, paste the snippet just above it and click Save.
The chat then appears on your store’s pages, but not on Shopify’s checkout pages (theme.liquid does not apply there).
When you switch to another theme, or update your theme to a new version, add the snippet again in that theme.
Wix
You need a published site with a connected domain (which on Wix means a paid plan).
- In your site’s dashboard, open Settings.
- Under Development & integrations, click Custom Code.
- Click + Add Custom Code at the top right and paste the snippet. Give it a name, for example “IsTyping chat”.
- Under Add Code to Pages, choose All pages and, when asked, load it on each new page.
- Under Place Code in, choose Body - end.
- Click Apply.
The chat appears on your published site, not in the Wix editor. If you later connect a different domain, Wix removes custom code, so add it again.
Squarespace
Adding code needs a Core, Plus or Advanced plan (or an older Business or Commerce plan).
- Open the Code Injection panel. Squarespace has moved it between menus over time; the quickest way is to search for “Code Injection” in your site’s settings or in the Website panel.
- Paste the snippet into the Footer field.
- Click Save.
Check the result on your live site in a private window: Squarespace does not run custom code on checkout pages, and it can hold back scripts in the editor preview.
Webflow
Adding custom code needs a paid site plan or a paid workspace plan.
- Open your project’s Site settings and go to the Custom code tab.
- Paste the snippet into Footer code.
- Click Save changes, then publish your site.
Saving alone does not change your live site: the chat appears once you publish.
Google Tag Manager
If your site already uses Google Tag Manager, you can add the chat there instead of editing the site:
- In your GTM container, go to Tags and click New. Name the tag, for example “IsTyping chat”.
- Click Tag Configuration and choose Custom HTML.
- Paste the snippet, including the
<script>and</script>lines. Leave Support document.write unticked. - Click Triggering and choose Initialization - All pages (the All Pages trigger also works).
- Click Save.
- Click Submit, choose Publish and Create Version, then Publish.
If you use a cookie consent tool with Tag Manager, check which consent category the tag needs, or it may not fire for visitors who have not chosen yet.
Any other site builder
Almost every builder and shop system has a setting for code that runs on every page. Look in your site’s settings for a name like Custom code, Code injection, Tracking code, Footer code, Scripts or HTML head/body.
- Find the setting that adds code to all pages, ideally at the end of the body (footer). The head is fine if it is the only option.
- Paste the snippet unchanged and save.
- Publish your site if your builder has a separate publish step.
- Open the live site in a private window and check that the chat button appears.
Do not paste the snippet into an ordinary text or rich-text block on a page: many editors remove <script> tags from
those, and the chat would appear on that one page only.
Troubleshooting
The chat button does not appear. Open the page, then your browser’s developer tools (F12 on most computers), and
look at the Console tab. Messages from the widget start with [IsTyping]. Then check these, most common first:
- Wrong or incomplete snippet. Copy it again from Settings → Install and paste it unchanged. A Website ID from another website or with a missing character makes the console say “could not start the chat session (404)”; a wrong app address makes the loader fail to load. In the WordPress plugin, compare the Website ID and App address with the Install page.
- Not published or not on this page. Many builders only run custom code on the published site, not in the editor or preview. Check that the code was added for all pages, and that the page is not excluded (in the WordPress plugin: “Show it to” and “Hide on”).
- A cached page. Caching plugins, your host and CDNs can keep serving the page as it was before you added the snippet. Clear the cache (and the CDN’s), then reload. The widget’s own loader is cached for a few minutes.
- Blocked by a cookie consent tool or an ad blocker. Consent tools can hold back scripts until the visitor agrees; check which category the chat is in. Ad blockers and privacy extensions sometimes block chat widgets: try a private window with extensions turned off.
- Blocked by your Content-Security-Policy. The console then shows “Refused to load the script” or “Refused to connect” naming the app address. Add the sources from the table above.
- Mixed content. If your site is on
https://and the app address in the snippet starts withhttp://, the browser blocks it. Use the snippet from the Install page, which has the right address. - The website is not available to visitors. While the account owner has not confirmed their email address, or while the account is suspended, the widget stays hidden without any console message. Sign in to IsTyping to see what it needs.
Logged-in customers show as “Unverified”. The identity secret on your server (or in the WordPress plugin) differs from the one on the Install page, for example after it was rotated or with a stray space; or the signature was computed over the email before lower-casing and trimming it.
The next person on a shared computer sees the previous person’s chat. Your site must push
["do", "session:reset"] on logout (the WordPress plugin does this for you), and pages of logged-in users must not be
served from a shared cache.