One consent decision, enforced where the data enters.
Two systems with their own idea of consent will eventually disagree, and the disagreement surfaces in an audit rather than in a dashboard. The consent platform is the policy engine. Reveliqo reads the configured state and applies the matching collection mode — Minimal, Visit or Customer — at ingestion.
In short: Your consent platform holds the configured privacy and consent state; Reveliqo reads it and enforces the matching collection mode at ingestion, rather than running a second, independent consent policy of its own.
What it is
A consent platform discovers the cookies and tracking technologies a site loads, collects visitor choices, controls what is allowed to run, and continuously verifies that the implementation matches the policy the site publishes.
What this lets you ask
- “Which identity mode is in force for visitors in each region right now?”
- “How much of our traffic is measured in Minimal mode, and what does that limit?”
- “Did the consent configuration change on the day our measured conversion rate moved?”
What Reveliqo receives
- The configured privacy state per site and region, including which categories the customer has decided require a choice.
- Visitor consent signals as they change, so a collection mode can tighten or loosen within a visit.
- The mapping from consent category to Reveliqo identity mode: Minimal, Visit or Customer.
- Verification results from consent scans, so drift between published policy and actual behaviour is visible in both products.
How it is connected
- Authorise your consent platform in the shared workspace and select the sites whose state Reveliqo follows.
- Map each consent category to an identity mode. Minimal is the default, and a mode only loosens where the configuration says so.
- Decide the mode for visitors who have not yet chosen, and for regions where your configuration does not require a choice.
- Apply. Ingestion enforces the mode from that point — nothing is stored first and filtered afterwards.
How you verify it
- Decline in the consent banner, browse, then inspect the stored events. No persistent visitor identifier should exist for that visit.
- Compare the identity modes in use against the consent configuration per region. Both views are built from the same state.
- Run a consent scan and confirm Reveliqo's collection appears in it exactly as your policy describes.
Limits worth knowing
- What a region or configuration requires is a legal question this connection does not answer. Collection follows the configuration you choose, and choosing one that fits your legal position is your call.
- Reveliqo enforces consent state, it does not decide it. If the consent configuration is wrong, Reveliqo enforces something wrong faithfully.
- Minimal mode changes what can be answered. Without a persistent identifier, returning-visitor and multi-visit journey questions are limited by design, and the product says so instead of estimating.
Other integrations
Connect the rest of the stack
Finance system
Customers, invoices, payments and subscriptions — revenue that arrived, not orders that were placed.
Accounting system
Cost, margin and recognised revenue — so a channel is judged on profit, not turnover.
Content platform
Stable identifiers for headlines, CTAs and claims — measure the message, not the URL.
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