. . . . . . . . . . . 18 2.4.3. Tracking page views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.4.4. Tracking form submissions custom page information for the initial page view, you can simply Apache Unomi 1.x - Documentation - 18 do it like this: unomiTracker.initialize({ scope: 'myScope', url: 'http://unomi:8181' "_filtered": 4085, "2018-10-02": 3, "2018-10-03": 17, "2018-10-04": 18, "2018-10-05": 19, "2018-10-06": 23, "2018-10-07": 18, "2018-10-08": 20 } You can see that we retrieve the count of newcomers

}, "source":{ "scope":"digitall", "itemId":"ff5886e0-d75a-4061-9de9-d90dfc9e18d8", "itemType":"site" } } { "eventType":"view", "scope":"digitall", "flattenedProperties":{ }, "source":{ "scope":"digitall", "itemId":"ff5886e0-d75a-4061-9de9-d90dfc9e18d8", "itemType":"site" } } It is worth keeping in mind that for Apache Unomi 2.0 we do "_filtered": 4085, "2018-10-02": 3, "2018-10-03": 17, "2018-10-04": 18, "2018-10-05": 19, "2018-10-06": 23, "2018-10-07": 18, "2018-10-08": 20 } JSON The resulting JSON response will look something

trigger the rule via the condition property. Here, we specify Apache Unomi 1.1.x - Documentation - 18 that we want our rule to trigger on an eventTypeCondition condition. Unomi can be extended by adding