Erase a visitor's data, and clearer cookieless tracking
Permanently erase one visitor's data for GDPR requests without deleting your whole site, and cookieless-tracking sites now automatically hide per-visitor views since there's no stable identity to show.
A real erase button for visitor data
If one of your website's visitors asks you to delete their data, you no longer need to email support or delete the whole site to do it. Open that visitor's journey page and use "Erase visitor data" — it permanently removes their analytics events, identify() record, manual tags, and any transactions tied to them, across every device they've been recognized on.
This is irreversible, so it asks for confirmation before running, and it's available to any site owner or team member — the same permission level who can already tag and manage that visitor's data today.
Cookieless tracking, made consistent end to end
The cookieless snippet already avoided cookies and browser storage entirely, deriving a visitor id server-side from a hash that rotates roughly every 24 hours. That choice now sticks to the site itself, and the dashboard follows through on it: since a cookieless "visitor" is a same-day hash rather than a person you can recognize again tomorrow, showing it in a Visitors list or a Journey timeline would overstate what's actually being tracked — so those views are hidden automatically for a site declared cookieless, both on the main dashboard and on a direct link to a specific visitor.
Aggregate analytics — visitor counts, breakdowns, goals, and funnels — are unaffected either way.
What shipped
- NewYou can now permanently erase a single visitor's data — their events, identity record, tags, and transactions — right from their journey page. Built for fulfilling a GDPR erasure request from one of your own visitors without deleting your whole site.
- ImprovedCookieless tracking is now a saved setting per site (Settings → Script), not just a snippet you copy. A site marked cookieless automatically hides its Visitors and Journey views, since a cookieless visitor id is a rotating daily hash, not a stable identity to build a profile from.
- ImprovedAdding a new website now explains the cookie-based vs. cookieless trade-off inline, with a link to the GDPR doc, instead of two unlabeled buttons.