Frequently asked questions.

DataVisitors combines website analytics and product analytics. Website reports explain where visitors come from and which pages they use. Product reports examine event completion and repeat use through goals, funnels, retention cohorts, segments, and journeys.

For example, use web analytics to compare signup sources. Use product analytics to examine the steps after signup. You define the product events that explain activation.

The map demo is an interactive product demonstration with fictional records. Explore country activity and filters before you create an account. Its locations are coarse, not precise visitor positions. The homepage analysis is an illustration. Neither is a claim about customer activity.

No. DataVisitors provides session activity and optional heatmaps, but not session replay or visitor video recordings. A session activity view lists collected events. A heatmap combines click or scroll activity on a page. Neither replays a visitor's screen.

No. Reports describe collected activity. Attribution models assign credit according to their definition. Findings and suggested actions need your review; they do not establish causation.

No. Aggregate analytics is the starting point. People is off by default. Identified traits require explicit collection choices and the appropriate consent. Your privacy settings determine which activity can connect across visits. Read the privacy and access controls before you enable individual analysis.

The browser tracker starts stateless. Your privacy regime and consent determine when it can use device storage. Cross-day behavior analysis needs an appropriate way to connect visits. Read Cookies for the distinction between the marketing site and your installed tracker.

Yes. A revocable public share link provides aggregate reports without an account. Individual profiles do not appear on that surface. Review the report before you share its link. Revoke the link when you no longer want it available. Read teams and sharing for the access choices.

Use the browser tracker for websites and single-page applications. Use the HTTP API for server events and aggregate queries. Client libraries are not currently published on package registries. The integration directory lists the supported public connection paths.

Supported CSV imports include Plausible, DataVisitors, and generic aggregate history. Imports do not recreate original sessions or individual retention behavior. Read the import guide.

Plans differ by event volume, retention, seats, projects, and feature access. Pricing explains the factors. Your organization's Plans page supplies the current offers.