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 declared in a JSON schema for an property has been added to store the properties as flattened in Elasticsearch and should avoid mapping explosion for dynamic properties. If there is dynamic properties that you want to send with your event 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 event example in Apache

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3.3. Accessing profile properties in a context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 8.21.4. Update properties event type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 10.2.2. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

identifier (identity). This base structure can be extended, if needed, using properties in the form of key-value pairs. These properties are further defined by the Item’s type definition which explicits the the Item’s structure and semantics. By defining new types, users specify which properties (including the type of values they accept) are available to items of that specific type. Unomi defines default "itemType": , "scope": , "itemId": , "properties": properties> } Some types can be dynamically defined at runtime by calling to the REST API while