Skip to main content

Stickiness Attributes

Stickiness attributes are user attributes that are used to persistently assign a user to a specific rollout or version.

Stickiness attributes are used to ensure that a user will experience rollouts, progresive deploys and versions in a consistent way. This can be important when a feature is deployed in stages, or when different versions of a feature are made available to different users.

In most of the cases stickiness attribute can be user IDs but sometimes we may chose another attribute.

For example lets imagine we have a streaming service for companies. We want to try a new feature and we roll out it for 5% of one country userbase, but we want that given any company all of the employees see the feature or none of them do.

In this case we will use the company id as a rollout stickiness atribute. This way all users of 5% of companyies of the segmented country will be able to see the new feature.

If we increase progresively to 20% of companyies the rollout but at some point we rollback to 5%, the same 5% of companyies will be able to keep seing the feature.