For the complete documentation index, see llms.txt. This page is also available as Markdown.

Account Condition / User Attributes

A condition that is associated with a user's account.

Overview

User attributes are information about a user, such as the user's knowledge, skills, and attributes on general topics. These user attributes are calculated and aggregated through the experience data performed by the user.

An example use case: the "vr_controls_familiarity" user attribute is a numerical value between 0.0 and 1.0 that defines how much experience a user has with virtual reality and its controls. If the user's "vr_controls_familiarity" falls below 0.25, the simulation may present a tutorial to guide the user through VR controls.

An example use case

Additional attributes will be added in the future. If there are additional user attributes that you would like to request for your use case, please contact us at https://www.siminsights.com/contact.

How to Use

User attributes can be used in the state machine as a condition.

  1. Select "Account Condition" in the condition type dropdown, then click "Create".

  2. Select the attribute by clicking "Select Attribute" and choosing the desired attribute (for example, "vr_controls_familiarity").

  3. Select the operator (Equals, Greater than, Less than, etc).

  4. Enter the value the attribute is compared to using the operator. If the value is satisfied, the condition passes.

How to edit

Depending on their license, Authors can edit the value of user attributes as users go through their experience. To request access to this feature, please contact us at https://www.siminsights.com/contact.

  1. User attributes can be edited using the Set User Attribute state action.

  2. Select the attribute by clicking "Select Attribute" and choosing the desired attribute (for example, "vr_controls_familiarity").

  3. Set the value of the attribute. If the attribute type is a number, enter a number. If it is true/false, toggle the checkmark.

Keep in mind: user attributes are tied to the user and persist across simulations.

Last updated