Discover
Start with a site audit and inspect the implementation, technologies, privacy signals and important journeys.
Start with an audit →How Analytics Capture works
How Analytics Capture turns evidence into measurement.
Analytics Capture turns real product behaviour into trusted measurement. This walkthrough explains what happens from first discovery through governed activation, without asking you to sign in just to understand the product.
Product walkthrough
One path from evidence to action.
Each stage has a clear purpose. You can understand the outcome before touching implementation settings.
Prove
Set up the project-specific capture tag, verify it, and record real journeys when static evidence is not enough.
Set up capture →Govern
Turn observations into understandable measurement definitions, then apply privacy and destination rules before release.
See measurement planning →Activate
Publish approved definitions to destinations and keep an auditable path back to the evidence that justified them.
Connect destinations →Why the evidence matters
See the gap between what you planned and what users actually do.
Example journey
Product viewed ✓→Apply clicked ✓→Form started ✓→Form error missing→Complete ✓
Instead of guessing which event is missing, the product shows the journey, the evidence and the affected measurement definition together.
Governed recommendation
ObservedUsers encounter a form error before completing the flow.
Canonical event
form_error with a privacy-safe schema.DecisionReview and approve the event before production delivery.
ActivationRoute the approved meaning to selected analytics and warehouse destinations.
Built for controlled change
Automation finds evidence. People control production.
Privacy first
Sensitive values are excluded before evidence becomes measurement. Consent and identity decisions remain explicit.
One governed meaning
Keep the business definition separate from vendor-specific delivery details, so destinations do not become separate sources of truth.
Release deliberately
Review, approve and publish changes as a controlled lifecycle rather than silently changing production tracking.
What happens after sign-in
Authentication is for setup, not for explaining the product.
The public site is where people learn. Once you create a workspace, the private experience becomes focused: choose a workspace, install and prove capture, then work through the measurement lifecycle.
First-session path
1 · WorkspaceCreate or select the project you want to measure.
2 · InstallGenerate the project-specific capture setup and add it to your site.
3 · VerifyConfirm real browser evidence is arriving safely.
4 · ContinueReturn to Discover, Journeys, Test and Destinations with evidence in hand.
Everything stays connected
Workspace navigation uses the same destinations at every supported screen size. Desktop uses the full menu; tablet and mobile use one compact menu pattern. Links keep their names and active state, so the interface does not become a different product on a smaller screen.
Questions
Understand it before you sign up.
Do I need an account to understand the product?
No. This walkthrough and the public audit explain the product before authentication.
What does the workspace do?
It is the operational control plane: evidence, measurement definitions, privacy decisions, destinations and releases live there.
Does Analytics Capture silently change production tracking?
No. Production delivery is an explicit governed step with review and approval.
Why is there a separate public walkthrough?
Operational navigation should answer what to do next. Public product information answers why the product works this way. Keeping them separate makes both experiences easier to understand.
Ready to see your own evidence?
Start with a free website audit. Create a workspace when you want to save findings and prove runtime behaviour.
Understand evidence before activating analytics
A tracking inventory, a connected reporting source and a live event destination answer different questions. Analytics Capture keeps those states separate so a detected tag or saved configuration is not mistaken for verified measurement.
Canonical event meanings can be reviewed before being transformed for a destination. Consent integration is optional; when enforcement is enabled, an explicit visitor denial remains authoritative. Each integration describes its actual connection and delivery method.