. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 6.5. Related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . what is going on in the system. You can of course find more information about the REST API in the related section in the Apache Unomi website. For these requests it can be nice to use a browser (such as session. This query can have additional such as eventTypes, q (query), offset, size, sort. See the related section in the REST API for details. /cxs/events/search POST Listing events for a profile. You

type. A custom keyword named self has to be present in the JSON schemas to store the information related to each schema. The following example is the self part of the view event JSON schema. Having the withData specifies whether the data associated with the profile must be anonymized or not 11.5. RELATED You might also be interested in the Consent API section that describe how to manage profile consents what is going on in the system. You can of course find more information about the REST API in the related section (http://unomi.apache.org/documentation.html) in the Apache Unomi website. For these requests

most items are also associated to a scope, which is a concept that Unomi uses to group together related items. A given scope is represented in Unomi by a simple string identifier and usually represents granularity. In the context of web sites, a scope could, for example, represent a site or family of related sites being analyzed. Scopes allow clients accessing the context server to filter data to only see together and made clearer as Unomi captures more and more traces of their actions. Unomi will merge related profiles as soon as collected data permits positive association between distinct profiles, usually