Getting started
Embedding in your website
One line of code for every website, instructions for each site builder, and control through your cookie banner.
Your Talky comes onto your website with a single line. You find the code in the customer area in your website's Embedding tab:
<script src="https://embed.talkypage.com/v1/loader.js"
data-key="tpk_…" async
data-cfasync="false" data-no-optimize="1" data-no-minify="1"></script>The three data- attributes keep caching and performance plugins away from the code, see Caching and performance plugins.
The code only loads on the domains you have entered. If someone copies it onto another website, the Talky stays silent there.
By site builder
| Site builder | Where the code goes |
|---|---|
| WordPress | In the theme before </body> or with a plugin for custom scripts, such as WPCode. With a caching plugin, see Caching and performance plugins. |
| TYPO3 | In TypoScript as page.includeJSFooter or in the template. |
| Joomla | In the template or with an extension for custom scripts. |
| Wix | Settings, Custom Code, "Body – end". |
| Jimdo | Settings, Edit Head. |
| Squarespace | Settings, Advanced, Code Injection, Footer. |
| Webflow | Project settings, Custom code, Footer. |
| Duda | Site settings, Head HTML. |
| Shopify | Theme, Edit code, theme.liquid before </body>. |
| Static HTML | In every page before </body>, also on Netlify, GitHub Pages or your own server. |
The customer area has step-by-step instructions for the common site builders.
Cookie banner
As a rule you need no change to your cookie banner: TalkyPage stores nothing on the visitor's device and connects to nothing before they click.
If you still want your banner to control the Talky, there is the consent mode: with data-consent the Talky waits until your banner releases it with TalkyPage.consent(). The customer area explains how this works for seven common banners.
When your website changes
TalkyPage reads your website again every week. After larger changes you can start the reading at once in the Pages tab, or automatically through a deploy hook, for example from Netlify, Vercel, GitHub Actions or a script of your own.
A guest on your website
The Talky lives in a closed-off area (Shadow DOM) and uses only one single global name, window.TalkyPage. It does not interfere with the style, history or navigation of your page unless you set it to.
Rather try it than read about it? Talk to our Talky, or we'll set up a preview on your own website.