A single script tag is all that Talkmio needs on a website. The integrations page lists more than two dozen platforms, from WordPress and Shopify to Ghost, Framer and Laravel, and ends with a simple promise: the widget is one script tag, and the team builds modules on request. This guide explains what the script tag is, where it must go, how the pattern differs between site builders, content management systems and shops, which plan requirements the builders attach to custom code, what to do when your platform is not on the list and how to test and troubleshoot the result.
The details come from the Talkmio documentation and from the individual integration pages on talkmio.com. Platforms change their menus often, so use the names below as a guide to what to look for.
What the Script Tag Is
The Talkmio chat is added to a page by a short piece of code. On the integration pages it looks like this, with your own site key in place of the placeholder: a script element whose source is the Talkmio address followed by your site key and the file type, with the async attribute. The site key is a short key of twelve characters that you get when you add your website under Websites in the Talkmio app. The async attribute tells the browser to load the chat without waiting, so that it does not hold back the rest of the page.
Because it is one line, it works anywhere that accepts a script. That is the reason for the integration list being long: each entry is mostly a note about where that platform keeps its custom code. A HTML script element is part of the standard markup of every web page, so a platform that lets you add code to every page can carry the chat.
Where the Script Tag Goes: One Rule
The documentation gives one rule for every platform: paste the snippet before the closing body tag on every page. In builders that do not show you the page template, the same idea appears under different names: the footer, the end of the body or site-wide code. If you can choose between the head and the footer, choose the footer, so that the page content loads first.
Two details matter. The snippet must be on every page on which you want the bubble, so site-wide settings are better than page-by-page edits. And it must be published: many builders keep a draft version of the site, and the code does nothing until you publish. Our guide to adding live chat to any website covers the general steps.
Modules Versus Custom Code: Two Families
The integration pages fall into two families. For some platforms Talkmio offers a ready-made module, plugin or package, and for the rest you paste the script tag into a custom code area. The table shows how they group.
| Family | Examples from the integrations page | What you do |
|---|---|---|
| Ready-made module or plugin | WordPress and WooCommerce, PrestaShop, OpenCart, Magento 2, Joomla, Drupal, TYPO3, Odoo, Laravel, React and Next.js | Install the download, paste the site key in its settings |
| Custom code, no plugin | Shopify, Wix, Squarespace, Webflow, BigCommerce, Blogger, Ghost, HubSpot CMS, Framer, Carrd, GoDaddy, Hostinger, Vue and Nuxt | Paste the snippet in the footer or body-end code area |
| Tag manager | Google Tag Manager | Import the container or add the script as a tag that fires on all pages |
| Anything else | A site that you built yourself, a framework or an unlisted builder | Add the script tag to your base template or layout |
Modules also offer extras that a bare script tag cannot, such as the option, on several platforms, to pass the name and e-mail of a logged-in user to the Inbox. With a plain tag you can still do this on your own, as described below.
Plan Requirements on Builders
The most common surprise with the script tag is not Talkmio but the builder. Several site builders allow custom code only on paid plans, and the integration pages say so. Check this before you start.
- Wix: custom code requires a Wix premium plan with a connected domain.
- Squarespace: code injection is available on the Business plan or higher.
- Webflow: custom code requires a paid Webflow site plan.
- Framer: custom code needs a paid Framer site plan.
- Carrd: embeds need a Carrd Pro plan.
Plans and rules change, so confirm on the builder’s own pages before you buy anything. If you are on a free plan of a builder, you may have to upgrade it, or choose a different place for the chat, before it can be installed. Our guide to adding live chat to a static site shows the pattern for sites that you host yourself.
When Your Platform Is Not on the List
If your platform is missing from the integrations page, there are four routes, in a sensible order.
- Look for a custom code area. Search the settings for words such as custom code, code injection, header and footer, tracking code, third-party scripts or HTML embed. Most builders have one.
- Edit the base template. If you control the template, add the snippet to the layout that every page shares, before the closing body tag.
- Use a tag manager. If the platform lets you add a tag manager, add the Talkmio script as a tag that fires on all pages. Our guide to live chat with Google Tag Manager explains the steps.
- Ask Talkmio. The integrations page says: need another platform? Write to support, since the widget is one script tag and modules are built on request.
If none of these works, the platform probably does not allow third-party scripts, and no chat tool can run there, because every website chat, whatever its brand, needs to run some code in the visitor’s browser. In that case, the practical choice is to link from your site to a page on a domain that you control, where the chat can be installed.
Step by Step for an Unlisted Platform
- Create a free account at app.talkmio.com and add your website under Websites. Copy the twelve-character site key.
- Build the line of code from the pattern on any integration page, replacing the placeholder with your key.
- Find the footer or body-end code area, and paste the line there. Save.
- Publish the site, and clear any cache that your host or platform uses.
- Open the site in a private browser window. The chat bubble should appear in the corner.
- Ask Mio two or three questions that customers often ask and check that each answer comes from your own pages. If something is missing, add it to your website or knowledge base and ask again.
How the Chat Loads and What It Means for Speed
The async attribute in the snippet tells the browser to fetch the chat file at the same time as the rest of the page and to run it when it is ready, instead of stopping the page while it waits. For visitors, that means the text, images and buttons of your page appear first, and the chat bubble arrives a moment later. This is also why the footer is the right place: if the chat is slow for any reason, it cannot delay the content above it. If you care about speed, test the page before and after with a tool such as your browser’s developer tools or a page speed service, and compare the loading times of the main content, not only of the whole page. Our guide to live chat widget page speed explains what to measure.
Identify Logged-In Users With a Plain Snippet
If your site has accounts, you can tell the Inbox who is writing. The Vue and Shopify pages show the pattern: before the Talkmio script, set a variable in the page that carries the visitor’s name and e-mail, for signed-in users only. The module versions of the integration do this for you. With a plain snippet, you add a few lines in your template, and only when a user is logged in. Think about privacy before you do it, and about who will maintain the code when your template changes. Passing a name and an e-mail to the chat is useful for your team, but you should mention it in your privacy policy, and pass nothing that you do not need. Our guide to live chat contact history explains how returning customers are recognised.
Keep a Record of Where the Chat Is Installed
It is tempting to treat the install as a one-minute job and to forget it afterwards. Websites live for years, and the people who built them move on, so a short record is cheap insurance.
An install is only done when someone else could find it. Write a short note for each website: the platform, the place where the snippet sits, the site key, the date and the person who did it. Put the note where your team keeps website documentation. When you redesign the site, change the theme or move to another platform, the chat will not carry over by itself, and the note is your checklist for putting it back. After a redesign, run the test again: open a private window, check the bubble on the main page types and ask Mio a question. Our guide to a website redesign checklist for live chat lists the checks. A good habit is to add the same note to every new website project from the start, next to the analytics and the cookie banner, so that the chat is never the forgotten script.
Test and Troubleshoot
If the bubble does not appear, work through these checks in order.
- Is the tag on the page? View the page source in the browser and search for the Talkmio address.
- Is the key right? Copy it again from Websites in the Talkmio app.
- Is the site published? Builders keep drafts. Publish and clear caches.
- Is a security policy blocking it? A strict content security policy can block scripts from other domains, so allow the Talkmio address. Our guide to live chat and content security policy explains how.
- Is a consent tool delaying scripts? Some tools wait for a visitor’s consent. Check the settings, and the overlap of the cookie banner with the bubble.
When all five are checked and the problem remains, write to support with the page address and a short description. See the integrations page for the list of supported platforms and instructions.
Frequently Asked Questions
What exactly do I paste on my website?
A single line of code whose source is the Talkmio address plus your twelve-character site key, with the async attribute. The integration pages show the exact line with a placeholder for your key. Paste it before the closing body tag on every page.
Where do I find my site key?
In the Talkmio app, open Websites and add your website. Talkmio shows a twelve-character site key together with the install snippet. Copy it into the script tag, or into the settings of a plugin or module if your platform has one.
Does my site builder allow custom code?
Many do, often on paid plans. The integration pages say that Wix needs a premium plan with a connected domain, Squarespace needs the Business plan or higher, Webflow and Framer need paid site plans and Carrd needs Pro. Check your builder’s current rules before you start.
What if my platform is not listed?
Look for a custom code area, add the tag to your base template, use a tag manager, or write to Talkmio support. The integrations page says the widget is one script tag and that modules are built on request.
Why does the bubble not show after I pasted the tag?
Usual causes are an unpublished site, a cached page, a wrong key, a tag on only some pages, a content security policy that blocks the script or a consent tool that delays it. Check the source of a page, clear caches and test in a private window.
Can I show my team who is logged in?
Yes, on platforms where the module offers it, and also with a plain tag by setting a variable with the name and e-mail of signed-in users before the script. Mention this in your privacy policy and pass only what you need.
The Bottom Line
If a website accepts one line of custom code, Talkmio fits it. Add your site, copy the twelve-character key, paste the snippet in the footer on every page, publish, clear caches and test in a private window. Check the builder’s plan rules first, and write to support when your platform has no code area. Start free with Talkmio and have the chat bubble on your site before lunch.
