PROFILES ALIASES Profiles may now have alias IDs, which is a new way to reference profiles using multiple IDs. The Unomi ID still exists, but a new index with aliases can reference a single Unomi profile }' SHELL yarn add apache-unomi-tracker SHELL 2.4.4. VIEWING COLLECTED EVENTS There are multiple ways to view the events that were received. For example, you could use the following cURL request: the /cxs/profile endpoint. This endpoint was initially the only way to update a profile but it has multiple issues: it requires authenticated access. The temptation can be great to use this endpoint because

/cxs/profile endpoint. This endpoint was initially the only way to update a profile but it has multiple issues: • it requires authenticated access. The temptation can be great to use this endpoint because on the whole platform. • No history of profile modifications is kept: this can be a problem for multiple reasons: you might want to keep an trail of profile modifications, or even a history of profile and the value are the same but that is no way a requirement. It could even be possible to using multiple setPropertyAction instances to copy the same event property into different profile properties.

the property values. Note that it is not an issue to attempt to create the same property type multiple times as Unomi will not add a new property type if an identical type already exists. Once this server relies on Elasticsearch to discover and configure its cluster. You just need to install multiple context servers on the same network, and enable the discovery protocol in $MY_KARAF_HOME/etc/org