Apache Unomi 1.x - DocumentationpageInfo object : Table 1. PageInfo Properties Name Description pageID A unique identifier in string format for the page. Default value : page path pageName A user-displayed name for the page. Default value 168.1.1 and 192.168.1.100 as well as the IPv6 loopback. Here’s another example using the subnet format: org.apache.unomi.thirdparty.provider1.ipAddresses=${env:UNOMI_THIRDPARTY_PROVIDER1_IPAD DRESSES:-1 subnets can be used as well, please refer to the IPAddress library documentation for details on how to format them. If you want to add another provider you will need to add them manually in the following file0 码力 | 158 页 | 3.65 MB | 1 年前3
Apache Unomi 2.x - Documentationevent, you should use the flattenedProperties field of the event. It’s also necessary to specify the format of the values which are added to flattenedProperties by JSON schema but these value will be stored "self": { "vendor": "org.apache.unomi", "name": "contactInfoSubmitted", "format": "jsonschema", "target": "events", "version": "1-0-0" }, "title": "cont 168.1.1 and 192.168.1.100 as well as the IPv6 loopback. Here’s another example using the subnet format: org.apache.unomi.thirdparty.provider1.ipAddresses=${env:UNOMI_THIRDPARTY_PROVIDER1_IPADDRESSES:-10 码力 | 117 页 | 4.78 MB | 1 年前3
Apache Unomi 1.1.x - Documentationexample when a rule is triggered. Events are sent to Unomi from client applications using the JSON format and a typical page view event from a web site could look something like the following: Example There are a couple of things to note here: • If we specify a payload, it is expected to use the JSON format so we stringify it and encode it if passed as a URL parameter in a GET request. • We need to make0 码力 | 32 页 | 477.20 KB | 1 年前3
共 3 条
- 1













