Namespace priority namespace-priority
Every customer implementation is unique and tailored to meet a particular organization鈥檚 goals, and as such, the importance of a given namespace varies from customer to customer. Real-world examples include:
- Your company might consider each email address to represent a single-person entity and therefore use identity settings to configure the email namespace as unique. Another company, however, might want to represent single-person entities as having multiple email addresses, and thus configure the email namespace as not-unique. These companies would need to use another identity namespace as unique, such as a CRMID namespace, so there can be a single-person identifier linked to the multiple email addresses.
- You might collect online behavior using a 鈥淟ogin ID鈥 namespace. This Login ID could have a 1:1 relationsh