Unleash

Unleash

  • Documentation
  • Deploy and manage
  • Integrations
  • Contribute
  • API
  • Enterprise
  • Help

›Getting started

Getting started

  • Introduction
  • Connect your SDK
  • Client SDK
  • Create a feature toggle
  • Activation Strategies
  • Control rollout
  • Projects
  • Unleash Context
  • Working with native apps
  • Working with single page apps

Working with the SDK

  • Java SDK
  • Node SDK
  • .net SDK
  • GO SDK
  • Python SDK
  • Ruby SDK

Addons framework

  • Addons Introduction
  • Webhook
  • Slack
  • Jira commenter

Advanced

  • Strategy Constraints
  • Custom Activation Strategy
  • Feature Toggle Types
  • Feature Toggle Variants
  • Archived toggles
  • The audit log
  • API Access
  • Tagging Features

Unleash Context

To standardise a few activation strategies, we also needed to standardise the Unleash context, which contains fields that vary per request, required to implement the activation strategies.

The unleash context is defined by these fields:

  • userId: String,
  • sessionId: String,
  • remoteAddress: String,
  • properties: Map<String, String>
  • appName: String
  • environment: String

All fields are optional, but if they are not set you will not be able to use certain activation strategies.

E.g., the userWithId strategy obviously depends on the userId field.

The properties field is more generic and can be used to provide more arbitrary data to strategies. Typical usage is to add more metadata. For instance, the betaUser strategy may read a field from properties to check whether the current user is a beta user.

← ProjectsWorking with native apps →
Unleash
Docs
Getting StartedSecuring UnleashAPI Reference
Community
User ShowcaseSlack communityUnleash-hosted.comTwitter
More
GitHubStar