Basic visits are estimates
Basic tracking uses a site-specific daily hash derived from transient network and coarse browser information. Raw IP addresses and full user-agent strings are not intended to be persisted in analytics storage. A new daily identity and 30 minutes of inactivity can start a new estimated visit.
Shared networks, browser changes, blockers, and daily resets can affect counts. Visit estimates are not an exact inventory of unique people.
Persistent attribution is optional
The default tracker does not create a persistent browser identifier. Workspace settings enable the attribution capability, while your website’s consent integration decides whether to activate it in each browser.
When appropriate consent has been obtained, call setConsent(true). The optional first-party identifier has a fixed 30-day lifetime. Call setConsent(false) to revoke and remove it. Do not treat the feature setting as a substitute for a visitor’s choice.
// Integrate with your own consent-management flow.
window.visitlift?.setConsent(true);
// When the visitor revokes consent:
window.visitlift?.setConsent(false);Events and conversions
An accepted pageview or custom event consumes one event. Duplicate events, identified bots, excluded visits, and payment webhooks do not. Automated filtering cannot identify every bot or guarantee perfect counts.
A goal counts matching events; a funnel checks ordered steps within a visit. Custom date ranges use your reporting timezone. Do not infer a causal lift from a before/after chart alone.
Retention and deletion
Active accounts retain up to 12 months of analytics. Collection stops after trial expiry or the end of paid service, with analytics retained for 30 additional days before deletion. Workspace deletion is a destructive action and should be reviewed by an owner.
Do not send personal information in paths, events, or UTMs. Configure exclusions for sensitive routes before distributing the tracker. Review the Privacy and Security pages for deployment and data-handling boundaries.