Web analytics
Behaviour and experience from a first-party beacon that sets no cookie.
- Journeys, goals, funnels and revenue
- Real-user Web Vitals and JavaScript errors
- No cookie, no visitor ID, no stored address
Behavioural, request-level, search and answer-engine signals, kept apart because they answer different questions. One site, one time range, one operating language.
It never sees a crawler handed a 500, an answer engine citing a competitor, or a request blocked before the script loaded. Abnio measures those layers separately, then puts them behind one site and one time range.
Behaviour and experience from a first-party beacon that sets no cookie.
Every request your edge and origin actually served, script or no script.
What search engines and answer engines do with the content you publish.
A first-party, cookieless beacon records meaningful behaviour and experience. Visitor identity rotates daily, which makes aggregate journeys possible without building a durable profile of anyone.
Visitors, pageviews, engagement and goals with period comparison, plus a rolling 30-minute live pulse.
Landing pages, referrers, campaigns and channels. Filters follow you from one report into the next.
Country, region, city, device, browser and operating system, derived without storing an address.
Real-user Core Web Vitals and navigation timing show where visitors actually wait.
Custom events, outbound links, downloads, forms, rage clicks and JavaScript failures in one stream.
Name an outcome, see where people leave the sequence, attribute the revenue. No second product needed.
Log intelligence reads edge and origin access logs, so it sees what browser JavaScript cannot: every request served, every crawler, every cache result, every failure. Source-aware deduplication keeps the totals honest.
Watch paths, status codes, sources and traffic classes as they reach your delivery stack.
Search-engine crawls, the pages they favour and how that moves, measured at the request layer.
Assistant reads, AI referrals and AI crawler traffic, separated rather than pooled into one bot bucket.
Cache hit ratio, points of presence and heavy assets across both edge and origin sources.
Trace 4xx and 5xx trends to their top paths, with referrer-level detail where it helps.
Namespaced request signatures and an explicit partial-data state prevent double-counting and false precision.
Privacy note: server-log analytics retains the raw User-Agent for bot classification and forensic drill-down. Raw IP addresses are still never stored. This distinction is disclosed plainly throughout Abnio.
Google Search Console performance beside repeatable prompt monitoring across seven answer engines: whether your brand appears, whether your site earns the citation, and what the engine actually said.
Monitor a deliberate set of real buyer questions, imported from search data or managed directly.
Run one panel across seven engine adapters behind a single measurement contract.
Brand presence stays separate from direct source citation. They are different kinds of visibility.
Wilson confidence intervals and sample-aware rates stop a handful of answers becoming a claim.
Every returned answer is archived, so your team can read the context behind an aggregate score.
Clicks, impressions, CTR and position, joined to the newer crawl, cite and click discovery funnel.
Abnio is multi-tenant at the data boundary, not only in the interface. Every analytics route is scoped to a site, customer roles are explicit, and the controls that carry weight stay in the application.
Site-level admin and read-only viewer roles give each person only the properties they should see.
App-native TOTP protects every customer account, with recovery codes for safe re-entry.
Mint a new ingest token, migrate at your pace, then revoke the old one. Collection never stops.
Abnio checks your live production host for the active snippet before it calls setup complete.
Daily analytics follows each site’s IANA timezone, so today means the operator’s actual day.
Authentication, collection correctness and authorization live in the app, not in an edge vendor.
An answer engine crawls a page, decides whether to cite it, and a reader may then click through. Those three steps land in three different modules. Abnio reports them for the same site, over the same days.
Start with Web, add Logs or GEO, and keep one operating view across them. Tell us what you run and we will shape a setup around your traffic, your stack and your data requirements.