Skip to content
Conversions

Measure what mattered

The conversion is the middle of the story, not the end.

Send a pseudonymous customer or account key with your server events and Reveliqo joins what happened before the conversion to what happened after it, under the collection mode configured for the workspace. The trial that upgraded and the trial that cancelled stop looking identical in the report.

Customer Journeys

  • Pseudonymous customer and account keys
  • Pre- and post-conversion activity joined
  • Journeys through upgrade and cancellation
  • Collection governed by workspace privacy mode

How it helps

What Customer Journeys gives you

1

The key comes from you

Reveliqo does not construct an identity. Joining runs on a pseudonymous key your system already holds — a customer id, an account id, a hashed reference — sent with your server events. No key, no join.

2

What happens after the signup

A signup is not a customer. Journeys continue through upgrade, renewal, downgrade and cancellation, so a source whose trials cancel in week three stops looking like the best source in the table.

3

Privacy mode decides what joins

Journeys run under the collection mode configured for the workspace, and your consent platform supplies the consent state governing what may be connected. What is collected, and for how long, varies by region and configuration — and the configuration is yours.

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