Editing content
Add analytics and custom code
Add analytics tools and snippets of your own to every live page, pause them, and know which need consent.
Tidewater counts visits with Plausible and runs a chat widget from a snippet its support tool gave it. Both are set up under Site settings → Integrations, without changing the site’s code.
After reading this guide, you will know:
- How to add an analytics tool, and where to find what it asks for.
- Which tools need a visitor’s consent.
- How to add a snippet of your own, and where it goes on the page.
- How to pause either without losing its settings.
Note
Analytics and custom code load on the live site only: not in previews, the Control Plane, or while indexing is blocked. A test visit from a staging server never shows up in your numbers.
1. Analytics
Open Site settings → Integrations → Analytics and choose Add analytics. Pick a tool, then paste its snippet into the card exactly as the tool gives it: every tool has one on its install page, and each card says where. Add as many tools as you like; the tab’s name counts those that are running, as in Analytics · 2.
| Tool | Where its snippet is | Goes |
|---|---|---|
| Plausible | Site settings → Site installation | in the head |
| Fathom | Settings → Sites → Embed code | in the head |
| Umami | Settings → Websites → Edit → Tracking code | in the head |
| Cloudflare Web Analytics | Web Analytics → Manage site | at the end of the body |
| Google Analytics 4 | Admin → Data streams → View tag instructions → Install manually | in the head |
| Google Tag Manager | Admin → Install Google Tag Manager: two snippets | the first in the head, the second at the start of the body |
The snippet reaches the page exactly as you pasted it, where its tool says it goes. A card only accepts the snippet the tool gave you, so a stray ID or tag is refused when you save.
Some tools need one extra setting so they count every page a visitor opens, not just the first. Each tool’s card says what to switch on.
If your developer has added security rules for scripts, ask them to allow each analytics tool.
Cloudflare Web Analytics can be added once, since a page carries one beacon.
Tip
A tool that isn’t listed can go in custom code below, or your developer can add a card for it.
1.1 Consent
Each tool carries a badge. No cookies: Plausible, Fathom, Umami and Cloudflare keep nothing on the visitor’s device, and don’t need a consent banner. Needs consent: Google Analytics and Tag Manager set cookies, which in the EU and the UK needs the visitor’s agreement first.
Nibble has no consent banner of its own. If your site needs one, add your consent tool as custom code, and set it up to hold back the tools marked Needs consent until a visitor agrees.
2. Custom code
Custom code holds snippets a tool gives you to paste into a page: a chat widget, a heatmap, a verification tag. Choose Add snippet, name it, choose where it goes and paste the code into the editor. A collapsed card reads as its name and place, such as “Chat widget · At the end of the body”.
| Where | For |
|---|---|
| In the head | most tools, and anything that asks to be “before the closing head tag” (</head>) |
| At the start of the body | a snippet that asks to be “immediately after the opening body tag” (<body>) |
| At the end of the body | widgets that draw on the page, and anything that asks to be “before the closing body tag” (</body>) |
Snippets in the same place are written in the order of their cards; drag a card to move it.
Caution
A snippet is added to every live page exactly as written, and runs for every visitor. Only paste code from sources you trust, and only when you know what it is for.
3. Pausing and removing
The eye on a card pauses it: its settings stay, and nothing of it reaches the site until you turn it back on. A paused card isn’t counted in the tab’s name. The bin removes a card for good.
Saving clears every cached page, so a change reaches visitors straight away.
4. Who can change these
Anyone whose role may edit the Integrations settings, after entering their password again: what it holds runs on every live page. That permission is separate from the other site settings, and AI apps connected to the site can’t reach Integrations at all. See Users and roles.