Appendix: Glossary

March 28, 2019 00:30

Updated

The following terms are used by Split. In most cases, the definition is one commonly found in computing, experimentation or in the use of feature flags.

Terms

Definition

Split

Combines the feature (any front end or back end change) being released with the rollout plan associated with it. (i.e. a feature flag). Could also include how that given code change is impacting the metrics you care about.

Tags

An additional way to filter your Splits. Use tags for things like identifying several Splits on a theme or Splits that are long-lived for product packaging vs. short-term experiments.

Editors

Users of the Split app with the permission to edit a Split (i.e. feature)

A reserved treatment in Split named control that will be served to customers if a) the rollout plan for any Split has not been defined, b) the SDK does not have the feature cached, or c) the SDK encounters an exception.

Unique Users

Users are, generically, the external users or customers of the software where Split is being used for experimentation. Also known as “visitors.” Unique users are individual users with any duplicates of that user removed.

“Reshuffles the deck” to reset and randomly re-assign customers to the same rollout plan. For example, if a feature is set to “on” for 1% of customers and the feature has a bug, once the bug is fixed traffic can be reallocated to be “on” for a new 1% of customers in order to gain unbiased feedback.

When triggered, the Kill switch will immediately revert 100% of customers to the selected default treatment for that Split. Once killed, a feature can also be “Reactivated” to revert customers back to the exact state of the rollout plan set prior to the Kill.