How to Install Website Chat With Google Tag Manager (No Code Changes)
Add a chat widget to your website in 5 minutes with Google Tag Manager: custom HTML tag, all-pages trigger, exclusions and preview testing. No developer.
In this article
You want to install website chat with Google Tag Manager because the alternative is a ticket to the agency, a two-week wait and an invoice. If GTM is already on your site (on most marketing-managed sites in the US and the UK it is), you can add the chat widget yourself in about five minutes, test it in preview mode and publish without touching the theme.
This guide walks through the tag, trigger and exception setup, then the three things that go wrong most often: consent mode silently blocking the tag, subdomains sharing a container, and the widget loading twice because someone also pasted it into the theme.
What you need before you open GTM
- Access to the GTM container with permission to publish (not just "edit").
- The widget snippet from your chat platform. In Omnifox it is one line: go to Channels, open your website chat channel and click Install. Copy the script with your
data-widget-key. - A list of pages where the chat should not appear: checkout, admin or account areas, and any page where a second overlay would fight with a booking flow.
The snippet looks like this; only the key changes:
<script src="https://omnifox.io/widget/loader.js" data-widget-key="YOUR_KEY" async></script>
It works on any site GTM runs on: HTML, WordPress, Shopify, Wix, Webflow or a React app. If you prefer to install in the theme, the WordPress install guide covers that route.
Step by step: install website chat with Google Tag Manager
- Create the tag. Go to Tags, click New, and choose the tag type Custom HTML. Name it something a colleague will recognize in a year, such as
Omnifox – website chat widget. - Paste the snippet. Put the one-line script in the HTML box exactly as copied. Leave "Support document.write" unchecked; the loader does not need it.
- Set the firing trigger. Under Triggering, choose All Pages (the built-in Page View trigger).
- Add an exception trigger. Create a Page View trigger that fires on "Some Page Views" where Page Path contains
/checkout(or/admin,/account), then add it to the tag as an Exception. GTM evaluates exceptions after firing triggers, so the tag fires everywhere except those paths. - Preview. Click Preview, enter your site URL and let Tag Assistant connect. On a normal page the tag should show under "Tags Fired"; on a checkout page under "Tags Not Fired" with the exception listed.
- Publish. Submit the workspace with a short version name ("Add website chat widget") and publish.
- Confirm the platform sees it. Back in the channel settings, the panel lists the domains where the widget is installed and when it was last seen. If your domain shows a recent timestamp, the install is done.
Google's own documentation on tags, triggers and preview mode lives at support.google.com/tagmanager; use it for any menu name that has moved since this was written.
Common pitfalls (and how to fix each)
Consent mode is blocking the tag
If your site runs a consent banner integrated with GTM, tags may wait for consent before firing. Some consent templates block every Custom HTML tag until the visitor accepts. Symptom: the widget shows for you (you accepted long ago) and not for new visitors.
Fix: open the tag, expand Advanced Settings, then Consent Settings, and review what the tag requires. Test in preview mode with a fresh incognito window before accepting anything on the banner. Whether chat needs consent in your jurisdiction (GDPR, UK GDPR, US state privacy laws) is a question for your own counsel; the technical point is to know which setting is in charge.
One container, several subdomains
A company site on www.example.com and a help center on help.example.com often share one container. Two things follow. First, the exception trigger should match on Page Path, not the full URL, or it will miss on the subdomain. Second, if the help center has its own team, create a second website chat channel with its own key and scope each tag with a Hostname condition. The platform reports each domain separately, so you can see which one is missing.
The script is also in the theme
The most common cause of two chat buttons stacked in the corner: someone installed the widget in the theme footer last year, and you just added it in GTM.
Fix: pick one home for the script. If marketing owns GTM, it is the safer place because you can see it, version it and remove it without a developer. Search the theme (footer template, custom code area, "header and footer scripts") for widget/loader.js and delete the duplicate.
Caching and CDN delays
If you publish and nothing changes, a page cache or CDN may still be serving the old page. Purge the cache or wait for its TTL, then hard-refresh.
GTM vs pasting in the theme vs a plugin
| Approach | Who can do it | Time to first install | Visible to marketing | Risk of duplicates | Page speed impact |
|---|---|---|---|---|---|
| Google Tag Manager (Custom HTML tag) | Anyone with container publish rights | About 5 minutes | Yes, versioned | Low if it is the single source | One async script, loaded after GTM |
Paste in theme before </body> |
Developer or theme editor access | Minutes, if you have access | No | Medium (someone forgets it is there) | One async script |
| Platform plugin or app | Site admin | Minutes | Partly | Low | Plugin code plus the script; varies by plugin |
GTM wins when marketing owns the widget and the developer owns the theme. Pasting in the theme wins when you have no tag manager or want the widget to load without waiting for GTM. A plugin only makes sense when it does something the script alone cannot, which for a one-line widget is rare.
After the install: things to configure next
Once the platform shows your domain as installed:
- Set business hours and the after-hours message so late-night visitors can leave a name and email.
- Turn on the AI agent with your FAQ and documents in its knowledge base, at least for the first message.
- Add a trigger or two: a proactive bubble on the pricing page after 20 seconds, or an exit-intent message on desktop.
- Use the analytics events. The widget pushes
widget_loaded,widget_opened,conversation_startedandmessage_sentto your site'sdataLayerand togtagif GA4 is present, so the same container that installed the widget can fire a GA4 conversion onconversation_startedwith no extra code.
Frequently asked questions
Do I need a developer to install website chat with Google Tag Manager?
No. You need publish rights on the GTM container and the one-line widget script from your chat platform. Everything else happens inside GTM's interface and preview mode.
Will the chat widget slow down my site if it loads through GTM?
The widget is a single async script, so it does not block the page. It waits for GTM itself to load, a small delay compared with pasting the script in the theme that most sites will not notice.
How do I keep the widget off the checkout page?
Create a Page View trigger that matches the checkout path and attach it to the chat tag as an exception. Verify in preview mode that the tag appears under "Tags Not Fired" on that page.
How do I know the install worked?
Open a page in a fresh incognito window and look for the chat button, then check the channel settings in your platform: it lists the domains where the widget was detected and when it last loaded.
Wrapping up
Installing website chat through Google Tag Manager keeps the widget in the hands of the people who use it, with versioning and preview built in. Omnifox's website chat is included in every plan and installs with one line, so the GTM part is the whole job. Grab your key, create the tag, and if you don't have an account yet, start a 7-day free trial to get one.
Ready to try it in your business?
Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.
7 days free. No credit card required.
Read more
-

What Is Click-to-Call and How to Implement It in Your Business
-

AI Website Chat That Answers From Your Knowledge Base: Documents, FAQ and Catalog
-
Viber vs WhatsApp for business: which to use in each market
-

Sales Automation With a CRM: Put Your Follow-Up on Autopilot
-
The best WhatsApp Business API providers in 2026
-

Inactivity follow-up: remind the customer and escalate to a human
-

Click to Messenger Ads: A Complete Guide to Get Started
-

Approved Templates: The Key to Bulk WhatsApp Sends Without Bans
Comments (0)
No comments yet. Be the first to share your thoughts.
Leave a comment
Your email is never published. Comments are moderated before appearing.