Install the Allinaa chatbot with Google Tag Manager

If your website already loads Google Tag Manager, you can add the Allinaa assistant as a tag without editing the site at all. It is a good fit for teams whose marketing tags already live in one container, and it survives theme and template changes.

Requirement: the GTM container is already on your site

Tag Manager can only add the assistant to pages that already load your container. If you are not sure, ask whoever set up your analytics, or check whether your pages contain the Tag Manager container code. If the container isn't installed, use your platform's own guide instead, such as the installation guides for WordPress, Shopify or Wix.

You also need your Allinaa code. Start the 14-day free trial at bot.allinaa.com/start, follow the setup wizard, and copy the code from step 5, "Install":

<script src="https://bot.allinaa.com/widget.js" data-bot-id="your-bot-id" defer></script>

Step by step: Tags > New > Custom HTML

1. Open your container at tagmanager.google.com and go to Tags > New.
2. Click Tag Configuration, choose Custom HTML and paste your code.
3. Under Triggering, click the trigger box, click +, choose Trigger Configuration > DOM Ready, keep All DOM Ready Events and save the trigger.
4. Name the tag, for example "Allinaa chat", and click Save.
5. Click Submit (top right), keep "Publish and Create Version", add a version name and click Publish.

Google's help pages for each part: Custom HTML tags, trigger types, and submitting and publishing.

Trigger: DOM Ready, All DOM Ready Events

The trigger decides when Tag Manager adds the code. The assistant adds a chat button to your page, so it needs the page to exist first:

• Initialization fires before the page has been read. It is meant for consent and setup tags, not for something that adds an element to the page.
• DOM Ready fires once the page structure is ready, which is what Google suggests for tags that work with the page. Choose this one.
• All DOM Ready Events means every page that loads your container, so visitors see the assistant wherever they land.

If your site uses a consent banner that holds back tags until a visitor agrees, the chat button may appear only after that choice, depending on how your banner and container are set up.

Submit and Publish a version

Saving a tag changes only your workspace. Visitors get it after you click Submit and Publish. Tag Manager's Preview mode lets you test the tag on your site first, which is useful in a container with many other tags. Each published version is kept, so you can roll back if something else in that version needs undoing.

Why 'Check my site' can't see GTM tags

The Check my site button in your Allinaa cabinet reads the HTML your web server sends for your homepage and up to two pages it links to, and looks for your script tag. Tag Manager adds the tag later, inside the visitor's browser, so it is never in that HTML. A GTM installation therefore shows "not found" in the check even when it is working. That is expected and not an error.

How the installed status appears

The cabinet has a second, passive signal. When a visitor loads a page of your website with the assistant on it, Allinaa notes that it was seen on your site, and the status turns to installed. Opening one of your own pages is enough. Only your site's address (for example https://www.example.com/) is recorded, never the page path, because a path can contain personal details.

To confirm right away:

1. Open your live site in a private browser window.
2. Wait for the chat button and ask a question your knowledge covers.
3. Reload the Allinaa cabinet; the installation card should show installed.

If it still doesn't, see the troubleshooting page. Agencies running containers for clients can also receive the code by e-mail from the client's cabinet. For campaign pages that share one container, see the landing pages use case.

Frequently asked questions

Which Google Tag Manager trigger should I use for the chatbot?

DOM Ready with All DOM Ready Events. Initialization fires before the page is read, and the assistant needs the page to add its chat button.

Why does Check my site say not found when the chatbot works?

The check reads the HTML your server sends. Tag Manager adds the tag later in the browser, so the check cannot see it.

How do I know the GTM installation worked?

Open a page of your live site with the assistant. The cabinet's status turns to installed once a visitor, including you, loads such a page.

Do I need to publish the container after adding the tag?

Yes. Click Submit and then Publish; a saved but unpublished tag never reaches visitors.