Real-time Customer Profile creates a holistic view of each of your individual customers, combining data from multiple channels including online, offline, CRM, and third-party data. This document serves as a guide for interacting with Real-time Customer Profile data in the Adobe Experience Platform user interface (UI).
This UI guide requires an understanding of the various Experience Platform services involved with managing Real-time Customer Profiles. Before reading this guide, or working in the UI, please review the documentation for the following services:
In the Experience Platform UI, select Profiles in the left navigation to open the Overview tab displaying the profile dashboard.
If your organization is new to Platform and does not yet have active Profile datasets or merge policies created, the Profiles dashboard is not visible. Instead, the Overview tab displays links and documentation to help you get started with Real-time Customer Profile.
The profile dashboard outlines key metrics related to your organization’s profile data.
To learn more, visit the profile dashboard guide.
Select the Browse tab to display several metrics related to your organization’s profile data. You can also use this tab to browse the profile store using a merge policy or an identity, as outlined in the next section of this guide.
In addition to these metrics, this section provides a last updated date and time, showing when the metrics were last evaluated.
The profile count displays the total number of profiles your organization has within Experience Platform, after your organization’s default merge policy has merged together profile fragments to form a single profile for each individual customer. In other words, your organization may have multiple profile fragments related to a single customer who interacts with your brand across different channels, but these fragments would be merged together (according to the default merge policy) and would return a count of “1” profile because they are all related to the same individual.
The profile count also includes both profiles with attributes (record data) as well as profiles containing only time series (event) data, such as Adobe Analytics profiles. The profile count is refreshed regularly to provide an up-to-date total number of profiles within Platform.
When the ingestion of records into the Profile store increases or decreases the count by more than 5%, a job is triggered to update the count. For streaming data workflows, a check is done on an hourly basis to determine if the 5% increase or decrease threshold has been met. If it has, a job is automatically triggered to update the profile count. For batch ingestion, within 15 minutes of successfully ingesting a batch into the Profile store, if the 5% increase or decrease threshold is met, a job is run to update the profile count.
The Profiles by namespace metric displays the total count and breakdown of namespaces across all of the merged profiles in your Profile Store. The total number of profiles by namespace (in other words, adding together the values shown for each namespace) will always be higher than the profile count metric because one profile could have multiple namespaces associated with it. For example, if a customer interacts with your brand on more than one channel, multiple namespaces will be associated with that individual customer.
Similar to the profile count metric, when the ingestion of records into the Profile store increases or decreases the count by more than 5%, a job is triggered to update the namespace metrics. For streaming data workflows, a check is done on an hourly basis to determine if the 5% increase or decrease threshold has been met. If it has, a job is automatically triggered to update the profile count. For batch ingestion, within 15 minutes of successfully ingesting a batch into the Profile store, if the 5% increase or decrease threshold is met, a job is run to update the metrics.
On the Browse tab you can view sample profiles using a merge policy or look up specific profiles using an identity namespace and value.
The Browse tab is set to the default merge policy for your organization by default. To choose a different merge policy, select the
X beside the merge policy name and then use the selector to open the Select merge policy dialog.
If there is no merge policy selected, use the selector button next to the Merge policy field to open the selection dialog.
To choose a merge policy from the Select merge policy dialog, select the radio button beside the policy name and then use Select to return to the Browse tab. You can then select View to refresh the sample profiles and see a sampling of profiles with the new merge policy applied.
The profiles that are shown represent a sample of up to 20 profiles from your organization’s profile store, after the selected merge policy has been applied. The sample profiles for the selected merge policy are refreshed when new data is added to your organization’s profile store.
To view the details of one of the sample profiles, select the Profile ID. For more information, see the section later in this guide on viewing profile details.
To learn more about merge policies and their role within Platform, see the merge policies overview.
On the Browse tab, you can use an identity namespace in order to look up a specific profile by an identity value. Browsing by an identity requires you to provide a merge policy, an identity namespace, and an identity value.
If necessary, use the Merge policy selector to open the Select merge policy dialog and choose the merge policy that you would like to use.
Then use the Identity namespace selector to open the Select identity namespace dialog and choose the namespace by which you would like to search. If your organization has many namespaces, you can use the search bar in the dialog to begin typing the name of a namespace.
You can select a namespace to view additional details or select the radio button to choose a namespace. You can then use Select to continue.
After selecting an Identity namespace and returning to the Browse tab, you can enter an Identity value related to the namespace that you selected.
This value is specific to an individual customer profile and must be a valid entry for the namespace provided. For example, selecting the identity namespace “Email” would require an identity value in the form of a valid email address.
Once a value has been entered, select View and a single profile matching the value is returned. Select the Profile ID to view the profile details.
After selecting a Profile ID, the Detail tab opens. The profile information displayed on the Detail tab has been merged together from multiple profile fragments to form a single view of the individual customer. This includes customer details such as basic attributes, linked identities, and channel preferences.
The default fields shown can also be changed at an organizational-level to display preferred Profile attributes. To learn more about customizing these fields, including step-by-step instructions for adding and removing attributes and resizing dashboard panels, please read the profile detail customization guide.
You can view additional information related to the individual customer profile by selecting another of the available tabs. These tabs include attributes, events, and the segment membership tab that shows the segments for which the profile is currently qualified.
The Attributes tab provides a list view summarizing all of the attributes related to a single profile, after the specified merge policy has been applied.
These attributes can also be viewed as a JSON object by selecting to View JSON. This is helpful for any users wishing to better understand how the profile attributes are ingested into Platform.
The Events tab contains data from the 100 most recent ExperienceEvents associated with the customer. This data could include email opens, cart activities, and page views. Selecting View all for any individual event provides additional fields and values captures as part of the event.
Events can also be viewed as a JSON object by selecting to View JSON. This is helpful for understanding how events are captured in Platform.
The Segment membership tab displays a list with the name and description of segments to which the individual customer profile currently belongs. This list is updated automatically as the profile qualifies or expires from segments. The total count of segments for which the profile is currently qualified is shown on the right-hand side of the tab.
For more information about segmentation in Experience Platform, please refer to the Adobes Experience Platform Segmentation Service documentation.
From the main Profiles menu, select the Merge Policies tab to view a list of merge policies belonging to your organization. Each listed policy displays its name, whether or not it is the default merge policy, and the schema class that it applies to.
For more information on merge policies, see the merge policies overview.
From the main Profiles menu, select the Union Schema tab to view available union schemas for your ingested data. A union schema is an amalgamation of all Experience Data Model (XDM) fields under the same class, whose schemas have been enabled for use in Real-time Customer Profile.
For more information on union schemas, please visit the union schema UI guide.
By reading this guide, you know how to view and manage your organization’s profile data using the Experience Platform UI. For information on how to work with profile data using Experience Platform APIs, please refer to the Real-time Customer Profile API guide.