incremented on each page reload. You can also use the rule-list command to display all the rules in the system and the rule-tail to watch in real-time which rules are executed. The rule-view RULE_ID command array is created with two objects that associated personalization IDs with content IDs. Then we build the personalization object that contains the two IDs and their associated conditions (only a condition yet introduced more advanced notions such as profile segmentation or Groovy action scripting. The system is capable of much more, for example by directly using its actions to integrate with third-party

should look something like this: 1. Login to a social platform 2. Call back to a special secured system that performs an server-to-server call to send the login event to Apache Unomi using the Unomi key analytics.js- integration-apache-unomi.js apply your modification in this file then use the command yarn build to compile a new JS file. Then you can use the test page to try your changes http://localhost:8181/tracker/ form-mapping-example The parameter is the itemId of the rule. If you want to see all the rules deployed in the system you can use the command : unomi:rule-list 1000 The 1000 parameter is the limit of number of objects

values as opposed to a scalar value). `PropertyType`s can also be categorized using tags or file system structure, using sub-directories to organize definition files. Apache Unomi 1.1.x - Documentation BUILDING Simply type at the root of the project: mvn clean install -P generate-package The Maven build process will generate both a standalone package you can use directly to start the context server already installed Apache Karaf server (see "Deploying into an existing Karaf server") If you want to build and run the integration tests, you should instead use : mvn -P integration-tests clean install 2