THE CURRENT PROFILE By default, Unomi uses a cookie called context-profile-id to keep track of the current profile. You can use this the value of this cookie which contains a UUID to lookup the details /context.json and /eventcollector will now look up profiles by profile ID or aliases from the same cookie ( context-profile-id ) or body parameters ( profileId ) Verb Path Description GET /cxs/profil original profile and replace it with the merged profile (aka "master" profile). Once this is done, all cookie tracking will use the merged profile. To test, simply configure the action in the "login" or "facebookLogin"

original profile and replace it with the merged profile (aka "master" profile). Once this is done, all cookie tracking will use the merged profile. To test, simply configure the action in the "login" or "facebookLogin" Unomi 1.x - Documentation - 36 and you will also need to change the cookie domain in the same file: org.apache.unomi.profile.cookie.domain=apache.org Main virtual host config: session was found, the profile ID is extracted from the session and if it not found, Unomi looks for a cookie called context-profile-id to read the profileID. If no profileID is found or if the session didn’t

original profile and replace it with the merged profile (aka "master" profile). Once this is done, all cookie tracking will use the merged profile. To test, simply configure the action in the "login" or "facebookLogin"