is currently considered a beta feature. We look forward for this new GraphQL API to be used, feel free to open discussion on Unomi Slack channel (https://the-asf.slack.com/messages/CBP2Z98Q7/) or create name, age, email, etc.) as well as default segments to categorize users. Unomi users are, however, free and even encouraged to create additional properties and segments to better suit their needs. Contrary CONDITION TYPE DESCRIPTORS Here is a non-exhaustive list of condition types built into Apache Unomi. Feel free to browse the source code if you want to discover more. But the list below should get you started

name, age, email, etc.) as well as default segments to categorize users. Unomi users are, however, free and even encouraged to create additional properties and segments to better suit their needs. Contrary CONDITION TYPE DESCRIPTORS Here is a non-exhaustive list of condition types built into Apache Unomi. Feel free to browse the source code if you want to discover more. But the list below should get you started EXISTING ACTION TYPES DESCRIPTORS Here is a non-exhaustive list of actions built into Apache Unomi. Feel free to browse the source code if you want to discover more. But the list below should get you started

name, age, email, etc.) as well as default segments to categorize users. Unomi users are, however, free and even encouraged to create additional properties and segments to better suit their needs. Contrary standard). Note that this last object is not under control of the context server and clients are free to use it or not. Our example will not make use of it. On the other hand, the cxs top level object