Environment settings for projects (legacy feature)

In Amplitude Data, the project is where you configure events, properties, sources, and destinations. It's also called the tracking plan. This is distinct from an environment.

Amplitude Analytics also uses projects, but it does so differently. Setting up a project in Amplitude Analytics is a prerequisite for receiving data from your product. The project is where the data flows to, and where you conduct your analyses.

It's best practice to have at least two projects in Amplitude Analytics: one for production, and one for development. This way, you can validate against the development project first, and then roll out approved changes to production.

In Amplitude Data, the environment is another name for a specific project in Amplitude Analytics.

Each project in Amplitude Data can have up to two environments. Use one for debugging and the other for clean production data.

In Amplitude Data, the Environments tab is where you manage the mapping between your two environments (production and development) and your Amplitude projects. Amplitude Data uses the information you enter here to configure sources and destinations, validate data in the tracking plan page, and sync schemas on the Integrations tab.

For each environment, select the project name from the drop-down list. When you're finished, click Save.

Environments in the tracking plan

You can make modifications to your tracking plan in any filtered environment (Production, Development, or Staging), or an environment further segmented by status and filters, as seen in the image below. Understand which changes sustain when working in environments where the action wasn't taken.

Any creation, update, or deletion of events, properties, or groups applies to all environments that the object is present in. All other actions, like blocking or transformations, are environment-specific.

The following table highlights actions that sustain across all environments versus actions that sustain only in the filtered environment where you performed the action.

Actions that sustain across all environments are:

• Creating events, properties, or groups.
• Updating events, properties, or groups (includes visibility and activity status changes).
• Deleting events, properties, or groups.

Actions that sustain only in the filtered environment where you performed the action are:

• Applying block or drop filters.
• Blocking events, properties, or groups.
• Any action involving custom events.
• Any action involving derived properties.
• Any action involving lookup properties.
• Any action involving transformations.