Environment

Definition

Environments, in Bucket, serve to fully segregate the collected data. In practice, this means that any data received by our public API in the "Production" environment for example, will be completely different from the data collected in other environments. Specifically, this pertains to:

• Companies' details that have been collected

• Users' details

• Track events

• Collected feedback

• Feature events

Aside from the collected data itself, there are a number of environment-specific settings and behaviors that can be configured on features and feature views. Additionally, any targeting rules used within the app use environment-specific data.

Each new app, comes with three predefined environments: Production, Staging and Development.

You can create or delete any environment at any time, except the Production environment.

Deleted environments cannot be restored, and all collected data for that environment will essentially be lost.

The main use case for environments is to test if data is coming through as expected and if features are set up correctly on local or staging environments before releasing to production.

Next steps

• Learn about users and companies,

• Learn how to manage environments within Bucket UI.