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. This means object properties must be be stored as flattened and will not create dynamic mapping contrary to the properties field of the events. Here is an example for objects that used dynamic properties for URL parameters: The following our Unomi 2 migration process will handle the data model changes for you. If you are using custom events/objects, please refer to the detailed migration guide for more details. 1.1.5. NEW WEB TRACKER

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2.4. How to search for profile events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.4. Sending events using the context servlet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.5. Sending events using the eventcollector servlet using property files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 2.5.4. Secured events configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1.2. Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . that clients can use to share data across scopes. 1.1.2. EVENTS Users' actions are conveyed from clients to the context server using events. Of course, the required information depends on what is collected and users' interactions with the observed systems but events minimally provide a type, a scope and source and target items. Additionally, events are timestamped. Conceptually, an event can be seen as