The platform
9 modules. 52 capabilities. One explanation.
Reveliqo is not nine tools sharing a login. Every module reads the same four layers — edge traffic, browser behaviour, server-side conversions and commercial outcomes — which is the only reason Performance can explain a revenue movement and Traffic Quality can correct an acquisition report.
- AI Overview
- Ask AI
- Acquisition
- Content & Journeys
- Conversions
- Revenue & Sales
- Performance
- Traffic Quality
- Live
Nine modules
What each one owns.
The split is by question, not by data source — because a question like “did the release cost us money?” needs three sources and belongs in one place.
AI Overview
Opens with a written briefing: what changed, why it matters, what to check.
5 capabilitiesAsk AI
Plain questions become governed metric queries. Every answer arrives with the definition behind it.
5 capabilitiesAcquisition
Channels, campaigns, referrers and AI assistants, sorted by revenue rather than traffic volume.
6 capabilitiesContent & Journeys
Pages, landing pages, paths and content assets, ranked by the outcomes recorded after them.
6 capabilitiesConversions
Goals, funnels, forms, server events, attribution and journeys, organised around your chosen outcomes.
6 capabilitiesRevenue & Sales
What the traffic was worth, in the figures your finance systems already hold.
7 capabilitiesPerformance
Core Web Vitals, origin latency and errors, read against conversions and revenue.
6 capabilitiesTraffic Quality
Classify every request as human, crawler, AI agent, bot or attack before it is counted.
6 capabilitiesLive
Active people, conversions, revenue, traffic quality and incidents — the present, with business context.
5 capabilitiesCollection
Two sources that see different things.
The edge sees every request that reached it, including the ones a browser would never report. Smart Beacon sees what happened inside the page, which the edge cannot observe at all.
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
Underneath the explanations
Governed metrics, not a model guessing.
Every metric on this platform has one canonical definition, and the AI reaches them through approved operations rather than by writing its own queries. That constraint is what makes the explanations checkable — and what stops two screens quietly disagreeing about what a conversion is.
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
Diagram: a question goes to the AI analysis planner, which calls the semantic metrics layer and the analytics query service. Those compute a deterministic result, which the AI then explains. The model never calculates the numbers itself.
The story
Four layers, six steps.
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.
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