[2-6]" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown 4.12 section: NOTE If you don’t want profile to be created if missing, set createIfMissing to false . The response will look like this: 6.5.2. UPDATING PROFILE Now let’s update our profile with some data. It can "firstName": "John", "lastName": "Doe", "gender": "Male" } } ] } JSON The response will have the number of processed events: NOTE processEvents accepts a number of other event types

Unomi 1.1.x - Documentation - 5 RULE `Rule`s are conditional sets of actions to be executed in response to incoming events. Triggering of rules is guarded by a condition: the rule is only triggered if be updated with the new values of the properties coming from Unomi. Additionnally, the raw JSON response is displayed. We will now explain in greater details some concepts and see how the example works conditions in the source page, if any> } We will look at the details of the context request and response later. 2.3. EXAMPLE 2.3.1. OVERVIEW We will examine how a simple HTML page can interact with

[2-6]" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown common processed against the profile 8. The updated profile is sent back as a response to the context.json request. Along with the response It is important to note that the profileID is always server-generated "condition": { "type": "matchAllCondition", "parameterValues": {} } } EOF The resulting JSON response will look something like this: Apache Unomi 1.x - Documentation - 48 { "_all":4095, "_filtered":4095