embent

Install guides / Google Tag Manager

Install Embent with Google Tag Manager

Already run your site through Google Tag Manager? Add Embent as a Custom HTML tag — no direct code access to your site required.

Before you start

  • A Google Tag Manager container already installed on your site, with publish access to it.
  • If your site uses a consent banner wired into GTM's consent settings, the tag can be delayed or blocked until the visitor responds — see the FAQ.

Steps

1

Copy your embed snippet

In your Embent dashboard, open your bot's Overview and copy the embed snippet. It looks like this:

<script src="https://api.embent.com/widget.js" data-bot="YOUR_BOT_ID" async></script>
2

Create a Custom HTML tag

In Tag Manager, go to Tags → New, and under Tag Configuration choose Custom HTML. Paste the snippet into the HTML field.

3

Fire it on all pages and publish

Under Triggering, choose a Page View trigger scoped to all pages (most containers already have an "All Pages" trigger you can select) so the tag fires on every page load. Save the tag, then click Submit → Publish to push it live.

Check it worked

Use Preview mode to check the tag fires, then publish and reload your live site: the chat bubble appears in the corner. Ask it a question about your own pages and it should answer with a citation.

If it doesn't work

Tried it and the widget isn't showing? These fix nearly every case.

I added the embed code but the widget doesn't appear — no chat bubble, no launcher, nothing shows up on my siteFour checks solve almost every "widget not showing" case. First, open your live site and view the page source (right-click → View Page Source) and search for "embent" — if the script is not there, the code was not saved to a published page. Second, make sure the data-bot ID in your snippet matches the one shown in your dashboard under Settings. Third, clear your site's page cache and any CDN cache — a cached page keeps serving the old version without the widget. Fourth, check the bot is not paused in the dashboard: a paused bot deliberately shows nothing to visitors.
The tag fires in GTM preview but visitors only see the widget after accepting cookiesThat is your cookie-consent tool blocking unapproved scripts until the visitor consents. The Embent widget sets no tracking or advertising cookies — it keeps one functional key in localStorage so a returning visitor keeps their conversation. Classify the Embent tag as "functional" or "necessary" in your consent tool and the widget can greet visitors right away.

Common questions

Why isn't the widget showing up even though I published the tag?If your site runs a consent banner connected to GTM's consent settings, a tag with consent requirements can be delayed or blocked until the visitor responds. Check the tag's Advanced Settings → Consent Settings, or fire it on a plain page-load trigger without a consent condition.
Do I still need to add the snippet directly to my site's code?No. Once the Custom HTML tag is published in GTM, it loads the widget on every page the GTM container itself is installed on — that is the point of using GTM instead of editing code by hand.
Will this slow down my page or affect my other tags?No. The widget script loads async and stays under 50KB gzipped — it doesn't touch your other tags or your dataLayer.
Point Embent at your site now.An AI agent that would rather say “I don’t know” than make something up. Free plan, no card — most sites are answering within two minutes.

The chat bubble in the corner is Embent itself, running on this page — ask it anything about us.