cxs object that contains the context with the current user profile, segments, scores as well as functions that makes it easier to perform further requests (such as collecting events using the cxs.collectEvents() Result will be something like this: 2084 8.2. METRICS Metric queries make it possible to apply functions to the resulting property. The supported metrics are: sum avg min max It is also possible to is quite straight forward to use. There are also helper functions to build events, such as : Here’s an example of using these helper functions and the collectEvent function alltogether: SENDING MULTIPLE

cxs object that contains the context with the current user profile, segments, scores as well as functions that makes it easier to perform further requests (such Apache Unomi 1.x - Documentation - 14 as Result will be something like this: 2084 3.2. METRICS Metric queries make it possible to apply functions to the resulting property. The supported metrics are: • sum Apache Unomi 1.x - Documentation - containing strictly context information or as a couple of JSON objects augmented with javascript functions that can be used to interact with the Unomi server using the /context

containing strictly context information or as a couple of JSON objects augmented with javascript functions that can be used to interact with the Unomi server using the /context }(document, 'script', 'context')); This initial context results in a javascript file providing some functions to interact with the context server from javascript along with two objects: a cxs object containing context.json. However, if the client requests context.js then useful functions to interact with Unomi are added to the cxs object in addition to the context information