here. 1.1.2. SCOPES DECLARATIONS ARE NOW REQUIRED Scopes declarations are now required in Unomi 2. When submitting an event and specifying a scope, that scope must already be declared on the platform. events. For example a rule could update a profile when a certain event comes in, either copying values from the event or performing some kind of computation when the event occurs, including accessing remote property in the current profile. The above rule will execute when a view event is received (which is automatically sent by the tracker when a page is loaded) and increments a property called pageViewCount

ElasticSearch 7.4 . It is highly recommended to use the ElasticSearch version provided by the documentation when possible. However minor versions (7.4.x) should also work, and one version higher (7.5) will usually history of profile values in case you want to understand how a profile property was modified. • Even when protected using some kind of proxy, potentially the whole profile properties might be modified, including aforementioned security issues. The second method, although a little more involved, is much preferred. When sending a login event, you can setup a rule that can check a profile property to see if profiles can

just about anything. Events can also be triggered as part of Unomi’s internal processes for example when a rule is triggered. Events are sent to Unomi from client applications using the JSON format and expected structure and which fields are expected to be provided at runtime, that are then instantiated when needed with actual values. 1.2.2. PLUGIN STRUCTURE Being built on top of Apache Karaf, Unomi leverages ACTIONTYPE ActionType`s define new actions that can be used as consequences of Rules being triggered. When a rule triggers, it creates new actions based on the event data and the rule internal processes,