Concepts

The four data layers

Everything in the product is a view over one or more of these. Which layer a number came from determines how much weight it carries.

Edge Intelligence

Traffic, pages, referrers, campaigns, geography, status codes, latency and traffic quality, collected from proxied HTTP traffic at the global edge. Complete for requests that reached it, and independent of what the browser then does.

Smart Beacon

Browser-only signals: single-page navigation, engagement, Core Web Vitals, clicks, forms, client-side events and content-asset exposure. Optional, and the only way to see inside the page.

Business Events

Server-side conversions sent by your application: leads, trials, accounts, orders, subscriptions, upgrades, cancellations and refunds. Authoritative in a way a browser event cannot be.

Commercial Data

Sales, invoices, recurring revenue, customer value and margin from your finance, accounting and connected commerce systems. Reveliqo reads these; it does not compute them.

The core objects

Site

A property with its domains, business type, primary goal, currency, timezone and privacy mode. Most configuration hangs off a site rather than an account, because one organization frequently runs sites with different goals.

Person

A human visit, after crawlers, bots and security traffic are excluded. Whether people are counted across visits depends entirely on the collection mode in force.

Goal

What this site needs to achieve, chosen during onboarding. A page goal, an event goal, a server goal, a revenue goal or an account-lifecycle goal — and the product organises itself around the answer.

Business event

A named server-side outcome with a pseudonymous customer key, a timestamp, a value, a currency and properties, carrying an idempotency key so a retry cannot double-count it.

Commercial fact

A record from a connected finance or commerce system: an invoice, a payment, a subscription change, a refund. Reveliqo stores the projection it needs for analysis, not the source-of-truth record.

Insight

A detected change with a type, a severity, a summary, the metric evidence behind it, the segments examined, a confidence and a status. Produced continuously rather than on request.

Traffic classification

The default business view counts only the first of these. The others remain visible when you want them.

• Human visits — counted as people
• Verified search crawlers — identified and reported separately
• AI crawlers — AI agents reading your content, with the areas they read
• Other bots — classified automation
• Suspicious automation — challenged or rate-limited at the edge
• Blocked attacks — summarised for analytics, investigated in the edge console

Which layer answers which question

When two layers disagree, the more authoritative one wins — and the product says which it used.

How an answer is produced

The order matters, and it is the reason a figure in an explanation matches the figure in the report.

• The question becomes an analysis plan across approved metrics and dimensions
• The semantic metrics layer resolves the canonical definition of each metric
• The analytics query service computes against the store
• A deterministic result comes back with its sample sizes
• The AI explains what returned, names what it ruled out, and states what it could not establish

Where to go next