To create a new feature flag, go to the feature flags tab in the PostHog app, and click on the "New feature flag" button in the top right.
This presents you with a form where you can complete the details of your new flag:
Here's a breakdown of each field in the form:
This is the name of the key you use in your code to evaluate the feature flag.
Description and tags
Metadata to describe and share information about your feature flag in the PostHog app.
Enable feature flag
This determines whether your flag is enabled. Disabled flags return
Persisting feature flags across authentication steps
This is only relevant if your feature flag is shown to both logged out AND logged in users.
Feature flag values are calculated based on a user's properties. Since it's possible for a user to have different properties before and after login, they may receive different feature flag values before and after logging in.
By enabling the option to persist feature flags across authentication, you ensure that the flag value remains the same.
There are trade-offs to enabling this:
- It slows down the feature flag response.
- It disables local evaluation of the feature flag.
- It disables bootstrapping the feature flag.
There are two types of feature flags:
1. Boolean flags.
2. Multiple variant flags (multivariate flags).
Instead of returning true or false, multivariate flags return a key – for example,
You can choose the rollout percentage for each variant key, where each is given a specific percentage of the total audience. Users will then be randomly assigned to each variant based on these percentages.
A payload is an additional piece of information sent to your app when a flag is matched for a user. The returned value can be any valid JSON type (object, array, number, string, boolean, or null).
They enable you to configure functionality related to your flag inside PostHog, instead of having to make code changes or redeploy your app.
This specifies the conditions a user must meet to access the feature flag and receive a value.