The Full Stack Developer Guide Developer Hub

Welcome to the Full Stack Developer Guide developer hub. You'll find comprehensive guides and documentation to help you start working with the Full Stack Developer Guide as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Define attributes

Use attributes to build the audiences that see your experiments, and use the Attributes tab to manage all your user attributes. In Full Stack, you can have up to 100 unarchived attributes per project. Attribute values are not explicitly typed in the Optimizely app. However, when you create audiences, you can choose different match criteria (comparison operations like 'greater than" or "equal to") depending on the format of the attribute value you pass. For more information, see Target audiences.

To create a new attribute:

  1. Navigate to Audiences > Attributes.
  2. Click New Custom Attribute.
  3. Enter a key for the attribute. For example, an attribute for visitors located in the United States might be called "US_VISITOR". You can pass attributes to the Full Stack SDK in your code, so always make sure to update your code with any changes made to your keys.
  4. Click Save.

Attribute keys must be unique:

  • within your project
  • across multiple projects, if you use the same user IDs across projects. (using identical attribute keys in multiple projects can cause incorrect attribution of events in the attribute-based segments on the Results page).

Value format requirements

For number and boolean audience types, the required types will vary by SDK. For Version match types, the required attribute value is a string representation of at least a Major and Minor version, with Patch version and additional release labels optional.

Updated 8 months ago


Define attributes


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.