schema required us to modify Apache Unomi data model, One of the key differences is the removal of open maps. The properties field in the events objects provided by unomi are now restricted by JSON schema "eventType":"view", "scope":"digitall", "properties":{ "URLParameters":{ "utm_source":"source" } }, "target":{ "scope":"digitall", "itemId":"30c0a9e3-4330 ... }, "attributes":{}, "consentTypes":[] } }, "source":{ "scope":"digitall", "itemId":"ff5886e0-d75a-4061-9de9-d90dfc9e18d8", "itemType":"site"

changes are introduced quite often. If in doubt, don’t hesitate to check with the Apache Unomi community to get the latest information about ElasticSearch version compatibility. Apache Unomi 1.x - Documentation This indicates that all the Unomi services are started and ready to react to requests. You can then open a browser and go to http://localhost:8181/cxs to see the list of available RESTful services or retrieve http://localhost:8181/context.json?sessionId=1234 \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "source": { "itemId":"homepage", "itemType":"page", "scope":"example" },

provide a type, a scope and source and target items. Additionally, events are timestamped. Conceptually, an event can be seen as a sentence, the event’s type being the verb, the source the subject and the target , "scope": , "source": , "target": , "properties": } Source and target can be any Unomi item but are not limited to properties and Unomi’s type mechanism and can be processed either natively or via extension plugins, source and target can represent just about anything. Events can also be triggered as part of Unomi’s internal