Skip to content

Edits to Multi Environment docs #2712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
russell-loube-mixpanel wants to merge 3 commits into
base: mestopinal-multi-environment-docs
Choose a base branch
from
Open

Edits to Multi Environment docs #2712

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
936ac43
Clarify Multiple Environments docs
russell-loube-mixpanel May 19, 2026
19bfc17
Mention both experiments and flags in intro; drop competitor names
russell-loube-mixpanel May 19, 2026
bbadde2
Add callout about cross-project feature flag billing
russell-loube-mixpanel May 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 18 additions & 15 deletions pages/docs/experiments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -259,36 +259,39 @@ You can also add the experiment breakdowns and filters directly in a report via

## Multiple Environments

Multiple Environments lets you treat separate Mixpanel projects as development, staging, and production environments for the same experiment or feature flag. Build and iterate on an experiment (and its underlying flag) in one project, then push it to another project when you're ready — without recreating it by hand. Linked experiments and flags stay connected so you can continue pushing updates over time.

### Other Environments Selector

The "Other Environments" selector will appear under the "Settings" tab of a feature flag. This panel allows the user
to manage changes between Experiments across different projects. This enables users to use a Mixpanel project as a development environments
where they can create and make changes to an experiment, and select another project to push those changes to.
The "Other Environments" selector appears under the **Configuration** tab of an experiment, inside the **More** section. This panel lets you manage an experiment's links to copies of itself in other projects.

#### Pushing changes
When pushing changes to a linked experiment, the source experiment will push all info to the destination flag. All other changes on the destination experiment will
be overwritten.

Pushing changes copies the full configuration of the source (original) experiment to the linked destination experiment in the other project. Any changes that exist only on the destination experiment will be overwritten.

#### Other Environments Menu

This menu displays a list of the linked experiment that exist in other projects. From here, you can manage the other experiments. This menu allows you
to navigate to the linked experiment, push changes that have occurred to the linked experiment, or remove the connection.
This menu lists the experiments in other projects that are linked to the current experiment. From here, you can navigate to a linked experiment, push the source experiment's current configuration to it, or remove the connection.

#### Duplicate To Project

A user can duplicate an experiment to other projects. You may not use this experiment for duplicating to the same project (use the existing duplicate flow instead).
Once a user has duplicated an experiment to another project, they will be able to manage the connection from within the "Other Environments" menu.
To duplicate an experiment to another project, open the experiment's overflow (`...`) menu in the top-right of the experiment page and select **Duplicate**. In the dialog, choose the destination project.

This flow is for duplicating across projects only — to duplicate within the same project, use the same **Duplicate** option and leave the current project selected (this is also the standard in-project duplicate behavior).

Once duplicated, the new experiment is linked to the original and can be managed from the "Other Environments" menu.

#### Feature Flags

If an experiment is linked to a Mixpanel Feature Flag, you can manage both from within the Experiments "Other Environments" menu.
If an experiment is linked to a **Mixpanel** Feature Flag, the underlying flag cannot be duplicated on its own from the Feature Flags page — use the experiment's Duplicate flow to copy the experiment and flag together. If your experiment uses a **third-party** flag instead, you can duplicate the experiment directly; no flag duplication step is involved.
Copy link
Copy Markdown
Contributor

@matthewestopinal matthewestopinal May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently a user can duplicate the flag on it's own if they want to. But they are also able to duplicate both from the experiment page

Copy link
Copy Markdown
Contributor Author

@russell-loube-mixpanel russell-loube-mixpanel May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting — in P3 I'm seeing the Duplicate button disabled on experiment-type flags with the tooltip "You cannot duplicate an experiment type feature flag" (screenshot below).

Copy link
Copy Markdown
Contributor Author

@russell-loube-mixpanel russell-loube-mixpanel May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2026-05-19 at 4 39 02 PM

Copy link
Copy Markdown
Contributor

@matthewestopinal matthewestopinal May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha. Yeah in this case we should probably match the existing flow.

Are you good with me just disabling the "Duplicate to Project" button in the Other Environments selector and displaying a tooltip with the same copy writing here?


When duplicating an experiment that is linked to a Mixpanel Flag to another project, you will be prompted to confirm whether or not you
would also like to duplicate the linked flag. If you choose to do so, the new experiment will be linked to the new flag. The new flag will
also appear in the "Other Environments" menu for the original flag; they will be linked.
When duplicating an experiment that is linked to a Mixpanel Flag to another project, you will be prompted to confirm whether you also want to duplicate the linked flag. If you do, the new experiment will be linked to the new flag, and the new flag will also appear in the "Other Environments" menu of the original flag.

When pushing changes to a project, if both the destination and source experiments are linked to flags that are ALSO linked, (i.e. you choose
to duplicate the flag as well), you may choose to push any changes that have occurred in the source flag to the destination projects flag.
When pushing changes, if both the source and destination experiments are linked to flags that are also linked (i.e., you chose to duplicate the flag as well), you can choose to push any changes from the source flag to the destination project's flag at the same time.

<Callout type="info">
**Billing across projects:** You aren't double-charged for using the same feature flag across multiple projects. Mixpanel charges based on active feature flag keys, so the same flag-key shared across projects is counted once.
</Callout>

## Advanced Statistical Methods

Expand Down
30 changes: 19 additions & 11 deletions pages/docs/featureflags.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -374,31 +374,39 @@ to the feature flag page of the associated flag, or the related experiment page.

## Multiple Environments

Multiple Environments lets you treat separate Mixpanel projects as development, staging, and production environments for the same feature flag or experiment. Build and iterate on a flag (and any experiment it's tied to) in one project, then push it to another project when you're ready — without recreating it by hand. Linked flags and experiments stay connected so you can continue pushing updates over time.

### Other Environments Selector

The "Other Environments" selector will appear under the "Settings" tab of a feature flag. This panel allows the user
to manage changes between Feature Flags across different projects. This enables users to use a Mixpanel project as a development environments
where they can create and make changes to a flag, and select another project to push those changes to.
The "Other Environments" selector appears under the **Configuration** tab of a feature flag, inside the **More** section. This panel lets you manage a flag's links to copies of itself in other projects.

#### Pushing changes
When pushing changes to a linked flag, the source flag will push all info to the destination flag. All other changes on the destination flag will
be overwritten.

Pushing changes copies the full configuration of the source (original) flag to the linked destination flag in the other project. Any changes that exist only on the destination flag will be overwritten.

#### Other Environments Menu

This menu displays a list of the linked feature flags that exist in other projects. From here, you can manage the other flags. This menu allows you
to navigate to the linked flag, push changes that have occurred to the linked flag, or remove the connection.
This menu lists the feature flags in other projects that are linked to the current flag. From here, you can navigate to a linked flag, push the source flag's current configuration to it, or remove the connection.

#### Duplicate To Project

A user can duplicate a feature flag to other projects. You may not use this feature for duplicating to the same project (use the existing duplicate flow instead).
Once a user has duplicated a flag to another project, they will be able to manage the connection from within the "Other Environments" menu.
To duplicate a feature flag to another project, open the flag's overflow (`...`) menu in the top-right of the flag page and select **Duplicate**. In the dialog, choose the destination project.

This flow is for duplicating across projects only — to duplicate within the same project, use the same **Duplicate** option and leave the current project selected (this is also the standard in-project duplicate behavior).

Note that flags created as part of an experiment (experiment-type flags) cannot be duplicated from the Feature Flags page — duplicate the parent experiment instead, which will optionally duplicate the linked flag with it.
Copy link
Copy Markdown
Contributor

@matthewestopinal matthewestopinal May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not currently true, although we could add this restriction. It may need some UX work though (I'm imagining the Multi Env selector just shows a redirect message to the experiment page instead of the normal multi-env content). Or we just hide the button altogether and replace with a link to the experiment tab.

Copy link
Copy Markdown
Contributor Author

@russell-loube-mixpanel russell-loube-mixpanel May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same topic as the experiments.mdx thread — see screenshot there.


Once duplicated, the new flag is linked to the original and can be managed from the "Other Environments" menu.

#### Data Groups

Feature Flag rollouts may include configuration that reference data groups in a given project. For instance, if the user changes the
Feature Flag rollouts may include configuration that references data groups in a given project. For instance, if you change the
"Assignment Key" of a flag, both the source and destination projects _must_ include the referenced data group in order to duplicate or push changes.
If the assignment key is _not_ present in the destination project, the operations will fail.
If the assignment key is _not_ present in the destination project, the operation will fail.

<Callout type="info">
**Billing across projects:** You aren't double-charged for using the same feature flag across multiple projects. Mixpanel charges based on active feature flag keys, so the same flag-key shared across projects is counted once.
</Callout>

## Feature Flagging Pricing FAQ

Expand Down
Loading