Cookieless website analytics, matched to the leads they bring.
Built-in cookieless website analytics for every client site: visitors, pages and sources, with traffic to leads on the same screen — without Google, without cookies on the visitor’s device.
Traffic to leads
See which pages and sources turn into enquiries.
Every accepted form submission adds an anonymous lead event to that visit. Pages, items, referrers and UTM campaigns show the leads they brought — traffic to leads without a separate goals product.
Leads on every panel
Visitors, page views, visit length and bounce rate sit beside leads and conversion for the same range.VisitorsViewsLeads2.5%Content that converts
Content performance ranks every page and item: most read, best at leads, traffic with no leads, and falling.Best at leadsNo leads yetClick a row to filter
Narrow the whole screen to one page, source, campaign, country or device — the chart and panels follow./contactgoogleutmSame leads you already work
The leads in Analytics are the website's Forms & Leads records — one place to count them, another to call back.AnalyticsForms & Leads
Privacy-first
Website analytics without cookies on the visitor.
Privacy-first website analytics: nothing is stored on the visitor’s device. A daily visitor hash counts people once per day, then can’t link them to yesterday. The IP and full User-Agent are thrown away.
No cookies set
The script never writes a cookie or local profile. Owners can opt their own browsing out with one localStorage flag.CookielessA hash that expires daily
Visitor = hash of a daily salt, the website, IP and User-Agent. The salt rotates every UTC day and is gone after two.dailySaltIPUANo cross-site tracking
First-party measurement only: no ad networks, no session replay, no journeys across days. Aggregate stats for one website.No replayNo adsOne siteCopyable privacy text
Admin gives the privacy-policy paragraph to paste. The website owner stays the controller; mywebcms is the processor.Copy for your policy
Tracking setup
One lightweight script. Any stack.
Drop a tracking ID into the site’s layout, call POST /v1/collect from the server, or proxy both through your own domain. Only allowed domains are counted — the same list as the Content and Form APIs.
Recommended · any stack
<script defer src="https://api.example.com/v1/script.js" data-site="trk_…"></script>
About 1 KB. Sends a page view on load and on SPA route changes. Never put an API key in the page just to count visits.
Tracking ID, not the API key
Each environment gets a public trk_… id that can only send page views. It reads nothing.trk_…Three ways to install
Script in the layout, server-side collect with the API key, or a proxied script on your own domain for fewer ad blockers.ScriptServerProxyOnly your domains
Origins outside the environment's allowlist are refused and listed in setup, so a forgotten www is easy to spot.CORS allowlistEvery feature, every plan
Free includes the full Analytics module. Upgrading buys longer history: 30 days, then 12 or 24 months.30d12m24m
History per plan is on Pricing. Compare analytics history
FAQ
Questions about website analytics.
Cookies, consent, leads, plans and what stays out of scope.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.