Real-time Customer Profile enables you to see a holistic view of each of your individual customers within Adobe Experience Platform. Profile allows you to consolidate disparate customer data from multiple channels, such as online, offline, CRM, and third party data, into a unified view offering an actionable, timestamped account of every customer interaction.
The Real-time Customer Profile API includes multiple endpoints, outlined below. Please visit the individual endpoint guides for details and refer to the getting started guide for important information on required headers, reading sample API calls, and more.
To view all available endpoints and CRUD operations, visit the Real-time Customer Profile API Reference swagger.
For a guide to working with Real-time Customer Profile data in the Experience Platform UI, please refer to the Profile user guide.
Computed attribute functionality is in alpha and is not available to all users. Documentation and functionality are subject to change.
Computed attributes are functions used to aggregate event-level data into profile-level attributes. These functions are automatically computed so that they can be used across segmentation, activation, and personalization.
Each computed attribute contains an expression, or “rule”, that evaluates incoming data and stores the resulting value in a profile attribute. These computations help you to easily answer questions related to things like lifetime purchase value, time between purchases, or number of application opens, without requiring you to manually perform complex calculations each time the information is needed. These computed attribute values can then be viewed in a profile, used to create a segment, or accessed through a number of different access patterns.
You can create, view, edit, and delete computed attributes using the
config/computedAttributes endpoint. To learn how to use computed attributes, refer to the computed attributes overview. For API operations, visit the computed attributes API endpoint guide.
Adobe Experience Platform enables real-time personalization of customer experiences by making data easily accessible on strategically located servers called “edges.” The Real-time Customer Profile API provides endpoints for working with edges through components called “projections.” This includes projection configurations to determine what data should be projected to each edge, as well as projection destinations to define where to route a projection. For detailed information on working with edge projections, please visit the projection configurations and destinations endpoints guide.
Through Adobe Experience Platform you can access Real-time Customer Profile data using RESTful APIs or the user interface. To learn how to access entities, more commonly known as “profiles”, using the API, follow the steps outlined in the entities endpoint guide. To access profiles using the Platform UI, refer to the Profile user guide.
Real-time Customer Profile data can be exported to a dataset for further processing, such as exporting audience segments for activation or profile attributes for reporting. Export jobs for audience segments are part of the Adobe Experience Platform Segmentation Service API, please read the segmentation export jobs endpoint guide to learn more. For step-by-step instructions on how to create and manage export jobs for profile attributes, please visit the export jobs endpoint guide.
When bringing data from multiple sources together in Experience Platform, merge policies are the rules that Platform uses to determine how data will be prioritized and what data will be combined to create individual customer profiles. Using the Real-time Customer Profile API, you can create new merge policies, manage existing policies, and set a default merge policy for your organization. To work with merge policies using the API, visit the merge policies endpoint guide.
To learn more about merge policies, and their role within Platform, please begin by reading the merge policies overview.
As data enabled for Profile is ingested into Experience Platform, it is stored within the Profile data store. As the number of records in the Profile store increases or decreases, a sample job is run that includes information regarding how many profile fragments and merged profiles are in the data store. Using the Profile API you can preview the latest successful sample, as well as list profile distribution by dataset and by identity namespace. To get started using the
/profilepreviewstatus endpoint, refer to the preview sample status endpoint guide.
Profile-enabled data that is ingested into Platform is stored in the Data Lake as well as the Real-time Customer Profile data store. Occasionally it may be necessary to delete a dataset or batch from the Profile store in order to remove data that you no longer require or that was added in error. This requires using the API to create a Profile System Job, also known as a “delete request”, which can be modified, monitored, or deleted if required. To learn how to work with delete requests using the
/system/jobs endpoint in the Real-time Customer Profile API, follow the steps outlined in the profile system jobs endpoint guide.
To begin making calls using the Real-time Customer Profile API, read the getting started guide then select one of the endpoint guides to learn how to use specific Profile-related endpoints. To work with Profile data using the Experience Platform UI, please refer to the Real-time Customer Profile user guide.