Create and utilize multiple environments. Different environments are useful if you need to use different setups for different domains, either within your organization or for your clients. Another way to utilize environments is to separate development and testing from your production setup.

🚧

Limitations

• Event identification is not separated by environment, meaning the same device will get the same visitorId in all environments.
• Proxy integrations are not scoped to a specific environment.

If this is something you would like to use, let us know by leaving feedback on our public roadmap.

Managing environments

To manage your environments, navigate to Settings → Environments.

Here you can create new environments, or delete existing ones.

Your application will always have a default environment which cannot be removed.

Configuring monthly usage limits

When managing environments, you can adjust monthly usage limit for each environment. This is useful when you don't want your testing environment, or an environment dedicated to an external team, to make excessive number of API calls.

You can configure the usage threshold and what happens when the threshold is reached.

• Selecting Notify turns on email notification when the environment reaches the set limit.
• Selecting Restrict turns on email notification, and will prevent any further calls to be made from this environment when the limit is reached. Restricting usage is available to Enterprise customers only.

The usage limit is reset every month on your billing date. For enterprise customers, this happens at the start of calendar month.

API keys

When creating new public API keys, you can assign them to a specific environment. By doing this, identification events registered with a specific environment can then be filtered by different set of request filtering rules.

To create a new API key for specific environment, go to API Keys. Changing environment for an existing key is not supported.

📘

Only public API keys are scoped to an environment.

Request filtering

When setting up request filtering rules, you can assign them to a specific environment. In combination with API keys, you can create different request filtering rules for each environment, ensuring that you don’t accidentally allow traffic from unwanted origins.

To manage environment specific request filtering rules, go to Security. On top of the page, you can select the environment you're configuring filtering rules for.

Sealed Client Results

When creating Encryption keys in order to enable Sealed Client Results, you can assign them to specific environment. This will result in client-side payload being encrypted for this particular environment. Other environments will remain unaffected and their payloads will not be encrypted.

To manage Encryption keys, go to API Keys and look for Encryption keys section.

Webhooks

When creating webhooks, you can optionally limit their scope to a specific environment. An environment-scoped webhook will only report identification events from the matching environment. On the other hand, workspace-scoped webhook will report all identification events from the workspace.

To manage webhooks, go to Webhooks.