Pre-launch checklist

Seven things to confirm before you rely on this data for a real decision.

1. 1Install verified: you've generated your own visit and seen it appear
2. 2Your key conversion events are starred
3. 3The funnel that matters most to you is built
4. 4Your own and your team's traffic is excluded or filtered out
5. 5Your team is invited
6. 6You know your plan's retention window
7. 7You've checked usage against your quota

#Install verified

Walk through Verify your install: a visit that shows up in realtime is the fastest confirmation the script is live, reaching the right site id, and not being blocked by a CSP or ad blocker.

#Star your conversions

From the Events page, mark the events that represent real outcomes (signup completed, purchase, whatever matters for your product) as conversions. This is what makes an event count toward conversion-rate reporting anywhere in the product, not just inside a specific funnel.

#Build the funnel that matters

One funnel covering your primary flow, with a conversion window that matches how long that flow actually takes. See designing funnels that tell you something.

#Exclude your own traffic

Add any internal-only paths to excluded paths, and expect to use filters at view time for anything excluded paths can't isolate. See accuracy and excluding traffic.

#Invite your team

Workspace members are invited from Settings and hold one of three roles: owner, admin, or member. Inviting someone requires admin or owner access. There's no separate limit on how many people you can invite; the plan limits are on sites and monthly pageviews, not seats.

#Understand your retention window

A daily cleanup job prunes sessions, the per-event mirror, replay data, and daily rollups older than your plan's window. This is what keeps the underlying database bounded, and it means historical detail genuinely disappears past the window: it isn't just hidden from the UI. Plan exports accordingly if you need data past your plan's retention.

#Check your usage

Settings shows pageviews consumed against your plan's monthly allowance. Every current plan meters overage at $0.05 per 1,000 rather than dropping data, so a traffic spike costs money rather than losing events. Custom events, goals, revenue, scroll depth, engaged time and session replay do not consume quota at all, so the only lever on this number is pageviews. See what counts toward your quota.