added to flattenedProperties by JSON schema but these value will be stored as flattened and will not create dynamic mapping contrary to the properties field of the events. Here is an example for objects that tracker/wab/src/main/webapp/index.html . However you will still need to use the REST API calls to create the scope and rule to make it all work. 2.4.1. INSTALLING THE WEB TRACKER IN A WEB PAGE Using accepted. So in order to make sure the events are collected with the above Javascript code, we must create a scope with the following request. The authorization is the default username/password for the REST

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2.5. How to create a new rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . will indeed retrieve all the events for a given profile. 2.2.5. HOW TO CREATE A NEW RULE There are basically two ways to create a new rule : • Using the REST API • Packaging it as a predefined rule will be exactly the same, and in most scenarios it will be more interesting to use the REST API to create and manipulate rules, as they don’t require any development or deployments on the Apache Unomi server

well as default segments to categorize users. Unomi users are, however, free and even encouraged to create additional properties and segments to better suit their needs. Contrary to other Unomi items, profiles line: feature:install -v war feature:repo-add cxf 2.7.11 feature:install -v cxf/2.7.11 . Create a new $MY_KARAF_HOME/etc/org.apache.cxf.osgi.cfg file and put the following property inside : trigger the loading of the /context.js script, which will try to retrieving the user context or create a new one if it doesn’t exist yet. It also contains an experimental integration with Facebook Login