Add the Allinaa chatbot to a Magento or Adobe Commerce store

Adobe Commerce and Magento Open Source have a built-in place for site-wide scripts in the design configuration of a store view, so the Allinaa assistant needs no module to get started. A module is the developer's route when the store's code is managed in a repository. Both are below, with the cache flush that every Magento change needs.

Design configuration or module

The design configuration of each store view has a field for scripts and style sheets in the HTML head. Whatever you paste there is added to the head of every storefront page of that view. For the exact place of the field in your version, check in the Adobe Commerce user guide. A module adds the script through layout XML instead, which is what developers prefer when configuration is kept in code. The head is fine for the assistant: the script is deferred and waits for the page body before adding its button.

Get your code

The line comes from your Allinaa cabinet. After you sign up at bot.allinaa.com/start and approve the knowledge the wizard drafts from your public pages, step 5 of the wizard shows it, and the Overview keeps it under "Website installation":

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

Route 1: the design configuration field

1. In the admin, open the design configuration and edit the store view (or the website, if all its views should carry the chat).
2. Find the HTML head section and paste the line into the field for scripts and style sheets.
3. Save the configuration.
4. Flush the cache. Until you do, the storefront serves the old pages.

Route 2: a module

1. A developer adds the script tag through layout XML in a small module, with your bot id as data-bot-id and defer kept.
2. Deploy, enable the module and flush the cache.

There is no Allinaa extension on the Commerce Marketplace today, so a store's own module is the route. A developer who needs the line can get it from you through Send the code to my web developer in your cabinet.

Several store views and languages

Set the field on each store view that should have the chat, or at website level for all of them. One bot serves all views: the assistant answers in the visitor's language within the languages chosen in your cabinet, three on Standard and all supported languages on Premium.

Check the installation

Open the live site in a private window and look for the button; then click Check my site in your cabinet, which reads the homepage and up to two pages it links to. If the button is there but the check says not found, the pages it read are probably cached or the code sits on pages it did not open; the status turns to installed anyway once the assistant loads on any page of your site.

If the button is missing right after saving, the cache was not flushed. The troubleshooting page has the rest; the online stores page describes product questions in chat.

Frequently asked questions

Do I need a module to add the chatbot to Magento?

No. The design configuration has a field for scripts in the HTML head. A module is the developer's alternative.

Is there an Allinaa extension on the Commerce Marketplace?

Not today. Use the design configuration field or a small module of your own.

Head or body?

The head field is fine: the script is deferred and waits for the page body.

Why does nothing change after I save?

Flush the cache. Magento serves cached pages until you do.