edgeglint
Useful website analytics, without visitor histories.
See which pages get attention, how far people scroll, which buttons they click, and where JavaScript breaks.
edgeglint runs on Cloudflare Workers + Analytics Engine, with a small same-origin tracker and a dashboard in your own account.
Get started · Why edgeglint · What it measures · Privacy and data flow · Project page
Actual edgeglint v0.2.0 dashboard, shown with generic demo fixtures. These are not customer traffic figures. Screenshot provenance.
Why edgeglint
- Find friction beyond pageviews. See scroll-depth buckets, element click counts, rage/dead-click heuristics, outbound links and JavaScript error classes.
- Keep your Cloudflare stack. A Worker collects measurements into Analytics Engine; the dashboard queries them through the Analytics SQL binding. No separate database server to operate.
- Serve the tracker from your own domain. Script, collection endpoint and dashboard share your site's origin. The tracker has a tested ceiling of 3,072 bytes gzip.
- Collect less by design. No measurement cookies, localStorage or visitor identifiers. No form contents, page text, query strings, pointer trails or session replay in the measurement dataset.
- See engagement and quality together. Page activity, referral sources, scroll, clicks, error counts, and average LCP/CLS share one overview.
- Control what is measured. Host/path allowlists, a collection-off switch, GPC, DNT and explicit opt-out checks are part of the collector, not optional dashboard filters.
When to choose it
edgeglint fits a Cloudflare-hosted site where aggregate page and interaction measurements answer the questions you need,
and you prefer a small, inspectable collector over operating a separate analytics database.
Cloudflare Web Analytics already supplies Core Web Vitals; edgeglint's focus is the additional bounded interaction and error measurements.
See the source-linked comparison for alternatives and the limits of that research.
Choose another approach if you need unique visitors, returning-user histories, session replay, funnels tied to people,
or complete regional coverage. edgeglint does not provide those capabilities.
Pilot, with explicit trade-offs. The current country-code rule excludes the EEA, UK, Switzerland and related areas,
unknown countries and Tor. This reduces coverage; it is not a legal consent map or a compliance guarantee.
Cloudflare still processes requests, and operational logs are separate from the measurement dataset.
The software license is undecided and all rights remain reserved. Review the use terms before adoption.
Choose an installation
- New collector: use the standalone Worker below.
- For a Worker, Astro or Pages project: use the source adapters.
- No npm package is available. Check the use terms before installation.
Cloudflare documents this button path, but we have not tested it with these Analytics Engine, rate-limit and Analytics SQL bindings.
Read the button documentation for the platform mechanism.
For a new project, C3 also documents this template command:
npm create cloudflare@latest -- --template https://github.com/dataxad/edgeglint
The C3 path is untested here. Configure the account, bindings, routes and runtime secret before collection.
Choose a level
Start with level 0, the current measurement features, before adding a consent form or tracking service.
It gives pageviews, referrer-based visits, scroll, clicks, errors, LCP and CLS averages, and width groups.
The dataset has no visitor identifiers. The country-code rule decreases coverage.
- Level 1 proposes daily unique visitors with a daily identifier and a different legal review.
- Level 2 proposes wider coverage after consent or a French exemption profile with review approval.
- Levels 1 and 2 are proposals. They have no flags.
- Level 3 uses external replay and heatmap tools. It is not part of edgeglint.
Read measurement levels and data flow before deployment.
For AI agents
Read docs/kb/index.md first: the one-page design in docs/one-page/ and the knowledge base behind it.
Read AGENTS.md for the shared installation procedure.
Use llms.txt as the documentation index.
Load the edgeglint-install skill from .agents/skills/, .claude/skills/ or skills/ when necessary.
What it never collects
- IP addresses or raw User-Agent strings in the dataset.
- Measurement cookies, local storage or visitor identifiers.
- Pointer coordinates, cursor traces or session replay.
- Form contents, page text or query strings.
- Element IDs, CSS classes, attribute values or error messages.
The edge reads request information for country, bot checks, rate limits and browser versions. It does not keep the raw values.
A visitor-selected opt-out cookie and a dashboard authentication cookie have different purposes. These cookies do not identify visitors for measurement.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
