Load ASDK's AI agents with Google Tag Manager

Google Tag Manager lets a marketing team add scripts to a site without waiting for a developer. If your site already loads a Tag Manager container, you can add ASDK's AI agents the same way you added analytics: one tag, one trigger, publish. Nothing in your site's code changes, and you can pause or remove the agents from Tag Manager at any time.

What you get through Tag Manager

Tag Manager only decides when the ASDK script loads. Everything else works exactly as with any other install: ASDK builds one knowledge base from your public pages and documents, and every agent you switch on in the dashboard answers from it.

• Chat (early access, from the Free plan) answers visitors from your content, links the pages each answer came from, and offers to take contact details when it cannot help.
• Sales (early access, from the Pro plan) asks the qualifying questions you write in plain language and offers a meeting to visitors who fit.
• Agent-Ready (early access, from the Free plan) publishes what your knowledge base knows in formats AI assistants read well.
• Search is coming soon. It will answer in place of a search box, with sources.

Changing agents, colors or texts later happens in the ASDK dashboard. You do not need a new Tag Manager version for that.

When Tag Manager is the right choice

Tag Manager is a good fit when your marketing team already manages scripts there and your developers prefer it that way. It is not required: pasting the snippet into your site's template works just as well and is easier to reason about.

• Choose Tag Manager if the container already loads on every page, you want version history and a preview mode for every change, or getting a code change deployed takes weeks.
• Choose the template or theme if your site does not use Tag Manager yet, if a consent tool blocks Tag Manager for many visitors, or if your platform has a simpler custom code setting. The platform guides cover each option.

Either way, do not load ASDK both ways on the same page.

Two ways to add it

Custom HTML tag

This works in every container today. The dashboard's Install page has a Google Tag Manager tab with code like this, filled in with your own site ID:

<script>
  window.asdkConfig = { siteId: "SITE_ID" };
</script>
<script async src="https://cdn.asdk.com/v1/asdk.js"></script>

Tag managers insert scripts in a way that can drop data- attributes, so this version passes the site ID in window.asdkConfig, which the widget reads. Google's help page on custom tags describes the Custom HTML tag type (checked October 2026).

The ASDK tag template

A tag template turns the code into a form with fields, which is easier to review and harder to break. The ASDK template is coming soon to Tag Manager's Community Template Gallery. Templates there are published from a public GitHub repository with an Apache 2.0 license and a metadata file, and Tag Manager tells users when a template they use has an update, according to Google's gallery documentation (checked October 2026). If you have the template file today, you can import it under Templates → Tag Templates → New.

Set up ASDK with a Custom HTML tag

What is available and what is coming soon

ASDK as a whole is in early access: the agents work and you can use them, but they may change while we improve them.

Tag Manager details worth knowing

• How the install check works here. The snippet is not in your page's HTML when Tag Manager adds it. The dashboard's check recognizes your container and waits for the widget to report from your site, so open a page after publishing.
• Consent settings. If you use Tag Manager's consent settings, set what the ASDK tag needs under the tag's Advanced Settings → Consent Settings. The widget sets no cookies; it keeps a random visitor ID in local storage. Decide the category with whoever owns privacy on your site. See consent managers.
• Only on some pages. A trigger other than All Pages limits where the widget appears, for example only on pricing and product pages. The agents still answer from your whole knowledge base.
• Content Security Policy. If your site sends a policy, it must allow https://cdn.asdk.com for scripts and https://api.asdk.com for connections, just as it allows Tag Manager itself. See Content Security Policy.
• One copy per page. If ASDK is also pasted into your site's template, remove one of the two. A second copy is ignored, but it costs a request.

Calling the widget from other tags

Tag Manager setups often react to page events. The widget adds a global asdk function, so another tag can open the chat, for example after a visitor has spent a while on the pricing page:

<script>
  window.asdk = window.asdk || function () { (asdk.q = asdk.q || []).push(arguments); };
  asdk("open");
</script>

The first line queues calls made before the widget has loaded. Use this sparingly: a chat that opens by itself on every page gets in the way. Our guide to qualifying leads without annoying visitors covers when proactive prompts help and when they hurt.