handle the migration of your data from Apache Unomi 1.5+ to Apache Unomi 2.0. { "eventType":"view", "scope":"digitall", "properties":{ "URLParameters":{ "utm_source":"source" "itemId":"ff5886e0-d75a-4061-9de9-d90dfc9e18d8", "itemType":"site" } } { "eventType":"view", "scope":"digitall", "flattenedProperties":{ "URLParameters":{ "utm_source":"source" yarn add apache-unomi-tracker SHELL 2.4.4. VIEWING COLLECTED EVENTS There are multiple ways to view the events that were received. For example, you could use the following cURL request: Another (powerful)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.21.2. View event type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . that developers might include the credentials to access it in non- secure parts of code such as client-side code. Since there is no difference between this endpoint and any other administration-focused "itemType":"page", "scope":"example" }, "events":[ { "eventType":"view", "scope": "example", "source":{ "itemType": "site",

Events are sent to Unomi from client 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 x - Documentation - 2 { "eventType": "view", "scope": "ACMESPACE", "source": { "itemType": "site", "scope": "ACMESPACE", "itemId": "c4761bbf-d85d-432b-8a94-37e866410375" information as is the case when the requested URI is context.json. However, if the client requests context.js then useful functions to interact with Unomi are added to the cxs