Update 24A
Revision History
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
| Date | Module | Feature | Notes |
|---|---|---|---|
| 08 MAR 2024 | Created initial document. |
The table includes a chronological listing of document changes.
Overview
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 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.
Feature Summary
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 |
|
||
New Attributes for Deliverability Status Reason and Deliverability Status Change Date |
||||||
Responsys Android Support for Firebase Cloud Messaging (FCM) - HTTP V1 API |
||||||
"From Name" Attributes available in Email Campaign Performance Report |
||||||
Responsys Campaign Management
Data
New Attributes for Deliverability Status Reason and Deliverability Status Change Date
Data Directors may now review the reason for a recipient’s latest Deliverability Status change and the date of latest change without reviewing the Contact Event Data (CED) output. This information is visible via new List attributes for Deliverability Status Reason and Deliverability Status Change Date. These are available for Email, SMS, mobile apps, and Web Push channels.
Similarly, a new Permission Status Change Date attribute exists for the Email channel and the SMS channel. The Permission Status Date attribute already existed for mobile apps and Web Push channels.
Date values are stored in the pod’s database time zone. The data viewer displays the value in the account’s time zone.
The new attributes are:
- Profile List (Email and SMS)
- EMAIL_DELIVERABILITY_REASON_
- EMAIL_DELIVERABILITY_DATE_
- EMAIL_PERMISSION_DATE_
- MOBILE_DELIVERABILITY_REASON_
- MOBILE_DELIVERABILITY_DATE_
- MOBILE_PERMISSION_DATE_
- App Channel List (mobile apps) and Web Push List
- CHANNEL_DELIVERABILITY_REASON_
- CHANNEL_DELIVERABILITY_DATE_
More efficient insights into deliverability changes.
Steps to Enable
You don't need to do anything to enable this feature.
Access Requirements
This enhancement is available to all accounts with the 24A Update.
Mobile
Responsys Android Support for Firebase Cloud Messaging (FCM) - HTTP V1 API
Google deprecated FCM legacy V1 APIs on June 20, 2023. Responsys Android now supports delivering mobile app push notifications using Google Firebase’s FCM V1 API.
Steps to Enable
Upload the FCM HTTP V1 key file in JSON format for Android App in App Developer Console.
Tips And Considerations
App developers should upgrade the existing Android mobile apps in Responsys to the HTTP V1 API by providing the FCM HTTP V1 key file in JSON format. App developers don’t need to change the Android app code/config to upgrade to FCM HTTP V1.
When new Android apps are created in Responsys, they must be created using the FCM HTTP V1 key file, as Firebase Legacy APIs are deprecated and will be discontinued from June 1, 2024. When app developers upgrade the Android platform to FCM HTTP V1 API for existing apps, they should thoroughly test the push notification features.
NOTE: All customers must upload their updated JSON and adopt the FCM HTTP v1 API before June 1, 2024.
Key Resources
For more information, visit the Responsys Firebase documentation.
Access Requirements
This enhancement is available to all accounts with the 24A Update
Program
Prepare Mobile Push and Web Push Campaigns in Advance
Responsys Program's Prepare Campaign stage now supports Mobile Push Campaigns and Web Push Campaigns.
- This feature enhances the push messages construction ahead of time to ensure they are ready for delivery at the specified time.
- You can proceed with either a Send Mobile Push Campaign or a Send Web Push Campaign stage after preparing the campaign.
- This enhancement improves campaign send time throughput by optimizing audience creation and caching during the preparation stage.
- It is particularly useful for campaigns that need to be sent at specific times, such as flash sales.
- Ensure that you specify the same campaign in both the Prepare Campaign and Send Push/Web Push Campaign stage
Allowing for more efficient and proactive campaign preparation and execution.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
For more information, please visit our Responsys Help Center: Program > Prepare Campaign content.
Access Requirements
This enhancement is available to all accounts with the 24A Update.
Reporting
"From Name" Attributes available in Email Campaign Performance Report
Marketers can now include "From Name" Attributes (From Name, From Address, From Address Domain) as columns to review Email Campaign Performance in Interactive Dashboards.
- From Name, From Address, From Address Domain attributes are hidden by default, but it is now possible to add them to the Email Campaign Performance Report in Interactive Dashboards.
Greater flexibility in reporting
Steps to Enable
You don't need to do anything to enable this feature.
Access Requirements
This enhancement is available to all accounts with the 24A Update
Event Flow Application: Push / Email Now Supported
Previously only supported for SMS, Responsys real-time event streaming service has been extended to email and push channels now.
With this service Responsys can stream channel event data in near real-time to any consumer application (built at customer’s end). The service is configurable where-in the customer can determine which specific events and specific attributes from those events, they want streamed to their system.
Capture real-time data that matters most.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
Please raise an SR with Oracle Support and they will share a guide for consumer side implementation.
Access Requirements
Only available for customers who are on OCI.
Web Push
CRUD APIs
Introducing Web Push CRUD APIs for Responsys Web push channel! Seamlessly create, read, update, and delete web push campaigns. Now aligns with existing Campaign CRUD APIs (SMS, Push, Email channels), ensuring a seamless management of Responsys Web Push campaigns alongside other campaign types:
- APIs:
- Create Web Push Campaign
- Retrieve Web Push Campaign
- Retrieve All Web Push Campaign
- Update Web Push Campaign
- Delete Web Push Campaign
- Retrieve All Web Push Apps
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
This enhancement is available to all accounts with the 24A Update
Storing Notification Preferences
Introducing a preference storage mechanism for Web Push channel via Preference PETs for Responsys Web Push channel.
- When you create a web push channel list and Preference PET will be auto generated and associated with the newly created web push channel list.
- setNotificationPreference – new SDK method that web developers can use to set web visitor's notification preferences in Responsys Web Push Preference PET
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
For existing Web Push channel lists, please contact Oracle Support.
Access Requirements
Available for all accounts
Web Push Support for Safari Browser
Extending Responsys Web Push support for Safari browser in MacOS (Ventura or higher), iOS and iPadOS (16.4 or higher)
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
-
Safari has included the requirement of a user gesture before a push notification prompt could be displayed. Hence, if lazy flag is “false”, native default prompt will not appear in Safari browser when the website loads. Web developers need to implement lazy registration and explicitly call the Responsys JS SDK registration method to show permission prompt in Safari browser.
-
Web push notifications on iOS works differently compared to Android and Apple has introduced following pre-requisites for web push notification in iOS and iPadOS devices
- Must be on iOS or iPadOS 16.4+
- The web app must be served alongside a web application manifest file with the display setting as either “fullscreen” or “standalone”
- The web app is added to the user's Home Screen
- Web app user will have to initiate an action on the website/Home Screen web app to display permission prompt
Access Requirements
Available for all accounts