Configuring the Profile explorer
To access the Profile explorer, the following prerequisites need to be set up and configured .
Note: Oracle Unity version 21A.2 released a fix for search for special characters. To review the steps for applying the fix, visit the What's New Release Readiness update for February 2021 and go to the section Important Actions and Considerations.
Mapping Profile explorer sources
The Profile explorer highlights the different sources that contribute towards a Master Customer record. Sources can be categorized into Marketing, Sales, Service, Commerce and Offline. These source categories are mapped to different sources using source names. To map sources to different categories, you'll have to provide the source names for the records that need to be mapped. For example, the source names can be Responsys and Eloqua for the Marketing category, Sales Cloud for the Sales category, and Service Cloud for the Service category.
To set up this mapping, contact Oracle Support. In your support request, include the source names and their respective categories (Responsys: Marketing) that you would like to configure.
Configuring the Customer 360 API
The Profile explorer relies on the Customer 360 API to retrieve, search for, and display customer profiles stored in Oracle Unity. The Customer 360 API makes use of rules and sub-rules and you can configure the Customer 360 API using the Expert Config page as follows:
- Set up Data Source Views (DSVs)
- DSVs are Data Source Views. On the Detailed View of the Profile Explorer, customers can configure and view all attributes and values from any data objects of their choice in the dropdown menu provided. Learn more about setting up a new DSV to adding new data objects to the drop-down by reviewing the help topic on Configuring Customer 360 Jobs from the Oracle Unity Developer Help Center.
- Set rules and subrules
- Rules are used to facilitate searches and allow Oracle Unity to understand which attributes a user wants to perform a search on. All accounts come with a default rule, which enables you to perform a search with five attributes. Learn more by reviewing the help topic on Retrieving Customer 360 Records from the Oracle Unity Developer Help Center.
- Subrules are used to configure the values that Oracle Unity returns for the matching information for a search.
Configuring intelligent attributes
You will have to make sure that the intelligent attributes that the Profile explorer uses are correctly configured to ingest accurate data so that you can view the data for customer profiles.
The key metrics along the top of the profile uses the following intelligent attributes from the OrderItemCube:
- Average Order Value (AOV)
- Customer Lifetime Value (CLTV)
- Total Orders (total_order_count)
- Days since last purchase (days_since_last_purchase)
Within the Transactional tab, the following intelligent attributes from the OrderItemCube are used:
- Top product
- Top product category
- Total purchase count
- Total return count
- Most popular day
- Most popular month
Within the Behavioral tab, the following attributes from the EventCube are used:
- Click rate
- Email open rate
- Days since last opened
- Days since last clicked
You will have to ensure that all the above intelligent attributes are set to “active” and that corresponding data is imported into the Order, Order Item and Event data objects.
Learn more about the Ready-to-use intelligent attributes and Managing intelligent attributes.
Running the Oracle Unity system jobs
To process the data needed for the Profile explorer, the following system jobs need to run:
- System - Data warehouse job.
- System - Identity resolution job.
- When these jobs successfully run, you need to run the System - Customer 360 job.
You can run these jobs from the Data feeds page and monitor their progress from the Jobs dashboard.
Working with the Profile explorer
Managing the Oracle Unity data model