Docs

Verify before launch

Configuration presence is not a successful customer journey.

1. Account

Open a protected route in a private browser: it must request sign-in in live mode. Sign in, refresh and confirm the same persisted account.

2. Payment and contact

Submit a contact request and confirm the row. Complete a Stripe test checkout, confirm the webhook persisted an active subscription, replay the event, then cancel and verify access expires as expected. A checkout success redirect alone never grants access.

3. Analytics

Verify no TideStat SDK or collection requests before consent. Allow analytics, visit a page and check for a fresh pageview in the signed-in TideStat account. Revoke consent and confirm collection stops. A browser pageview does not verify revenue.