Frequently asked questions.

Not for the analytics themselves, because they do not set a cookie. Visitors are counted with an anonymous identifier held in localStorage, IP addresses are hashed with a salt rather than stored, and no fingerprinting is used. Whether your site needs a banner overall still depends on everything else you run — an ad pixel elsewhere on the page does not stop being a cookie because our tag is not one.

Page views and events, the referring source, an approximate location derived from the IP, device and browser type, and an anonymous identifier that lives in the visitor's own browser. The raw IP address is hashed with a salt and never stored in its original form, and there is no cross-site tracking: a visitor identifier means nothing on anybody else's site.

It is built to make compliance easier rather than to make a claim on your behalf: no cookies, no raw IPs, no fingerprinting, and data you can export or delete. Whether your particular setup is compliant depends on your site, your jurisdiction and your own privacy notice — we give you fewer things to disclose, not a legal opinion.

The tag is 9.2 KB gzipped over the wire — 30 KB unminified — and loads asynchronously, so it never blocks rendering. That single request replaces what is often several hundred kilobytes across an analytics tag, a heatmap script, a chat widget, a popup tool and a WhatsApp plugin. It also reports your own Core Web Vitals back to you, so you can watch the effect rather than take our word for it.

You paste one script tag before the closing body tag. On WordPress that is a header-and-footer plugin or your theme settings; on Shopify or Webflow it is the custom-code panel; on a hand-built site it is one line in the template. Nothing else needs configuring for data to start arriving.

No, and this is deliberate. The tag you install is a small loader that fetches its configuration and behaviour from the server on each page load, so new capabilities and any setting you change apply on the next page view without anyone touching the site again.

Scope, mostly. General analytics tells you what happened; Insight OS also shows who is on the site right now and gives you a way to talk to them — chat, WhatsApp, click-to-call and lead capture from the same script. It is one dashboard for both halves rather than an analytics tool plus four other subscriptions. If deep funnel and attribution modelling is your main job, a specialist analytics product will go further.

The button opens WhatsApp with your business number and a prefilled message, using the visitor's installed app on mobile or WhatsApp Web on desktop. There is nothing for them to install beyond WhatsApp itself, and the click is recorded as an event so you can see which pages actually generate conversations.

They are never dropped. An offline message becomes a lead with the visitor's contact details attached, and so does an abandoned pre-chat form — someone who typed their email and then closed the tab still reaches you, which is usually the message you would most regret losing.

Yes — appearance and behaviour are controlled per site from the dashboard, and because the tag reads that configuration on each page load, a change applies on the next page view without a re-install.

Yes, and it is the reason the product exists in this shape. Every site you add appears in the same dashboard with its own key and its own settings, so an agency or an owner with a dozen properties works from one login instead of one per tool per site.

You do. Reports export to CSV whenever you want, and any site can publish a read-only public stats page on a token URL for a client or a colleague who should not have a full login. Nothing here is designed to make leaving difficult.

Insight OS is free during early access, with the whole product switched on and no card required. Paid plans will arrive with general availability; the commitment we can make now is that early-access workspaces get advance notice before anything changes, and nothing switches off while you decide.