Analytics from requests, not from tags.
If a site is already proxied through the global edge, the request records are the analytics. Reveliqo reads document and page requests as they pass: source, campaign, status, origin latency, country and traffic quality. Nothing is added to the page, and nothing is added to the response time.
In short: Sites already proxied through the edge produce traffic, source, campaign, status, latency and traffic-quality analytics from the request records themselves — no page tag required, and no analytics call inside the request path.
What it is
The edge is the protection and delivery layer that sits in front of a site: a reverse-proxy fleet that terminates TLS, filters attacks, caches, and forwards what remains to the origin. Every request crosses it.
What this lets you ask
- “How much of last night's traffic spike was human, and how much was AI crawlers?”
- “Which referrers and campaigns send people to the pages that error most?”
- “Did origin latency move in the hour our conversion rate started falling?”
What Reveliqo receives
- Document and page requests with route template, HTTP status, bytes and origin latency — /orders/883729 is stored as /orders/:id.
- Referrer, source and campaign parameters read from an allowlist, resolved into channels including search, AI assistants, social and direct.
- Country, device class and browser family derived at the edge, with no raw IP address written to analytics storage.
- Traffic-quality classification: human visits, verified search crawlers, AI crawlers, other automation, challenged traffic, and requests blocked before the origin.
How it is connected
- Turn on analytics for a zone in the edge control plane and select the Reveliqo workspace that receives it.
- Confirm the hostnames and route templates to measure; identifiers in paths are collapsed to templates before anything is stored.
- Choose the collection mode — Minimal, Visit or Customer — which the consent state then constrains per region.
- Traffic counts from the next request. There is no tag to deploy, and collection runs outside the request path, so a pipeline outage costs data rather than response time.
How you verify it
- Load a page and check it against the live view: the request appears with its route template, status, country and quality class.
- Compare edge request counts with origin access logs for the same hour. The difference is cached and blocked traffic, and it should be explainable.
- Request the same page with scripts disabled. The edge still records it — which is the reason this layer exists.
Limits worth knowing
- DNS alone provides none of this. The data comes from proxied HTTP traffic crossing the edge; a domain whose records merely resolve elsewhere produces no analytics here.
- The edge sees requests, not what the browser does afterwards. Engagement, scroll, Core Web Vitals and SPA route changes need Smart Beacon.
- Traffic that bypasses the edge is not measured — an unproxied subdomain, a direct origin IP, or an application calling a host outside the fleet.
Other integrations
Connect the rest of the stack
Connect a site today. Read tomorrow's brief instead of building it.
Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.
Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo