Identity namespaces are a component of Identity Service that serve as indicators of the context to which an identity relates. For example, they distinguish a value of “firstname.lastname@example.org” as an email address or “443522” as a numeric CRM ID.
Working with identity namespaces requires an understanding of the various Adobe Experience Platform services involved. Before beginning to work with namespaces, please review the documentation for the following services:
A fully qualified identity includes an ID value and a namespace. When matching record data across profile fragments, as when Real-time Customer Profile merges profile data, both the identity value and the namespace must match.
For example, two profile fragments may contain different primary IDs but they share the same value for the “Email” namespace, therefore Platform is able to see that these fragments are actually the same individual and and brings the data together in the identity graph for the individual.
Data can be identified by several different identity types. The identity type is specified at the time the identity namespace is created and controls whether or not the data is persisted to the identity graph and any special instructions for how that data should be handled.
The following identity types are available within Platform:
|Cookie ID||Cookie IDs identify web browsers. These identities are critical for expansion and constitute the majority of the identity graph. However, by nature they decay fast and lose their value over time.|
|Cross-Device ID||Cross-device IDs identify an individual and usually tie other IDs together. Examples include a login ID, CRM ID, and loyalty ID. This is an indication to Identity Service to handle the value sensitively.|
|Device ID||Device IDs identify hardware devices, such as IDFA (iPhone and iPad), GAID (Android), and RIDA (Roku), and can be shared by multiple people in households.|
|Email address||Email addresses are often associated with a single person and therefore can be used to identify that person across different channels. Identities of this type include personally identifiable information (PII). This is an indication to Identity Service to handle the value sensitively.|
|Non-people identifier||Non-people IDs are used for storing identifiers that require namespaces but are not connected to a person cluster. For example, a product SKU, data related to products, organizations, or stores.|
|Phone number||Phone numbers are often associated with a single person and therefore can be used to identify that person across different channels. Identities of this type include PII. This is indication to Identity Service to handle the value sensitively.|
Experience Platform provides several identity namespaces that are available to all organizations. These are known as standard namespaces and are visible using the Identity Service API or through the Platform UI.
The following standard namespaces are provided for use by all organizations within Platform:
|AdCloud||A namespace that represents Adobe AdCloud.|
|Adobe Analytics (Legacy ID)||A namespace that represents Adobe Analytics. See the following document on Adobe Analytics namespaces for more information.|
|Apple IDFA (ID for Advertisers)||A namespace that represents Apple ID for Advertisers. See the following document on interest-based ads for more information.|
|Apple Push Notification service||A namespace that represents identities collected using Apple Push Notification service. See the following document on Apple Push Notification service for more information.|
|CORE||A namespace that represents Adobe Audience Manager. This namespace can also be referred to by its legacy name: “Adobe AudienceManager”. See the following document on Audience Manager IDs for more information.|
|ECID||A namespace that represents ECID. This namespace can also be referred to by the following aliases: “Adobe Marketing Cloud ID”, “Adobe Experience Cloud ID”, “Adobe Experience Platform ID”. See the following document on ECID for more information.|
|A namespace that represents an email address. This type of namespace is often associated to a single person and therefore can be used to identify that person across different channels.|
|Emails (SHA256, lowercased)||A namespace for pre-hashed email address. Values provided in this namespace are converted to lowercase before hashing with SHA256. Leading and trailing spaces need to be trimmed before an email address is normalized. This setting cannot be changed retroactively. See the following document on SHA256 hashing support for more information.|
|Firebase Cloud Messaging||A namespace that represents identities collected using Google Firebase Cloud Messaging for push notifications. See the following document on Google Firebase Cloud Messaging for more information.|
|Google Ad ID (GAID)||A namespace that represents a Google Advertising ID. See the following document on Google Advertising ID for more information.|
|Google Click ID||A namespace that represents a Google Click ID. See the following document on Click tracking in Google Ads for more information.|
|Phone||A namespace that represents a phone number. This type of namespace is often associated to a single person and therefore can be used to identify that person across different channels.|
|Phone (E.164)||A namespace that represents raw phone numbers that need to be hashed in E.164 format. The E.164 format includes a plus sign (
|Phone (SHA256)||A namespace that represents phone numbers that need to be hashed using SHA256. You must remove symbols, letters, and any leading zeroes. You must also add the country calling code as a prefix.|
|Phone (SHA256_E.164)||A namespace that represents raw phone numbers that need to be hashed using both SHA256 and E.164 format.|
|TNTID||A namespace that represents Adobe Target. See the following document on Target fore more information.|
|Windows AID||A namespace that represents a Windows Advertising ID. See the following document on Windows Advertising ID for more information.|
To view standard namespaces in the UI, select Identities in the left navigation and then select the Browse tab to display a list of standard identity namespaces accessible to your organization. You can sort the namespaces alphabetically by their Display name, Identity symbol, or Owner. Alternatively, you can sort the namespaces chronologically by their most recent update date.
Select a namespace to see more specific information on the right rail.
Platform also provides namespaces for integration purposes. These namespaces are hidden by default as they are used to connect with other systems, and not used to stitch identities. To view integration namespaces, select View integration identities.
Depending on your organizational data and use cases, you may require custom namespaces. Custom namespaces can be created using the Identity Service API or through the UI.
To create a custom namespace using the UI, navigate to the Identities workspace, select Browse, and then select Create identity namespace.
The Create identity namespace dialog box appears. Provide a unique Display name and Identity symbol and then select the identity type you would like to create. You can also add an optional description to further information about the namespace. When finished, select Create.
Namespaces that you define are private to your organization and require a unique identity symbol in order to be created successfully.
Similar to standard namespaces, you can select a custom namespace from the Browse tab to view its details. However, with a custom namespace you can also edit its display name and description from the details area.
Once a namespace has been created, it cannot be deleted and its identity symbol and type cannot be changed.
Supplying the namespace for an identity depends on the method you use for providing identity data. For details on providing data identity data, please see the section on supplying identity data in the Identity Service overview.
Now that you understand the key concepts of identity namespaces, you can begin to learn how to work with your identity graph using the identity graph viewer.