on which to perform the merge (the email). What this means is that upon successful login using an email, Unomi will look for other profiles that have the same email and merge them into a single profile profile. Because of the merge, this should only be done for authenticated profiles, otherwise this could be a security issue since it could be a way to load data from other profiles by merging their data cfg Apache Unomi 1.x - Documentation - 29 Usually, login events, which operate on profiles and do merge on protected properties, must be secured. For each trusted third party server, you need to add these

on which to perform the merge (the email). What this means is that upon successful login using an email, Unomi will look for other profiles that have the same email and merge them into a single profile profile. Because of the merge, this should only be done for authenticated profiles, otherwise this could be a security issue since it could be curl -X POST http://localhost:8181/cxs/profiles/search \ --user INTERACTIONS WITH MERGING Profile merges have been modified to use aliases starting Unomi 2 Upon merge: Properties are copied to the master profile as before An alias is created for the "master" profile

patched together and made clearer as Unomi captures more and more traces of their actions. Unomi will merge related profiles as soon as collected data permits positive association between distinct profiles e.g : US visitor, non-US visitor, etc. PROPERTYMERGESTRATEGYTYPE A strategy to resolve how to merge properties when merging profile together. PROPERTYTYPE Definition for a profile or session property found to have the same value for the "email" property they will be merged by this action. Upon merge, the old profiles are marked with a "mergedWith" property that will be used on next profile access