Environments
Understand Development and Production environments in Hawcx
Overview
Every Hawcx project runs in one of two environments. Environments isolate your test traffic from real users and control how Config IDs are provisioned.
Development
The default environment for new projects. Use it for building, testing, and staging.
- Config IDs are provisioned instantly, and any Admin or Developer can generate them
- No approval workflow required
- Ideal for local development, CI/CD, and QA
Production
For live, user-facing applications. To set up a production environment, contact the Hawcx team — they'll provision it for your project.
- Production environments are provisioned by Hawcx
- Once your production environment is enabled, you generate and manage production Config IDs the same way as in Development
Switching Environments
Use the Environment Switcher in the console top bar to toggle between Development and Production. The switcher applies to dashboard analytics, Config ID lists, and project views.
Best Practices
| Practice | Why |
|---|---|
| Use Development for all testing | Keeps production metrics clean |
| Use separate Config IDs per platform | Easier to revoke and track usage |
| Rotate Config IDs when team members leave | Prevents unauthorized access |
| Arrange production setup before launch | Production is provisioned by the Hawcx team, so reach out ahead of go-live |
Last updated on