may now have alias IDs, which is a new way to reference profiles using multiple IDs. The Unomi ID still exists, but a new index with aliases can reference a single Unomi profile. This enables more flexible a new Elasticsearch field type called Flattened (https://www.elastic.co/guide/en/elasticsearch/reference/7.17/flattened.html), and although it was available in prior versions of Elasticsearch, we do not "destinationURL": document.location.origin + document.location.pathname, "language": "en", "categories": [], "tags": []

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 8. Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . arch/reference/7.5/secure-cluster.html) Depending on your ElasticSearch license you may need to install Kibana and enable xpack security: https://www.elastic.co/guide/en/elasticsearch/reference/7.5/ configured to be only accessible by authenticated users (https://www.elastic.co/guide/en/elasticsearch/reference/7.5/setting-up-authentication.html) Just edit etc/org.apache.unomi.persistence.elasticsearch.cfg

/sites/ACMESPACE/home.html", "referringURL": "http://localhost:8080/", "language": "en" }, "category": {}, "attributes": {} } } } 1.1.3. PROFILES doesn’t yet save the context back to the context server. 2.1.7. INTEGRATING ONTO A PAGE Simply reference the context script in your HTML as in the following example: