


For example, the profile of a product may include a SKU and description, whereas the profile of a person contains information like first name, last name, and email address. Record dataĪ profile is a representation of a subject, an organization or an individual, composed of many attributes (also known as record data). Therefore, the total number of profile fragments within Platform is likely to always be higher than the total number of merged profiles, as each profile is typically composed of multiple fragments from multiple datasets.

When the data from multiple datasets conflicts (for example one fragment lists the customer as “single” while the other lists the customer as “married”) the merge policy determines which information to prioritize and include in the profile for the individual. In other words, profile fragments represent a unique primary identity and the corresponding record or event data for that ID within a given dataset. When these fragments are ingested into Platform, they are merged together in order to create a single profile for that customer. For example, if a customer interacts with your brand across several channels, your organization will have multiple profile fragments related to that single customer appearing in multiple datasets. Profile fragments vs merged profilesĮach individual customer profile is composed of multiple profile fragments that have been merged to form a single view of that customer.
#Adobe revel customer service how to
To learn how to access and work with the Profile dashboard in the UI, and detailed information regarding the metrics displayed in the dashboard, refer to the Profile dashboard UI guide. The Experience Platform UI provides a dashboard through which you can view important information about your Real-time Customer Profile data, as captured during a daily snapshot. For more information, including a list of guidelines and example use cases, please read the Profile guardrails documentation. This includes soft limits that will result in performance degradation, as well has hard limits that will result in errors and system breakages.

#Adobe revel customer service series
Profile guardrailsĮxperience Platform provides a series of guardrails to help you avoid creating Experience Data Model (XDM) schemas which Real-time Customer Profile cannot support. The Profile store uses a Microsoft Azure Cosmos DB infrastructure and the Platform Data Lake uses Microsoft Azure Data Lake storage. The Profile store is separate from catalog data in the data lake and Identity Service data in the identity graph. Profile data storeĪlthough Real-time Customer Profile processes ingested data and uses Adobe Experience Platform Identity Service to merge related data through identity mapping, it maintains its own data in the Profile data store. Since dimensional and B2B entities only exist outside the primary entity, these are only used for batch segmentation.
