This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Product | Feature | Notes |
|---|---|---|---|
| 27 JAN 2022 | Created initial document. |
HAVE AN IDEA?
We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at omcdocumentation_ca@oracle.com.
DISCLAIMER
The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.
This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.
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 |
|
||
Activation Snapshot with The Oracle Audience Segmentation API |
||||||
View Summary and Errors While Ingesting Data with The Audience Segmentation API |
||||||
Activation Snapshot with The Oracle Audience Segmentation API
The Activation Snapshot feature helps you track the customers who have already been targeted for a campaign by creating a "snapshot" of the campaign and saving the data after the campaign runs.
Using the Activation Snapshot allows you to use the saved data to make marketing decisions, such as suppressing communication to customers that have been targeted recently.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
To use Activation Snapshots, you must create a campaign in the Audience Segmentation platform and then make further configurations using the Audience Segmentation API.
Key Resources
- Activation Snapshots from the Oracle Audience Segmentation Developer Help Center.
Role Information
This feature is available to Data masters.
The Data Deletion Job with The Audience Segmentation API
Using the Data Deletion job, you can delete customer data from the Audience Segmentation data model.
This gives you a way to comply with requests from customers to delete their data.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
To configure and manage Data Deletion jobs, you will need to use the Audience Segmentation API.
Key Resources
-
Data Deletion Jobs from the Oracle Audience Segmentation Developer Help Center
Role Information
This feature is available to Data engineers.
View Summary and Errors While Ingesting Data with The Audience Segmentation API
You can view a summary of the records and any errors for ingested data.
This gives you an efficient way to view and debug issues that occur during data ingestion.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
To view ingest job summaries and errors, you will need to use the Audience Segmentation API.
Key Resources
- Ingesting data using the Near real time ingestion API from the Oracle Audience Segmentation Developer Help Center.
Role Information
This feature is available to Data engineers.
Amazon Web Services (AWS) Outbound Connector
The AWS outbound connector allows you to export data from Oracle Audience Segmentation to an AWS S3 bucket.
The connector gives you a quick and seamless option to export data to your AWS S3 bucket.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
Role Information
This feature is available to Data engineers.