This Community Template installs Pulse Analytics, privacy-first web analytics from Ciphera, through GTM without a Custom HTML tag.
Pulse Analytics sets no cookies and never stores IP addresses, and the script the template loads is about 3 KB.
Once the template is in the Community Template Gallery:
- In GTM, go to Templates → Tag Templates → Search Gallery
- Find Pulse Analytics, add it to your workspace
- Go to Tags → New → Pulse Analytics
- Leave Domain blank for a single-site container, or set it to the domain your site is registered under in Pulse Analytics
- Set the trigger to All Pages (Initialization is better still, if you use it)
- Click Submit
You need a Pulse Analytics account with a site registered for that domain. The free plan is enough to start.
| Option | Default | What it does |
|---|---|---|
| Domain | the page's own hostname | The domain the site is registered under. Leave blank for one container serving one site; set it when a container serves several domains, or when the registered domain differs from the hostname. |
| API origin (advanced) | none | Set this only if you proxy Pulse Analytics through your own domain. Enter the origin only, without a path, because the script appends its own path. |
Scroll depth, outbound links, file downloads, and clicks, copies and form submits are each switched on or off in your site's settings in Pulse (Settings → General). The tag stays the same, so there is nothing to change here.
The Pulse Analytics docs show a tag carrying data-domain. This template cannot
emit that, and no GTM template can: the sandboxed
injectScript(url, onSuccess, onFailure, cacheToken) takes a URL and callbacks
and has no parameter for HTML attributes. GTM also strips data-* from
Custom HTML tags.
The tracker reads document.currentScript first and falls back to
window.pulseConfig, which it carries deliberately for tag managers. So the
template sets window.pulseConfig and then injects the script, which is the
same install by a different route.
It merges into an existing window.pulseConfig, so a setting you made by
hand is not silently dropped.
Pulse Analytics exists partly so that measuring your traffic does not require a US provider. Running it through Google Tag Manager puts one back in the path: the container script is served by Google, and Google sees the request for it. The tag itself sends nothing to Google, and Pulse Analytics still sets no cookies and never stores IP addresses. But if avoiding that path is the reason you chose Pulse Analytics, install the tag directly instead. The framework guides show how.
node scripts/check-template.mjsThe guard checks what the gallery would otherwise tell you about days later, in
a review issue: the seven sections and their order, that the JSON blocks parse,
the 1 to 3 category rule, that inject_script is pinned to Pulse Analytics' own
origin, that every URL the JS injects is covered by that allowlist, that the
test suite has not shrunk, and that LICENSE is the Apache-2.0 text.
Copyright 2026 Ciphera BV. Licensed under Apache-2.0. LICENSE is the licence
text verbatim, which the gallery requires.
This template is not affiliated with, endorsed by, or sponsored by Google. Google Tag Manager is a trademark of Google LLC.