The part of a visit only the browser can see.
The edge counts the request. It cannot see a route change that never leaves the browser, or how long someone actually read. Smart Beacon adds that layer: SPA navigation, engagement time, Core Web Vitals, clicks, form starts and submits, and the content assets a visitor was shown.
In short: A small first-party script that adds what only a browser can see — soft navigation, engagement, Core Web Vitals, clicks, form behaviour and client-side conversions — on top of what the edge already counts.
What it is
A bootstrap script of a few kilobytes, served from a path on your own domain such as /__reveliqo/event. No framework dependency, no bundler step, and no third-party host in the page's network graph.
What this lets you ask
- “Which pages hold attention and still fail to convert?”
- “Did the INP regression on Safari reach real users, or only our lab runs?”
- “How far into the checkout form do people get before they leave?”
What Reveliqo receives
- Soft navigation in single-page applications, recorded as the route template rather than the rendered URL, plus any route metadata you attach.
- Engagement: active time on page, scroll depth, and whether a visit was read or abandoned within seconds.
- Core Web Vitals as field measurements — LCP, CLS and INP from real visits at the 75th percentile, not a lab score.
- Clicks, custom events, form starts and submits, client-side conversions, and content-asset exposure IDs.
How it is connected
- Add the bootstrap tag, or proxy /__reveliqo/* from your own domain so collection stays on a first-party network path.
- Point the collector path at ingestion. One connect-src entry for your own origin is usually the whole CSP change.
- Declare which routes, events and form identifiers are collected. Anything undeclared is discarded at ingestion rather than stored and filtered later.
- Set sampling for high-volume behavioural events — engagement and vitals can sample while conversions stay at 100%.
How you verify it
- Open the network panel: batched requests to your own domain, sent with sendBeacon or fetch keepalive, never blocking navigation.
- Trigger a route change and a form submit, then watch both arrive in the live view within seconds.
- Compare beacon pageviews with edge document requests for the same hour. A persistent gap is mostly collection that never ran, and it is worth knowing.
Limits worth knowing
- Any client-side beacon can be blocked. Extensions, blocklists and strict browser modes stop some of it, and the edge layer keeps counting those visits.
- Beacon and edge numbers will not match exactly, and are not meant to. The edge is the traffic baseline; the beacon adds behaviour on top of it.
- An event sent from a browser is only as trustworthy as that browser. Revenue and conversions that must be exact belong in server-side Business Events.
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