Home Compare
An honest comparison
One snippet, or five of them.
Most sites end up running an analytics tag, a heatmap script, a chat widget, a popup tool and a WhatsApp button — five vendors, five scripts, five dashboards, one visitor. Here is how that stack compares with doing it in one.
At a glance
The stack, side by side.
Compared against the typical arrangement: a general analytics tag, a session-recording or heatmap tool, a chat widget, a lead-popup tool and a WhatsApp plugin.
| What you are comparing | A stack of five tools | Insight OS |
|---|---|---|
| Scripts on the page | Five vendors, five DNS lookups, five connections before anything renders | One tag, loaded async |
| Weight over the wire | Commonly several hundred kilobytes combined, chat widgets being the heaviest part | 9.2 KB gzipped, 30 KB unminified |
| Cookie consent | The analytics tag and most popup tools set cookies, so a banner is required | Cookieless by default — no cookie is set, no banner needed for it |
| What identifies a visitor | Varies per vendor; often cookies plus fingerprinting signals | An anonymous localStorage id; IPs hashed with a salt, never stored raw; no fingerprinting |
| Changing what is switched on | Edit the page, redeploy, and repeat it per tool and per site | Toggle it in the dashboard — the tag re-reads its configuration on the next page load |
| Seeing who is on the site now | Usually a paid tier of the recording tool, in its own dashboard | Built in: live visitors, city, device, source, journey and intent score |
| Chat, WhatsApp and click-to-call | Separate vendors, separate widgets, separate inboxes stacking up in the same corner | One widget, one inbox, one place to answer from |
| A message someone starts but never sends | Typically lost — if it was never submitted, it was never captured | Captured as a lead, including abandoned pre-chat details |
| Running several sites | One login per tool per site, so twelve sites means a lot of tabs | Every site in one dashboard, switchable from the same screen |
| Where the data lives | Split across five vendors, each with its own export story and terms | One place, with CSV export and public share pages |
Script weights vary by vendor and configuration — measure your own with your browser's network panel, which is exactly how we measured ours (curl with gzip, on the file this site serves). Product names are trademarks of their respective owners; this page compares categories of tool rather than any specific vendor's current offering.
Pick the right one
When each approach wins.
A dedicated analytics product
Deep, mature reporting, years of edge cases handled, and a team that does nothing else. If your job is analysis — funnels, cohorts, attribution modelling — a specialist tool will go further than we do.
Right for you if analytics is the work, not a means to an end, and you have no interest in talking to visitors from the same tool.
A dedicated support platform
Ticketing, SLAs, routing rules, help centres and a shared inbox built for a support team working queues all day. Chat is one channel among many, and the workflow around it is the product.
Right for you if you have a support team with a queue and escalation paths, rather than a founder answering messages between other work.
Insight OS
One script that tells you who is on the site and lets you talk to them before they leave, controlled from one dashboard across every site you run.
Right for you if you run one site or twenty, you want to stop maintaining five tags, and the questions you ask are “who is here, where did they come from, and how do I reach them?”
The part that is hard to copy
Change the site without touching the site.
The snippet is a loader. Everything it actually does — which features are on, how the widget looks, what counts as an event — comes from the server on each page load.
So switching on WhatsApp for a client site, or turning off the popup during a sale, is a toggle in the dashboard rather than a code change, a deploy and a conversation with whoever owns the release. Across a dozen sites, that difference stops being a convenience and starts being the reason the stack is maintainable at all.
- Install once, change behaviour whenever
- No re-install when new features ship
- The same story on every site you manage
Site settings Applied live
Replace the tags, keep the data.
Run Insight OS alongside what you already have for a week and compare the numbers yourself.