Unblu 6 (latest)

Unblu supports subdomain switching. This means a session can remain active if there is a navigation to another subdomain. This requires a definition of a cookie domain in the Unblu server configuration file (

The following property should be used to define a cookie domain:


A cookie domain can be set in one of the following ways; depending on the requirement/use-case (valid from Unblu 3.5.x and all new versions):

  1. If no subdomain-switch is required: then no cookie domain needs to be defined. In this way Unblu uses the current context origin as the cookie domain. For example, consider the visitor is on In this case Unblu uses as the cookie domain when creating cookies.

  2. If a subdomain-switch (only for one domain) is desired: it requires a cookie domain to be set as follows:

    In this case Unblu will use as a cookie domain when creating cookies. As a result, a subdomain switch is possible. This means if the visitor navigates to a subdomain (let us say to and the Unblu snippet is present on that page, the Unblu session will remain active.

  3. If a subdomain-switch is required (for more than one domain): a cookie domain should be set as follows:


    In this case Unblu will set the cookie domain to the second level domain of the current context origin. For example, consider the visitor is on In this case Unblu uses as the cookie domain. As a result, a subdomain-switch is possible for multiple domains (but only for the current context origin domain).

The property com.unblu.identifier.cookieDomain is considered only for the visitor context origin. This means your agent does not have to access the "Unblu Agent Desk" through the same origin defined via com.unblu.identifier.cookieDomain.