Install the ZapClaw chat widget with Google Tag Manager

In short: in Google Tag Manager, create a Custom HTML tag that holds the widget snippet, fire it on all pages and publish the container. Use this when Tag Manager is already on your site and you would rather not touch the site's code.

Before you start

• Your site already loads your Tag Manager container. If it does not, install the container first, following Google's instructions; this guide starts after that.
• Your agent is published and its widget is active in the dashboard.
• Allowed websites. In the dashboard, add your site's address to the widget's allowed websites, exactly as visitors see it. https://www.example.com and https://example.com are two different addresses. A site that is not on the list shows no bubble.

Create the tag

<script async src="https://chat.zapclaw.app/loader.js" data-widget-id="YOUR_WIDGET_ID"></script>

Copy the exact snippet of your widget from the Agents area of the dashboard. The id above is a placeholder: yours is different.

1. In Tag Manager, open your container and choose Tags, then New.
2. Name it, for example ZapClaw chat widget. Under Tag Configuration choose Custom HTML.
3. Paste the snippet in the HTML box and leave Support document.write off.
4. Under Triggering choose All Pages. To show the chat on some pages only, use a trigger that matches just those addresses.
5. Save the tag, then choose Preview and open your site. Check that the tag fired and that the bubble appears.
6. Choose Submit, then Publish. Until you publish, visitors see nothing.

The names of Tag Manager's buttons depend on the language of your Google account and change over time; the steps follow its Custom HTML tag, which has kept the same shape.

Cookie banners and consent

The widget sets no cookie and tracks nothing, so you can choose to fire it without waiting for analytics or marketing consent. That is your decision, with whoever handles your privacy compliance.

If your setup holds back every tag until a visitor accepts, this tag is held back too, and the bubble appears only after acceptance.

If the bubble does not appear

• Container not published. A tag works for visitors only after you publish the container; Preview shows it before that.
• Tag did not fire. In Preview, open the tag in the summary. If it says it did not fire, check the trigger and the consent settings.
• Content Security Policy. A site with a strict policy must allow chat.zapclaw.app. The two lines are in the overview.

Visitors and signed-in users

On this platform the widget runs anonymous. It answers from the knowledge bases you marked public, collects a contact and hands the case to a person. What anonymous mode means.

Other install guides

• Overview, with the Content Security Policy lines and the privacy sentence.
• WordPress, for a site you host yourself.
• WordPress.com, on the plans that allow plugins.