http://localhost:8181/context.json?sessionId=1234 \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "source": { "itemId":"homepage", "itemType":"page", "scope":"example" }, property names to find your needs. For example you might want to prefix the profile properties with the source of the event, such as 'mobileApp:firstName'. Apache Unomi 1.x - Documentation - 10 You could then { "eventType":"contactInfoSubmitted", "scope": "example", "source":{ "itemType": "site", "scope":"example", "itemId":

"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" "scope":"digitall", "flattenedProperties":{ "URLParameters":{ "utm_source":"source" } }, "target":{ "scope":"digitall", "itemId":"30c0a9e3-4330

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