Skip to main content
Available on the Corporate plan. This feature is part of woku’s enterprise capabilities. Talk to our sales team.
woku includes a sandbox environment: an isolated space where you can test features and configurations before taking them to production. The sandbox replicates the production configuration, so what you validate there behaves the same when you promote it, but without touching your data or your real customers.
The sandbox environment is available on the Corporate plan. Each company has its own sandbox, isolated from its production environment.

​
What the sandbox isolates

The sandbox is a parallel environment that does not share state with production. The following remain separate: Nothing you do in the sandbox affects production reports, alerts, or data. You can delete and recreate test data with complete freedom.

​
Switching environments

Each environment has its own key. To point your integration at the sandbox, just use the sandbox key instead of the production one; the base URL is the same.
1

Get the sandbox key

In the admin application, go to Company → Information and open the Sandbox tab to copy the Sandbox Key. It is independent from your production key.
2

Configure your integration

Use that key in the Authorization header of your calls. The company and its data are resolved by the key, so the same code works against sandbox or production just by changing the key.
3

Promote to production

When the configuration works as expected, replicate it in production by switching back to the production key. Since the sandbox mirrors the same configuration, there are no surprises when promoting.
If you use the React Native SDK, just initialize it with the sandbox publicKey to send all captures to the test environment.

​
It mirrors the production configuration

The sandbox mirrors the production configuration: same folder structures, same ingestion schemas, same tracker, survey, and rule definitions. This lets you reproduce a real scenario and trust that what you validate will behave the same when you promote it. You can sync the production configuration into the sandbox whenever you want to start from a clean and representative state.

​
Safe for testing ingestion, transformations, and alerts

The sandbox is designed to exercise the full pipeline without risk:
  • Ingestion, Send payloads by event or in batch against the sandbox key and verify that they are normalized and validated as you expect. See the ingestion and extraction limits.
  • Transformations, Test your code transformation functions on sample data and review the output before activating them in production.
  • Alerts, Trigger test conditions to confirm that alerts fire and are delivered correctly, without notifying your real teams.
Sandbox data is test data and can be purged. Do not use the sandbox as a backup or store information there that you need to keep.