Three collection modes, and what each one buys you

The three modes

Minimal

No persistent visitor identifier at all. Traffic, pages, referrers, campaigns, country, device class, performance, errors and traffic quality all work. This is a genuinely useful analytics product, not a degraded one — most questions about acquisition and content are answerable here.

Visit

Adds a short-lived first-party visit key where you configure it and your policy permits. This is what makes journeys, funnels and visit-level conversion possible, because linking two pageviews into one path requires knowing they were the same visit.

Customer

Your application supplies a pseudonymous account or customer key. Adds trial-to-paid, account lifecycle, customer value, revenue relationships and cohort retention — the questions that need to span weeks rather than minutes.

What each mode makes possible

The honest version of the trade-off, rather than a feature matrix designed to push you upward.

Discarded by default, in every mode

• Request bodies, authentication headers and cookies
• Query parameters outside the campaign allowlist
• Identifiers inside paths, replaced by route templates before storage
• Raw IP addresses, which are not retained in analytics storage

No fingerprinting, in any mode

Fingerprinting identifies a device from the combination of its characteristics rather than from something stored — it is designed to survive deletion, which is exactly why it is treated as an access technology in its own right.

Reveliqo does not require it for any part of the core product. Where a mode needs to link two events, it uses a first-party key that you configured and a visitor can clear, not an inferred identity they cannot.

With a consent platform connected

One consent policy, in one place. Reveliqo reads it rather than running a second engine that could disagree.

• The consent platform supplies the configured privacy and consent state for a visitor
• Reveliqo applies the collection mode that state permits, per region and per configuration
• Collection behaviour can therefore differ between visitors on the same site, which is the point
• Reveliqo does not implement its own consent policy logic and does not override what the consent platform densus was configured to do

Why no cross-site profile is needed

Reveliqo answers questions about a site's own visitors, content and revenue. None of that requires knowing what a person did on somebody else's website, so nothing in the architecture builds or trades that profile.

This is an architectural statement about what the product does, not a claim about your obligations. What your jurisdiction requires depends on your configuration, your region and your own processing — and that assessment remains yours.