Requirements
Fullstack project constraints and limitations
Fullstack projects differ from web-based projects. Key constraints:
General
All entities must have a unique identifier key (a string) when defined in the Convert web interface.
Audiences
The SDK does not manage persistence directly. You can provide your own DataStore to make user bucketing persistent. All audiences in a Fullstack project should be of type transient, where conditions are checked each time the visitor encounters the experience.
Segments
Segments represent audiences of type segmentation. Conditions are checked on every page view until they are met. In Fullstack projects, segments do not persist unless you provide a DataStore.
Rules
Rules are limited to the following types:
| Rule Type | Allowed Matching Types |
|---|---|
generic_bool_key_value | equals |
generic_numeric_key_value | equalsNumber, less, lessEqual |
generic_text_key_value | matches, regexMatches, contains, endsWith, startsWith |
Each rule must have a unique key (a string).
Experiences
Experiences are limited to:
| Type | Description |
|---|---|
a/b_fullstack | A standard A/B experience |
feature_rollout | An experience with only one non-original variation |
Features
Features support the following variable types:
| Type | Description |
|---|---|
boolean | True/false |
integer | Whole number |
string | Text |
json | JSON object or array |
Environments
All matching rules apply only to entities within the same environment. The default environments are staging and production.
Updated about 1 month ago