Anonview user
documentation
Simple, non-technical guidance to launch Anonview, answer common questions, and turn signals into action.
From installation to insights
Three simple steps to reach your first actionable insights in under 10 minutes.
- 1Create a site, install the snippet, and verify Live.
- 2Review Overview, then Pages to isolate strong sources.
- 3Ask Oracle your key questions and plan the next move.
Launch in 10 minutes
Activate Anonview with a light lift. Connect a site, install the snippet, then verify signals in real time.
From the dashboard, add a site and give it a clear name. This creates a dedicated space for signals.
Copy the script from Installation and place it before the closing body tag.
Open Live to confirm events and traffic quality without any sensitive data.
Pick one or two outcomes to improve this week so the team stays focused.
Know what a signal means
Signals are privacy-safe indicators that tell you what is working and where attention drops.
Begin with page views and one conversion point. Expand only after your first decisions land.
Organize sites and domains
A clean site structure keeps signals clear, comparisons fair, and stakeholders aligned.
Create a separate site for each product, brand, or region that needs its own story.
Add the primary domain so signals remain tied to the right property.
Use a shared naming pattern so teams can scan dashboards quickly.
If you run multiple brands, keep one site per brand and compare results in a shared weekly review.
Define conversions that matter
A clear conversion keeps everyone aligned. Use one primary outcome and a short list of supporting signals.
Choose the single action that defines success for your team.
Use the same name across pages and teams so results stay comparable.
Trigger the action once and confirm it appears before sharing the dashboard.
Understand the essential dashboards
The UI answers three questions: what is happening, why it matters, and what to do next.
Start with Overview, then move to Pages and Referrers to isolate segments impacting conversion.
Read trends with the right window
Your time range shapes the story. Align it with campaigns, releases, and retention limits.
Use 24h for anomalies, 7-28 days for trends, and monthly views for strategy.
Look at two windows side by side to confirm a change is real.
The range picker shows what is available so decisions stay grounded.
Start with a focused scenario
Pick one clear use case first. It keeps teams aligned and makes the value obvious.
Watch conversion and friction before and after a release.
Verify referrers, landing pages, and intent to see if spend is paying off.
Track drop-offs and fix the step with the highest impact.
Start with a single landing page and improve one outcome before scaling.
Separate humans from noise
Traffic Quality makes sure decisions are grounded in real behavior, not automation or noise.
Pause spend on the source, review referrers, and confirm the behavior inside Live.
Stay ahead with alerts
Alerts protect your time by highlighting what needs attention before it becomes a problem.
Use the recent average to define what normal looks like.
Pick a signal that truly matters, such as conversion or quality shifts.
Use Oracle to confirm the cause and decide the next move.
Turn signals into actions
Oracle synthesizes signals and proposes the next best move. Ask in plain language and get clear recommendations.
Use natural language to describe the outcome you want to improve.
Oracle links the insight to the dashboard that explains it.
Focus on a single change so impact stays measurable.
A weekly rhythm for confident decisions
A short routine keeps teams aligned and avoids reactive decision making.
Spend five minutes on Overview and Live to spot anomalies early.
Pick one strong source and one weak source to investigate together.
Confirm the one outcome that will matter most next month.
Use this cadence for launches, pricing updates, or major landing page changes so teams stay focused.
Checklist for a confident launch
Use this checklist before sharing results broadly. It keeps data, teams, and expectations aligned.
Open Live on the production site and verify signals appear.
Trigger the main outcome once and confirm it is tracked.
Add a baseline alert so drops are visible within hours.
Document the first insight and the next action in one paragraph.
Trust, compliance, sovereignty
Anonview protects users by design: no personal data, daily session rotation, and observability without payloads.
Privacy by design means fewer risks and faster approvals for new initiatives.
Work as one team
Invite the right people, share clear views, and keep decisions aligned.
Shared language for every team
A short glossary keeps decisions consistent and removes ambiguity.
Use these terms in status updates so teams stay aligned.
When something looks off
Most issues have a quick fix. Use this checklist before escalating.
Confirm the snippet is installed on the right site and verify it appears in Live.
Review recent releases, check referrers, and confirm traffic quality.
Look for new campaigns or automated sources. Quality will flag automation.
Frequently Asked Questions
Quick answers to common questions from marketing and product teams.
How long until I see data?
Usually a few minutes after installing the snippet. The Live page confirms signals immediately.
Do we need a cookie banner?
No. Anonview runs without third-party cookies or invasive tracking. No extra consent is required.
What does a signal represent?
A signal is a privacy-safe indicator of behavior. It helps you understand interest without personal data.
What should our first conversion be?
Choose the single action that reflects success, such as a signup, request, or purchase.
How should we split sites?
Create one site per product, brand, or region so each dashboard tells a clear story.
Can I compare time ranges?
Yes. Use the range selector in the dashboard to compare periods and spot shifts.
Which use case should we start with?
Pick the one outcome that matters most this quarter, then focus on one funnel or page.
Why do numbers change when I switch the time range?
Different windows highlight different behavior. Align the range with the question you are asking.
How long is data retained?
Retention depends on your plan. The range selector reflects what is available to analyze.
What is a good go-live checklist?
Verify Live, confirm the main conversion, set one alert, and share a short summary.
Where do I confirm the snippet works?
Open Live. If events appear there, the installation is successful.
How do we share insights with stakeholders?
Use a short summary, link the relevant dashboard, and list one clear action.
How is traffic quality handled?
Quality insights highlight automation and anomalies so you can trust the decision.
Is any personal data stored?
No. Anonview avoids IPs, emails, user agents, and input values by design.
How do teams collaborate?
Use roles, shared views, and a clear cadence so everyone acts on the same story.
How do we keep teams aligned on terms?
Use the glossary in this documentation as the shared language.
Can I export data to BI tools?
Yes. If enabled, the BI connector is available from Settings.
How do I set alerts?
Start with a baseline, choose one trigger, and assign clear ownership for follow up.
Where can I get fast help?
Reach support from the documentation or the Contact page. Premium plans get priority responses.