A cookieless analytics implementation checklist
Review browser storage, event payloads, server processing, identity, and optional replay before installing analytics. A script that sets no cookies still needs a deliberate collection contract.
Define the measurement contract
Start with the decisions your team wants to make. List pageviews and named events, the owner of each event, permitted property names and types, and the reports that use them. Avoid collecting form contents just because a DOM listener could capture them.
Use stable event names and scalar properties. Document whether revenue is an explicit numeric property or a reconciled payment amount. Write down whether a conversion rate uses people, daily IDs, sessions, or events.
Inspect browser behavior
Open developer tools on a test site. Record which cookies and storage entries exist before and after the tracker loads. Separate application login cookies from analytics identity storage. Inspect the outgoing requests to confirm that full URL queries and fragments are removed where intended.
- Verify one tracker instance and one expected pageview per navigation.
- Keep private read keys, database credentials, and AI provider keys out of browser bundles.
- Send a custom event and inspect property values.
- Navigate within the SPA and verify the router callback.
- Check logout and a fresh authenticated page load.
Inspect the collector and storage
Verify that the public write key resolves to the intended project and site, allowed origins are correct, and proxy headers follow your trust configuration. Trace the request through queue processing into Tinybird. Confirm that raw IPs are not forwarded with stored events.
Inspect access logs and failure payloads separately; a clean analytics table does not prove that an edge log or dead-letter queue retains no request information. Supabase should contain application state, while events and profile traits belong in Tinybird.
Review optional identity and replay
Explicit identify calls attach your own user ID and traits. Test partial updates, logout, and the displayed profile. Avoid treating a shared anonymous hash as proof that all earlier activity belonged to an account.
Replay needs its own review. Start on a synthetic test page, confirm masked inputs and text, block sensitive elements, and inspect URL attributes. Establish recording budgets and retention before wider rollout. Review your notice and legal obligations for the actual data collected; the word cookieless is not a complete compliance assessment.
Frequently asked questions
What should my tracking plan include?
The event name, business question, trigger, permitted scalar properties, owner, identity rule, and retention or privacy notes.
Can I skip a payload review if there are no cookies?
No. Explicit properties, campaign fields, user IDs, and replay can still contain information you chose to collect.
Where should I test installation?
Use a controlled non-sensitive page and the activity report, then verify router behavior and optional features separately.