This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Feature | Notes |
|---|---|---|
| 27 JUN 2019 | Created initial document. |
This document outlines the features in Oracle Adaptive Intelligent Apps for Customer Experience and describes any tasks you might need to perform for this service. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Give Us Feedback
We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_aiapps_doc_feedback_grp@oracle.com.
Column Definitions:
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
| Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Customer Must Take Action before Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
|---|---|---|---|---|---|---|
| Feature |
Report |
UI or |
UI or |
|
||
Oracle Adaptive Intelligent Apps for Customer Experience provides personalized, dynamic, and continuously adaptive offers across B2C commerce and marketing platforms. It delivers the product recommendations and promotions through commerce storefronts and marketing channels.
Email Strategies for Also Bought and Trending
Use the Also Bought strategy for email widgets where you want to display other products that consumers most often bought together with the product of interest. Use the Trending strategy for email widgets where you want to display other products that have a recent increase in popularity. Each of these strategies can improve the chances that the shopper receiving the email returns to your store and makes an additional purchase.
This screen capture shows the new list where you can select these strategies. To use the default personalization algorithms, select None (Default).
Email Widgets Page Showing Strategies
The Also Bought and Trending strategies for email widgets use simple algorithms with no personalization. If you want to use personalization along with a strategy, you can apply the strategy as a product filter with the default personalization. Applying a strategy returns personalized results filtered by the rules of the strategy.
To apply a strategy as a product filter, select None (Default) as the widget strategy, and then insert the product filter parameter in the code similar to these examples:
&pf=${"strategy": "alsoBought", "id:", "product-123"}
&pf=${"strategy": "trending", "minPrice:", 0.99, "minOrders": 4, "range": "WEEK"}
See Email Template Code for more information about URL parameters.
Steps to Enable
You don't need to do anything to enable this feature, even if you already use email widgets. Any existing email widgets are already set as having no strategy, which is the default for using the personalization algorithms.
To use these new strategies, follow the steps in Configure Email Widgets.
Tips And Considerations
- When you select a strategy, the code snippet that you copy updates to point to the appropriate REST API endpoint. For example, the default personalization algorithm uses the offers/widget/email/${SITE_ID} endpoint, whereas the Also Bought and Trending strategies use the offers/widget/email/${SITE_ID}/ab and offers/widget/email/${SITE_ID}/tr endpoints.
- The pid URL parameter is applicable only to the Also Bought strategy to identify the product that the algorithm is based on.
- If you’re using the REST API, refer to the Change History for this update to see the resources and methods added for this feature.
Key Resources
Oracle Adaptive Intelligent Apps for Customer Experience provides guidance for salespeople to increase their win rates with data-driven pipeline management and recommendations for the next best sales action. Salespeople benefit from advanced machine-learning techniques to optimize customer engagement.
Summary of Ingested Data to Monitor Data Processing
Use the Summary tab to know the volume of data ingested and troubleshoot any issues that are flagged in the data processing status report. Compare the number of different entities ingested with the total data size in Oracle Engagement Cloud to ensure that your application is receiving data as expected.
This screenshot shows the Summary tab in the Data Processing Status page.
Data Processing Status Summary Page
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources