running, you should wait until you see the following messages on the Karaf console: Initializing user list service endpoint... Initializing geonames service endpoint... Initializing segment service endpoint of a rule: Apache Unomi 1.x - Documentation - 9 curl -X POST http://localhost:8181/cxs/rules \ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "metadata": { "id": "setContactInfo" documentation is available in the REST API) : curl -X POST http://localhost:8181/cxs/events/search \ --user karaf:karaf \ -H "Content-Type: application/json" \ -d @- <<'EOF' { "offset" : 0, "limit" : 20,

will only load the tracker. To initialize it use a snipper like the following code: Initializing user list service endpoint... Initializing geonames service endpoint... Initializing segment service endpoint sent by the tracker when a page is loaded) and increments a property called pageViewCount on the user’s profile. You can then reload then page and check with the profile-view PROFILE_UUID SSH command custom events, API, … Learn more about segmentation View some more samples Continue reading Unomi’s user manual to see all that is possible with this technology 3. APACHE UNOMI RECIPES AND REQUESTS 3.1

information can then be used to personalize content, derive insights on user behavior, categorize the user profiles into segments along user-definable dimensions or acted upon by algorithms. 1.1.1. ITEMS AND } } } 1.1.3. PROFILES By processing events, Unomi progressively builds a picture of who the user is and how they behave. This knowledge is embedded in Profile object. A profile is an Item with any other Unomi items, profiles are not part of a scope since we want to be able to track the associated user across applications. For this reason, data collected for a given profile in a specific scope is still