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 |
|---|---|---|---|
| 05 APR 2021 | Mobile | Custom Handling of Deep Links in Push Campaigns by Apps | Updated document. Revised feature information. |
| 05 APR 2021 | Mobile | Rich Push Web Views for Apps with Splash Screens | Updated document. Revised feature information. |
| 12 NOV 2020 | Campaigns | Campaign Validation | Updated document. Revised feature information. |
| 23 SEP 2020 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update. All Oracle Responsys updates are conducted without disruption to service, meaning no downtime.
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. We frequently update this document so don’t forget to check back and get the latest information.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at omcdocumentation_ca@oracle.com.
Column Definitions:
Features Delivered Enabled
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. |
Action is Needed 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 |
|
||
Subject Line Predictions are now also supported for Japanese, Chinese and Hebrew subject lines.
The predict option is now available if less than 3 words are typed in the subject line.
Steps to Enable
This feature is available as part of the Advanced Intelligence Package add-on that must be ordered for your account. Please contact your account manager or Oracle sales.
Key Resources
- Visit our Help Center to learn more.
Mobile phone numbers are now validated to conform to the E.164 format if this format is specified in REST API requests using either the Merge Trigger SMS or the Trigger SMS Message endpoints.
Oracle Responsys recommends using E.164 format, an internationally-recognized standard phone number format that will help ensure deliverability of SMS messages across the globe.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Visit our Help Center to learn more about Trigger Email and Trigger SMS message endpoints.
Program Web Services Manager Role
A new Program Web Services Manager role is now available.
Users with this role can access and manage all APIs related to Programs.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Visit our Help Center to learn more.
Responsys Event Notification (REN) Enhancements
Query attributes for Responsys Event Notifications are now supported. The query attributes can be set in the Filters section of the payload, along with EventTypes.
You can filter event payloads and receive callbacks only when the query attribute is met.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
The Responsys Event Notification (REN) service add-on is required to use this feature. REN is currently released under our controlled availability program.
Key Resources
- Visit our Help Center to learn more.
The following new standard REST APIs are now available:
- Get Campaign Proof List: Enables you to retrieve the proof list associated with a campaign.
- Update Campaign Proof List: Enables you to update a campaign's proof list.
The following REST APIs were enhanced:
- Hashed Email Support, Email Trigger: Enables you to send ohashed email addresses, using MD5 and SHA256 encoding, to trigger an email.
- Hashed Email Support, SMS Trigger: Enables you to send ohashed email addresses, using MD5 and SHA256 encoding, to trigger an SMS.
Added and enhanced REST APIs enable you to use more of the Responsys platform capabilities programmatically.
Steps to Enable
Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.
Key Resources
- Visit our Help Center to learn more.
Role Information
Client applications that use the Responsys REST APIs must authenticate as an API user with the applicable Web Services Manager roles enabled.
Warnings are now displayed when two columns of the same name are used in data sources.
Not using unique names may result in personalization issues.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Make sure the field names you use for personalization are unique across data sources. Duplicate columns from different data sources with different values can result in missing personalization in campaign messages. Choosing two field names with the same name will prompt a warning message in the validation section. If these columns have the same set of values, this will not be an issue. However, when a supplemental data source is used as a look-up table, those columns may have duplicate names, and will not cause a personalization error. You can ignore the warning message in this instance.
Key Resources
Visit our Help Center to learn more about campaign validation:
List-unsubscribe now supports RFC8058 one-click-unsubscribe.
Supporting the RFC8058 one-click-unsubscribe standard helps prevent email software (such as email virus scanners and malware scanners) from accidentally unsubscribing recipients when you use List-Unsubscribe headers in your campaign messages. Using a List-Unsubcribe header reduces spam complaints and improves deliverability for supporting ISP email clients.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Learn more about this feature in our Help Center. Find additional information about RFC8058.
The Collaboration Process Monitor now supports multilingual processes.
Therefore, you now have control to monitor all active multi-language processes for your organizational units and take action, such as aborting the process, if necessary.
Steps to Enable
To enable this feature you need to log a Service Request (SR).
Multilingual collaboration is required to use this feature. Multilingual collaboration is currently released under our controlled availability program.
Key Resources
- Visit our Help Center to learn more.
The text for specifying the date range in behavioral simple filters has been updated to is before or equal to and is after or equal to.
A new checkbox is now available for simple behavioral filters for Mobile Push and Web Push channels to remove duplicate records returned.
It allows you to avoid sending multiple copies of the same email by filtering duplicate profile RIIDs from the filter output.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Visit our Help Center to learn more.
In the user interface, the terms whitelist and blacklist have been changed to allowlist and blocklist, respectively.
This enhancement is part of Oracle's initiative to use inclusive language in product interfaces, documentation, tutorials, and other materials.
Steps to Enable
You don't need to do anything to enable this feature.
Custom Handling of Deep Links in Push Campaigns by Apps
Apps can now intercept (on push open) the deep link URL specified in the Open URL attribute of Push campaigns and implement custom handling for these URLs.
This enhancement allows the app to ask the user if the user wants to open the URL in the app or the browser. Previously, the URL always opened in the browser.
Steps to Enable
The following are required in order to use this feature:
- Mobile app channel
- Responsys SDK 6.47.0 / 20D onwards
Tips And Considerations
This feature should be used with iOS and Android version 6.46.0 / 20D SDK onwards.
New Columns Added to App Channel Lists
Two new app channel list columns are now available:
- UNINSTALLED_AT_DATE_: data type is Date/Time Stamp
- CHANNEL_DELIVERABILITY_REASON_: data type is String / Text Field (to 255 characters).
Their values will be NULL (empty) initially, and they won’t start getting populated until after the 21A update.
This change supports future improvements to the Responsys SDK. With update 21A and onwards, you will be able to view additional information for app uninstalls:
- when (what time) an app uninstall was detected at Responsys; and
- why an app channel list record was marked as Undeliverable
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Even though these new columns will not have values populated until our next update, they will be part of the Connect Export Data job output when you export an App Channel List or App Channel List Filter as of 20D. Therefore, you may need to adjust your post-export Connect Export Data job file handling. The columns will be exported in the order that they appear in the data viewer while viewing App Channel Lists. In existing lists, the columns are appended at the end, after the APP_LOCATION_PERMISSION_ column (in the order: … APP_LOCATION_PERMISSION_, CHANNEL_DELIVERABILITY_REASON_, UNINSTALLED_AT_DATE_). In new lists, CHANNEL_DELIVERABILITY_REASON_ will be displayed after CHANNEL_PERMISSION_DATE_, and UNINSTALLED_AT_DATE_ will be displayed after INSTALLED_AT_DATE_.
Personalize Badge Count for App Icon Badging
Since the 19B update, Responsys has supported app icon badging on end user devices through both Push + Message Center and Message Center campaigns, allowing you to choose to increment the badge count for every message center message sent to an end user's device.
As of this update, in addition to the Increment Badge on App Icon option, you can specify a badge count for app icon badging. This allows you to implement a custom logic for app icon badging by either:
- personalizing the badge count for each recipient, or
- specifying a specific value for all recipients
You can also reset and clear the badge on app icons through a new option to Clear Badge on App Icon.
Using this feature, you can employ custom logic for the badge count on your apps.
Steps to Enable
The Mobile App channel and app icon badging for Message Center are required to use this feature.
In the Message Center:
- Enable Mobile App Message Center for Push Campaigns
- Enable Mobile App Message Center Campaigns
- Enable App Icon Badging for Message Center
Tips And Considerations
Important: Plan an app icon badging strategy for your app prior to launching any Push + Message Center or Message Center Direct campaigns with badging enabled:
- Plan how to clear and reset the badge count on the app icon (app developers must implement this logic)
- If you do not implement badge clearing and reset logic, the badge count on your app icon will keep increasing, which results in a poor user experience for app users
- Example: Clear and reset the badge count when the app user launches the app and navigates to the Message Center within the app.
This feature should be used with iOS and Android Version 6.41.0 / 19B SDK onwards.
Key Resources
- Visit our Help Center to learn more.
Rich Push Web Views for Apps with Splash Screens
This Responsys SDK enhancement extends the rich push format to apps that have a splash screen. App developers can use the 20D Responsys SDK enhancements to display rich push in-app web views once the app’s splash screen display is complete.
You can now launch rich push campaigns to engage app users on apps with a splash screen.
Steps to Enable
The following are required in order to use this feature:
- Mobile app channel
- Responsys SDK 6.47.0 / 20D onwards
Tips And Considerations
This feature should be used with iOS and Android version 6.46.0 / 20D SDK onwards.
Badge URL as Optional Attribute for Web Push Apps
The Badge URL is now an optional attribute for standard platform setup. You can now add a new Web Push app or edit an existing Web Push app without specifying the Badge URL attribute for the standard platform. To use the Badge Image for Web Push on Android devices effectively, you must comply with Android badge icon guidelines.
By making this parameter optional, you can get started with Web Push faster and add an Android compliant image URL once ready.
Steps to Enable
You don't need to do anything to enable this feature.
In-Product Guidelines for Web Push App and Website Setup
The following in-product guidelines are now available for web push app and website setup:
- Only one web push app and JS tag and service worker can be generated for a website domain
- The web push JS tag and service worker from one web push app should not be used on multiple websites
Guidelines are also displayed when downloading the JS tag and service worker:
- The Web Push JS tag and service worker from one Web Push app should not be used on multiple websites
- Each website domain that you want to set up Web Push on, must have its own Web Push app (own JS tag and service worker)
These guidelines will assist during Web Push app and Website Setup.
Steps to Enable
You don't need to do anything to enable this feature.
Migrating from an Existing Web Push Provider to Responsys
You can now use our migration guidelines for onboarding the Oracle Responsys Web Push Service if you already have an existing Web Push provider. You are now able to migrate from your existing Web Push provider to Responsys following these guidelines and register your opted-in user base with Responsys.
Users of Web Push providers can shift to Responsys Web Push and create more effective cross-channel marketing programs.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Visit our Help Center to learn more.
IMPORTANT Actions and Considerations
ACTION REQUIRED: RESPONSYS ANDROID PUSH SDK COMPATIBILITY WITH FIREBASE CLOUD MESSAGING SDK VERSION 20.1.1 OR LATER
Before you build your Android app with Firebase Cloud Messaging (firebase-messaging) / FCM SDK version 20.1.1 onwards you must upgrade to Responsys SDK version 6.45.0 or later due to a compatibility issue.
FCM SDK versions 20.1.1 or later are only compatible with the latest Responsys SDK version 6.45.0, which became available in early June 2020. Upgrading to FCM SDK version 20.1.1 or later before upgrading to Responsys SDK version 6.45.0 will cause Responsys Push notifications to break, and will result in the inability to obtain a Push notification token for Android apps.
We recommend that you wait to upgrade to FCM SDK version 20.1.1 (or later) in order to ensure you can continue to use Responsys Push notifications without issue.
KEY RESOURCES
- Review the Firebase Release Notes.