Server-side tag manager: keep bot traffic out of your conversion data
Hand-pasted scripts slow your pages down and fire for every bot that runs them: your ad platforms count its conversions and learn from it. Declare your tools in the console instead. Klacos fires each tag at the right moment, from your own domain or from the server, and not for visits it recognises as bots. Your campaigns learn from people.
What hand-pasted tags cost you
Heavier pages
Every tool adds its own script, which each visitor’s browser downloads and runs. The site slows down as campaigns pile up.
Campaigns that learn from bots
A bot that runs your pages fires your tags just like a visitor. Your conversion reports count it, and your ad platforms tune your campaigns on it.
One more server to look after
Server-side tagging usually means hosting, securing and monitoring your own tagging server, alongside the site.
Tags fired by the service that already analyses every visit
Your tags fire from the service in front of your site, the one already analysing every visit to tell visitors from bots. A tag set to skip bots doesn’t fire for them, in the page or from the server. Your analytics and ad conversions are cleaned at the source, rather than filtered afterwards, if they’re filtered at all. The same conversions feed your goals and funnels in the console.
It’s the same judgement used by bot management and cookieless analytics. Our guide to bot traffic in your analytics explains how bots end up in your figures.
Tag management, in the same place as your site
Ready-made templates
Precise triggers
Variables
Your setup carries over
Server-side sending
Switched off for bots
Versions and environments
Preview before publishing
From your own domain, or from the server
Your tags go out in three ways. Your site’s container is a single file, served from your own domain next to the analytics script. Simple tags are added to your pages by the service itself, without you touching the code. And server-side sending needs no script in the page at all: your ad platforms get the data without that sending storing anything on the visitor’s device.
There’s no tagging server to host: the service in front of your site does that job. Tags load without holding up rendering, in the order and with the delays you set, and they respect your site’s content security policy.
Publish with confidence, and impose nothing on your visitors
Every release on record
Who published what, and when. A release that causes trouble comes out in one step, and the previous one is back.
Consent stays with you
A tag can wait for the choice made in your consent tool. Klacos doesn’t replace that tool: it follows what it decides.
What your tags are doing
How many times each tag fired, and on which pages, in the console.
The tag manager is part of the analytics capabilities in Klacos, alongside traffic analysis and cookieless analytics.
Questions about the tag manager
Can I leave my current tag manager without starting over?
Your data layer calls (dataLayer) work without a rewrite, and your tags are rebuilt from the templates. The longest part is usually sorting out which tags still earn their place.
Will my tools still set cookies?
The tools you fire in the page set their own, as they do today. With server-side sending, they get the data without any script in the page.
Do I need the service in front of my site?
The container also works with the analytics script alone. Server-side sending, tags added to your pages and full bot filtering need Klacos in front of your site.
Can I write my own tags?
Yes: custom HTML or script, alongside the templates. They go through the same preview and the same versions.
Preview your tags on your live site before you publish
Request early access, or tell us about the analytics and advertising tools you use today.