"properties":{ "URLParameters":{ "utm_source":"source" } }, "target":{ "scope":"digitall", "itemId":"30c0a9e3-4330-417d-9c66-4c1beec85f08", "itemType":"page" "flattenedProperties":{ "URLParameters":{ "utm_source":"source" } }, "target":{ "scope":"digitall", "itemId":"30c0a9e3-4330-417d-9c66-4c1beec85f08", "itemType":"page" You can notice the following in the above schema: We are creating a schema of type "events" ("self.target" equals "events") The name of this schema is "contactInfoSubmitted", this MUST match the value of

"scope":"example", "itemId": "mysite" }, "target":{ "itemType":"form", "scope":"example", "itemId":"contactForm" "scope":"example", "itemId": "mysite" }, "target":{ "itemType":"page", "scope":"example", "itemId":"homepage" "scope":"example", "itemId": "mysite" }, "target":{ "itemType":"page", "scope":"example", "itemId":"homepage"

"metadata": { "id": "tweetNb", "name": "tweetNb", "tags": ["social"] }, "target": "profiles", "type": "integer" } Unomi defines a built-in scope (called systemscope) that clients 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 the object. "scope": , "source": , "target": , "properties": } Source and target can be any Unomi item but are not limited to them. In particular