Best Practices
Best practices for using WaitKit in production. Handle duplicate signups (409 Conflict), secure API keys with environment variables, track sources, and use custom metadata effectively.
Duplicate handling
Each email can only be registered once per project. Attempting to sign up the same email again returns a 409 Conflict. This is intentional - the waitlist tracks unique interest.
To update an existing subscriber's name or metadata, edit the entry from the dashboard's Waitlist tab.
API key security
- Store API keys in environment variables, never in source code or version control
- Use separate API keys for development and production environments
- Rotate keys periodically from the API Keys dashboard page
- If a key is compromised, revoke it immediately and generate a new one
- Prefix public environment variables with
NEXT_PUBLIC_(Next.js) or your framework's equivalent
Production checklist
Before going live:
- Called
subscribers.create()from the browser, not a server - Used environment variables for API keys and project slug
- Set a meaningful default
sourceon theWaitKitinstance - Handled
WaitKitErrorin your UI (show user-friendly messages) - Tested the full flow: signup → dashboard → analytics appear
Source tracking
Use the source field to distinguish signup origins. See the Source Tracking guide for the full resolution chain and URL parameter tips.
Metadata
Attach structured data to subscribers with the metadata field. See the Metadata guide for limits and patterns.
Integration
Integrate WaitKit into vanilla JavaScript, React, and Next.js projects. Framework-specific patterns for adding a waitlist signup form with the JavaScript SDK or REST API.
Source Tracking
Track waitlist signup sources with the WaitKit SDK. Learn the source resolution chain (per-call, URL parameters, instance default), common values, and how to measure channel performance.