How is Reveliqo different from Google Analytics?

Reveliqo starts from the business question rather than a reporting model you have to learn first. Ask why trial signups fell and the reply comes back as an explanation with its working shown, not a chart you interpret alone. The detail an analyst needs — dimensions, funnels, raw event rows, custom segments — stays available underneath every answer, and revenue from connected business systems sits beside the traffic.

Do I need to install a tracking script?

No. Sites proxied through the edge produce core request analytics — pages, referrers, campaigns, countries, status codes, origin latency and traffic classification — with nothing added to the page. Smart Beacon is optional and adds what only a browser can see: SPA navigation, engagement, Core Web Vitals, clicks, forms and client-side events. Run both and you have what the server saw and what the browser saw.

Do we have to move our DNS or our hosting?

Traffic has to be proxied through the edge, which normally means pointing the domain at the edge. DNS resolution on its own produces a name lookup and nothing else — there is no page, referrer, status code or latency in it. Once requests travel through the edge, the request records themselves are the analytics — nothing is added to the page and no analytics call sits inside the request path — and your origin and application stay exactly where they are.

Can ad blockers hide traffic from Reveliqo?

They can interfere with client-side beacons, as they can with any browser script. Requests that reach the edge are a different matter: they are counted where they are served, so pages, referrers, campaigns, status codes and latency stay in the record. A blocked beacon costs you browser-only detail such as Core Web Vitals and engagement; it does not cost you the request.

Does Reveliqo track bots?

Yes, and it separates them instead of folding everything into one traffic number. Requests are classified as human visits, verified search crawlers, AI crawlers, other automation and security traffic, and bot traffic is excluded before people, conversions and revenue are counted. An overnight jump in requests reads very differently once you can see that human visits did not move.

Can I ask questions in normal language?

Yes. Ask which channels bring the best customers, or what changed after yesterday's release, and the question is planned into a query against defined metrics and dimensions. Every answer carries the metric it used, the segment, the period and the comparison it made, so the number can be traced back to the rows behind it. Follow-up questions stay in the same context.

Does the AI calculate my metrics?

No. The semantic metrics layer and the analytics engine compute every number, from one stored definition of people, visits, conversion rate, revenue and revenue per visit. The AI plans which analysis to run, then explains the deterministic result it gets back. Two people asking the same question in different words get the same figure — and it matches the dashboard, the export and the API.

AI-native web & business analytics

Your numbers, explained.

Reveliqo combines edge-native traffic data, browser behaviour, conversions, sales and revenue — then explains what changed, why it matters and what deserves your attention.

Start free See how it works

Real people separated from bots
AI answers backed by exact data
Traffic connected to revenue

Demo data

Today

People: 2,842; +14%
Conversions: 94; +21%
Revenue: €18,420; +17%

Three things worth knowing

1Organic traffic is growingContext
Most of the increase arrived through two product guides, but their trial conversion stayed below the site average — so the extra visits have not yet turned into proportional signups.
2AI referrals carry a disproportionate share of new revenueWorking
AI assistants delivered 2.8% of human visits and 7.4% of new subscription revenue. The gap between those two shares is the finding.
3Mobile pricing conversion fellCheck this
The decline begins shortly after yesterday's deployment and is concentrated on Safari. Causation has not been established.

Show me why Ask Reveliqo

The idea

You run the business. Reveliqo reads the analytics.

Traditional analytics hands you reports and leaves the interpretation to you. Reveliqo starts from the questions that actually get asked: what changed, why, which traffic converted, what made money, and what to look at next.

Instead of 42 reports

You get the three things worth knowing.

The brief names what moved, what is outside its normal range and what has commercial consequences. The reports are still there, underneath, for when you want them.

Instead of building segments by hand

You ask why signups dropped.

The question becomes an analysis plan across approved metrics and dimensions. You read the result, not the query builder.

Instead of pageviews in isolation

You see which pages are credited with revenue.

Conversions arrive as server events, revenue from the systems that bill and recognise it, so a page's value is a number finance would also recognise.

Ask AI

Ask the question you actually have.

Reveliqo turns the question into an analysis plan, queries governed metrics and explains the result. It compares the right periods and segments because it was told which ones exist — not because it guessed from the wording.

Ask AI

Why are conversions down this week?
Which traffic sources bring our best customers?
What changed after yesterday's deployment?
Which pages get traffic but fail to convert?
Is our paid traffic profitable?
Are AI assistants sending us customers?
Why was traffic unusually high last night?
What content generates the most revenue?

Evidence

Every answer can show its work.

The analytics engine calculates the numbers. The AI plans the analysis and explains what came back. Open the evidence behind any answer and you get the exact metric, segment, period and comparison it used — and a plain statement of what it could not establish.

How evidence works

Demo data

Evidence

Mobile pricing conversion fell 27%.

Why Reveliqo says that

Traffic volume remained within its normal range. The decline is concentrated on iPhone Safari and begins 18 minutes after deployment #842.

Before deployment: 4.1%
After deployment: 3.0%
Visits analysed: 3,481
Difference: −26.8%

Metric: conversion_rate
Segment: device_class = mobile · browser_family = Safari · page = /pricing
Period: Yesterday 14:00 – today 09:00, compared with the preceding seven days

Strong correlation with deployment #842. Causation has not been proven — a controlled comparison would be needed for that.

Why you can trust the number

The AI never does the arithmetic.

A model asked to compute a conversion rate from raw event text will produce a plausible one. Reveliqo does not put it in that position. A semantic metrics layer holds the canonical definitions, the query service computes against them, and the model is restricted to calling approved operations and explaining what they returned.

Read the architecture

Demo data

How an answer is produced

1Your question
2AI analysis planner
3Semantic metrics layer
4Analytics query service
5Deterministic result
6AI explanation

Steps 3 and 4 compute every number. The model plans which question to ask and explains what came back — it never does the arithmetic, and it cannot reach data the asking user is not entitled to see.

Metrics

people
visits
pageviews
conversion_rate
revenue
revenue_per_visit
average_order_value
trial_to_paid

Dimensions

site
page
landing_page
channel
source
campaign
country
device

Collection

Your analytics start before JavaScript loads.

For sites proxied through the supported edge, Reveliqo sees traffic where it actually arrives. Core page and request analytics stay visible even when a browser blocks client-side tracking, because the request reached the infrastructure regardless.

This is about proxied HTTP traffic, not DNS. A name server that resolves a hostname never sees the page, the referrer or the status code, and no analytics product can read what was not sent to it.

Edge collection

Demo data

Edge collection

Visitor request
Arrives at the global edge
Edge analytics
Path, source, campaign, status, latency, geography
Traffic quality
Humans, crawlers, bots and security traffic separated
Durable spool
Written aside from the request path
Your origin
Answers the request, unaffected

No analytics call enters the live request path. An outage in the analytics pipeline slows nothing your visitors touch.

Two sources, on purpose

The edge sees the request. Smart Beacon sees the experience.

Neither one is the whole picture, and a product that pretends otherwise is hiding something. The edge cannot see a single-page navigation; a browser script cannot see a request it was blocked from reporting.

The edge sees the request

Page and document requests
Source and referrer
Campaign parameters
HTTP status and errors
Origin latency
Country and device class
Traffic quality classification

Smart Beacon sees the experience

SPA and soft navigation
Engagement and time on page
Core Web Vitals
Clicks and custom events
Form starts and submits
Client-side conversions
Content asset exposure

Smart Beacon

Traffic quality

Not every request is a customer.

Reveliqo separates real people from verified search crawlers, AI crawlers, other automation and security traffic — so a bot spike does not masquerade as business growth, and a quiet week is not hidden behind one.

An AI crawler reading your documentation and a person arriving from an AI assistant are different events with opposite commercial meanings. Most analytics tools file both under “referral” or neither.

Traffic Quality

Demo data

Traffic quality

Human visitsCounted as people: 68%
Search crawlersVerified: 12%
AI crawlersReading documentation: 7%
Other botsClassified automation: 6%
Suspicious automationChallenged: 4%
Blocked attacksNever reached origin: 3%

Total requests rose 42% overnight while human traffic was unchanged. The increase came almost entirely from verified AI crawlers reading the documentation. Without this separation it reads as business growth.

Acquisition

See where valuable people come from.

Compare channels and campaigns by conversion, sales, revenue and customer value rather than by clicks. The default sort is business value, because the channel with the most traffic is regularly not the one paying for the team.

Acquisition

Demo data

Acquisition · sorted by revenue

Channel	Visits	CVR	Revenue	Per visit
Organic Search	11,204	3.4%	€41,900	€3.74
Paid Search	6,431	4.1%	€27,100	€4.21
AI AssistantsBest per visit	812	6.2%	€18,640	€22.96
Direct	5,908	2.7%	€14,380	€2.43
Referrals	2,140	2.1%	€5,220	€2.44
Social	3,776	0.9%	€2,910	€0.77

AI Assistants sent the fewest visits of any channel except referrals, and the most revenue per visit of any channel at all. Sorting this table by traffic volume hides that entirely.

Content

See which pages are credited with customers, not only pageviews.

Rank content by what it contributed rather than by how many people saw it — then, with a content platform connected, go below the URL to the individual headline, CTA or claim that did the work.

Demo data

Content · by revenue per visitor

Page	People	CVR	Revenue	Per visitor
/pricing	4,812	5.8%	€42,000	€8.73
/guides/consent-mode	6,210	3.2%	€36,000	€5.80
/blog/privacy-first-analytics	9,421	0.7%	€12,000	€1.27

The blog post attracts nearly twice the audience of the pricing page and produces roughly a seventh of the revenue per visitor. Both facts are useful; only one of them survives a pageview ranking.

Demo data

Content asset

cnt_headline_82af

“Know what your website actually loads.”

Shown on: 18,421 visits
Conversion: 5.7%
Revenue: €82,410
Per 1,000 shown: €4,474

The same headline appears on four pages. Measured as a URL it is four weak rows; measured as an asset it is one clear result.

Measure the message

Journeys

See the paths that actually lead somewhere.

Follow the route from source to outcome — and run it backwards from a conversion to find what preceded it. Unusual drop-offs and unusually valuable paths are surfaced rather than left for you to notice.

User journeys

Demo data

Journeys

Organic SearchGuidePricingTrialPaid
The most common converting path, and the slowest.
AI referralFeature pageTrialPaid
One step shorter and the highest revenue per visit.
DirectHomepagePricingExit
Where the largest single drop-off happens.

Conversions

Tell Reveliqo what success means.

Onboarding asks one question — what does this website need to achieve? — and the product organises itself around the answer rather than around a default report set.

Generate leads
Start trials
Sell products
Start subscriptions
Book appointments
Take registrations
Drive calls
Grow readership
A custom outcome

Conversions

Revenue & sales

Pageviews stop where your business starts. Reveliqo keeps going.

Connect sales and finance data from your finance and accounting systems, Stripe, Shopify or your own event API, and a channel stops being a traffic number. It becomes customers, invoices, recurring value and — where the finance system supplies the measure — margin.

In the demonstration account, Organic Search brought fewer leads than Paid Search and carried more realised revenue. The gap is accounted for by plan mix: its leads are credited with higher-value annual plans in the revenue the finance system reports.

Revenue & Sales

Demo data

From visit to recognised revenue

VisitEdge and beaconReveliqo
Lead / Trial / OrderServer eventYour application
CustomerAccount createdFinance
Invoice / SubscriptionBilled and collectedFinance
RevenueRecognisedAccounting
MarginContributionAccounting

Reveliqo does not keep its own ledger. The last two steps are read from the systems that own them, so a revenue figure here reconciles against the one finance already trusts.

Sales and commercial outcomes

Finance system

Customers and accounts
Sale and order events
Invoice and payment outcomes
Subscription and customer value
Refunds and credits

Read the integration

Cost, margin and recognised revenue

Accounting system

Booked and recognised revenue
Cost and margin measures
Business-period numbers
Profitability classification
Cash and collection outcomes

Read the integration

Reveliqo does not duplicate either one. It reads only the outcome fields an analysis needs — customers, invoices, recognised revenue, margin — and leaves the definitions with the system that owns them.

Performance

When conversion changes, know whether the site changed too.

Edge latency, HTTP errors and real-user performance sit beside conversion and revenue movement — and next to the release that went out, so the first question after a drop has somewhere to start.

Demo data

Technical change vs business change

Measure	Before	After
Checkout revenue · mobile Safari	—	−11%
INP p75 · mobile Safari	190 ms	380 ms
Visits · mobile Safari	1,742	1,739flat
Origin latency p95	212 ms	218 msflat

Traffic held steady while responsiveness and revenue both moved. That pairing is what makes a technical explanation worth investigating ahead of a marketing one.

Demo data

Deployment impact

14:02ReleaseDeployment #842 released to production
14:20SignalPricing conversion begins falling on mobile
14:32SignalSafari INP rises from 190 ms to 380 ms
15:10AnalysisAnomaly opened and decomposed automatically

A release and a movement that follows it are a sequence, not a proof. Reveliqo reports the correlation and names what would be needed to go further.

Deployment impact

Live

See what is happening now without drowning in a firehose.

People on the site, what they are reading, where they came from, what just converted and whether anything is wrong — summarised in a sentence. A counter that only goes up is not information.

Live view

Demo data

Live

148people on the site now

Top page: /guides/consent-mode
Top channel: Organic Search
Last conversion: Trial started · 40 seconds ago
Last revenue event: €149 · subscription.started
Human share: 71%
Open incidents: None open

Steady afternoon traffic, weighted to documentation. Conversion is tracking its usual rate for this hour.

How it fits together

Four data layers. One explanation.

Each layer answers something the others cannot, and the product's whole job is to reconcile them into a single account of what happened.

Collect

Requests at the edge, behaviour in the browser, conversions from your server and commercial outcomes from the systems that own them.

Classify

Separate people from verified search crawlers, AI crawlers, other automation and security traffic before anything is counted as a visit.

Resolve

Every metric has one canonical definition in the semantic layer, so the brief, the funnel, the API and the scheduled email cannot disagree.

Investigate

Decompose what moved across channel, campaign, page, country, device, browser, performance and release, and rank the strongest explanations.

Explain

State what changed, what it is worth and what was ruled out — with the metric, segment and period it used attached to every sentence.

Connect

Follow the outcome through to the invoice, the recurring value and, where the finance system supplies it, the margin.

Nine modules, one engine

The platform, in full.

Every module reads the same four layers, which is why Content & Journeys can find a claim the traffic data contradicts and Performance can explain a revenue movement.

AI Overview

Opens with a written briefing: what changed, why it matters, what to check.

5 capabilities

Ask AI

Plain questions become governed metric queries. Every answer arrives with the definition behind it.

5 capabilities

Acquisition

Channels, campaigns, referrers and AI assistants, sorted by revenue rather than traffic volume.

6 capabilities

Content & Journeys

Pages, landing pages, paths and content assets, ranked by the outcomes recorded after them.

6 capabilities

Conversions

Goals, funnels, forms, server events, attribution and journeys, organised around your chosen outcomes.

6 capabilities

Revenue & Sales

What the traffic was worth, in the figures your finance systems already hold.

7 capabilities

Performance

Core Web Vitals, origin latency and errors, read against conversions and revenue.

6 capabilities

Traffic Quality

Classify every request as human, crawler, AI agent, bot or attack before it is counted.

6 capabilities

Live

Active people, conversions, revenue, traffic quality and incidents — the present, with business context.

5 capabilities

Solutions

Who this is for.

Small business

Your website, explained in plain language.

SaaS

From first visit to recurring revenue.

Ecommerce

Orders, margin and the traffic behind them.

Marketing teams

Reporting that arrives already interpreted.

Content & SEO

Rank the page by the revenue after it.

Agencies

One account, every client, explained.

Developers

Latency and errors, next to revenue.

Multi-brand groups

Every brand on one definition.

Integrations

Collection, commerce and the numbers finance trusts.

Two sources of collection, four sources of commercial truth, and an event API for everything a packaged integration does not cover.

Privacy by architecture

Analytics does not require a profile of the person.

Reveliqo runs in the collection mode you choose — no persistent identifier at all, a short-lived first-party visit key, or a pseudonymous account key your own application supplies. No fingerprinting is required for any of it.

What your jurisdiction requires is a decision for you and your advisers, and it varies by region and configuration. Reveliqo provides the technical modes and, with a consent platform connected, follows the consent state you have already configured there rather than running a second policy engine of its own.

Privacy modes Security

Questions

The ones worth answering up front.

Reveliqo is an AI-native web and business analytics platform. It combines four layers: request analytics from the edge, optional browser signals from Smart Beacon, server-side business events such as trials and orders, and commercial data from your finance and accounting systems. The analytics engine computes the numbers; the AI plans the analysis and explains what changed, where it changed and what deserves attention.

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.

Start free See how it works

Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo