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. Scopes can be easily object properties must be declared in a JSON schema for an event to be accepted. A new property, flattenedProperties has been introduced to the event object, this property has been added to store the properties properties. If there is dynamic properties that you want to send with your event, you should use the flattenedProperties field of the event. It’s also necessary to specify the format of the values which are

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.2.8. How to send a login event to Unomi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 8.6. Event. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 8.6.2. Event types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conceptually, an event can be seen as a sentence, the event’s type being the verb, the source the subject and the target the object. Event structure: { "eventType": event>, "scope": "scope": event>, "source": , "target": , "properties": } Source and target can be any Unomi item but are not limited to them. In particular, as long applications using the JSON format and a typical page view event from a web site could look something like the following: Example page view event: Apache Unomi 1.1.x - Documentation - 2 { "eventType":