Oracle Help Center | Oracle Responsys Mobile App Platform Cloud Service title

What's New

To make it easier for you to discover what's new with the SDK, this topic contains information about new features in recent updates and where to find more information about them.

Changes and enhancements for Responsys Update 19C

Added support for Android App Links. Android App links enables Email Marketers to deep link their Android end users in a standard, seamless and secure manner into their Android Apps. Similar to the existing support for Oracle Responsys iOS Universal Links, some of the highlights of this feature include:

See the Android App Links guide for more information.

Support for Multiple Push SDKs in one App

Integrate and use the Responsys Push SDK in your App even if your App already uses multiple other Push SDKs. Release 19C onwards, we provide a solution that Apps can implement to enable co-existence of Responsys Push SDK with multiple Push SDKs within the same app.

For more information, see the platform specific topics:

Documentation enhancements of note

The Universal Links guide has been added to the help center.


Changes and enhancements for Responsys Update 19B

Authentication Key Support for iOS Apps

Responsys now supports Authentication Key Credentials for iOS Apps. The key advantage of using Authentication Key Credentials over .PEM files is that unlike .PEM files, Authentication Keys do not expire. Learn more

App Icon Badges for Message Center

App Icon Badges are supported through Message Center messaging Campaigns. Marketers can display a Badge Count on the App Icon on an end user's device to indicate to the app user the number of new Message Center messages available. Marketers can Increment the Badge Count for every message sent to user's device. App Icon Badging with Message Center Messages can drive increased app user engagement rates.

For more details, see the App Icon Badges section for your platform:

Same App for Multiple Accounts

You can now use one Responsys app across multiple Responsys account. Previously, Responsys apps were restricted to a single Responsys account.

Responsys accounts may use a single app across multiple Brands or Geographic Regions. If you have multiple accounts in Responsys (each corresponding to a separate brand, organization, or geographic region) but have a single app that is used for each of these brands, organizations, or regions, you will now be able to configure and use the same app in each of your Responsys accounts.

At any given time an app user will be associated with only one of your Responsys Accounts. When an app user switches the brand, organization, or region on the app, they will be disassociated from the current Responsys account and associated with another of your other Responsys accounts.

NOTE: This feature is available under our Controlled Availability program. To request access to this feature, please contact your Customer Success Manager or log in to My Oracle Support and create a service request.

For more details, see the platform specific topics:

Support for AndroidX Libraries

The Responsys Android SDK (Release 19B / Version 6.41.0 onwards) supports AndroidX libraries. Apps using AndroidX libraries instead of Android Support libraries, can use the PushIO SDK with Jetifier enabled in the gradle.properties file.

In the gradle.properties file add the following:

    android.useAndroidX=true
    android.enableJetifier=true

Responsys to deprecate TLS 1.0 & 1.1 on June 1, 2019

Oracle is updating Responsys application security mechanisms to meet modern security requirements. On June 1st, 2019, Responsys will no longer allow inbound connections using TLS 1.0 and TLS 1.1 protocols. Responsys will continue to support inbound connections using the TLS 1.2 protocol.

Because Responsys already supports modern browsers that support TLS 1.2, there should be no impact on Responsys users. However, any Internet connections made to Responsys from browsers or external applications using TLS 1.0 or TLS 1.1 will fail. For example, if a consumer uses an older browser not supporting TLS 1.2 to open a Responsys-generated email message, that message may not get rendered properly. Please note that Responsys will not generate any error or warning messages in response to an incoming request using TLS 1.0 or TLS 1.1 protocols.

For APIs and App access, verify that all applications accessing Responsys, including custom apps, support TLS 1.2. If your application does not support TLS 1.2, it will not be allowed to establish a connection to Responsys. In the event that your application does not use TLS 1.2, it will need to be updated to allow connections via a supported protocol.

Learn more


 

Changes and enhancements for Responsys Update 19A

19A Responsys Push SDK version 6.40.0

The 19A Responsys Push SDK version 6.40.0 will be available from the download page following the deployments of the Responsys Update 19A to all pods. This release will support Oracle Responsys Update 19A features. We recommend that customers use the latest SDK version, but there is no need to upgrade if the SDK updates are not applicable for your mobile app.

For details about obtaining and using the latest released SDK version, see the Upgrade Guide sections for your platform:

REMINDER: Upgrade your Android Mobile App to an FCM-compliant version of the Responsys SDK

If you have not already done so, Oracle strongly recommends that you update your Android mobile apps to an FCM-compliant version of the Responsys SDK immediately. This will give your Android app users enough time to upgrade to your FCM-compliant mobile app before Google's April 11, 2019 deadline.

To upgrade your mobile app to use FCM:

For more details, see the section below about upgrading your Android app to a FCM-compliant version of the Responsys SDK.

Geofence and Beacon Events API

Responsys now supports geofence and beacon events. The Responsys Push SDK has added a set of open APIs that enable app developers to raise entry and exit events for geofences and beacons. You can integrate with a geofence/beacon solution of your choice, or integrate with a native geofence/beacon solution.

Once implemented, marketers will be able to use geofence and beacon events in their program orchestrations in Responsys. These location-based events will be triggered when a mobile device user enters or exits a geofence or beacon zone.

To enable this feature:

Learn more:

For more details, see the Geofences and beacons section for your platform:

See the following topics in the Responsys Help Center for more information:

mParticle Kit for Responsys SDK

The Oracle Responsys Push SDK now supports an integration with mParticle through iOS and Android mParticle Kits, which serve as an integration layer between the Responsys and mParticle SDKs. If you use mParticle as a Customer Data Platform (CDP), this integration will enable you to forward events to mParticle for further analysis and processing.

To enable this integration: Follow the instructions found at the following locations:

Oracle Responsys - mParticle SDK Integration Resources

Responsys users with the Mobile Apps Analytics Manager role have access to two new Interactive Dashboards for Push and In-app campaigns:

View the Bounce Analysis Dashboard and Deliverability Trends Dashboard topics in the Oracle Responsys Help Center to learn more.

Reporting update: Custom reports for mobile apps

For customers who require custom reporting capabilities, Interactive Dashboards Plus is now available for the mobile apps channel and supports push notifications and in-app messages.

To enable this feature:

View the Custom Reports in Dashboards Overview topic in the Oracle Responsys Help Center to learn more.

Support for conversion window for push conversions from mobile apps

Responsys already supports a Push Conversion event, which attributes conversions inside the app to the push campaign that led the app user into the mobile app. In 19A, this has been enhanced to allow mobile app developers and marketers to define the conversion window for push conversion events that occur from within the mobile app.

Marketers and mobile app developers will be able to define the concept of a conversion window that is applicable for their business. For example, they could define the conversion window to log a conversion only if the mobile app user makes the conversion within a certain number of days of opening the push notification. They could also define the conversion window such that a conversion is logged only once for every push notification opened.

To enable this feature: You must integrate your mobile app with the 19A Responsys Push SDK (version 6.40.0) when it becomes available. You must also modify your mobile app code as needed to define your custom conversion window or to ensure that a conversion is logged only once.

Learn more:

For more details, see the Engagements & Push Conversions section for your platform:

Support for titles in Push notifications

In the 19A update, we have made an enhancement that allows marketers to design and launch push notification campaigns with titles. Marketers can use the title to compose more contextual push notifications. Such notifications catch the mobile app user's attention more effectively and can lead to better campaign performance.

Marketers can access the Title field by opening the Settings dialog located on the Responsys Push Message Designer page. The Title field supports personalization and emojis.

To enable this feature:


 

Mobile App Customers: Upgrade your Android Mobile App to FCM-compliant Responsys SDK version 6.38.1 or later

Recently, Google has made some changes to their current push messaging infrastructure that will require immediate action for all of our Mobile App users. To ensure your Mobile App messaging is working as intended, we encourage you to upgrade your Android mobile app to FCM-compliant Responsys SDK version 6.38.1 or later. To help you through the upgrade, we have provided some additional details and FAQs below.

Why is this upgrade required?

Responsys and all other push messaging solutions rely on Google servers and infrastructure to deliver push notifications to Android devices.

Google has deprecated their current push messaging infrastructure, Google Cloud Messaging (GCM). Google will remove the GCM client and server APIs as soon as April 11, 2019. Google is replacing GCM with Firebase Cloud Messaging (FCM) infrastructure. All push messaging solutions must upgrade to FCM, so that they will keep receiving push notifications on Android apps.

See Time to Upgrade from GCM to FCM for the official Google communication on this upgrade.

Is Responsys SDK compliant with FCM?

The Responsys Android SDK is FCM compliant as of SDK version 6.38.1, released on October 4, 2018.

How do I upgrade my mobile app to use FCM?

By when do I need to upgrade my mobile app?

Oracle recommends that you complete the mobile app upgrade immediately. This will give your Android app users enough time to upgrade to your FCM-compliant mobile app before Google's April 11, 2019 deadline.

If your Android Mobile app users have not upgraded to your FCM-compliant mobile app by April 11, 2019, they will not receive push notification from Responsys after April 11, 2019.

NOTE: Along with the SDK upgrade, it is also important to migrate your existing GCM (Google Cloud Platform) project to Firebase. Kindly refer to our guide Get FCM Credentials for more details on this.


 

Changes and enhancements for Responsys 18D

PushIO SDK 6.39.0

PushIO SDK 6.39.0 will be available from the download page. This release supports Oracle Responsys 18D features. We recommend that customers use the latest SDK version, but there is no need to upgrade if the SDK updates are not applicable for your mobile app.

The 6.39.0 SDK will include the recent 6.38.1 SDK update for Android. The 6.38.1 SDK update added support for FCM, and it fixed an issue with In-app message window force-close in some cases.

For details about obtaining and using the latest SDK version, see the Upgrade Guide sections for your platform:

Redesigned In-app Backend feature for supporting In-app campaigns

Oracle Responsys and the SDK have changed how In-app Messaging works for mobile apps built with the 6.39.0 and later SDK. Customers enabled for this feature can realize the following benefits:

Implementation guidelines: If your organization has not yet integrated In-app Messaging and plans to implement a new In-app Messaging integration in its mobile app OR if your organization has already integrated In-app Messaging and are updating to SDK version 6.39.0 or later, you must use the "Redesigned In-app Backend" feature.

To enable this feature:

  1. Request access to the "Redesigned In-app Backend" feature by contacting your Customer Success Manager or logging in to My Oracle Support and creating a service request.

  2. You must build your mobile app with the 18D/6.39.0 SDK or greater.

  3. You must turn on the feature in your code, using the SDK's setInAppFetchEnabled method.

Note for customers updating their mobile apps: If you update your mobile app to SDK version 6.39.0 or later but do not enable the "Redesigned In-app Backend" feature in your app, then this will impact your marketers' ability to target all mobile app users immediately once you finally enable the "Redesigned In-app Backend" feature. Mobile app users will have to update their app to the app version that implements "Redesigned In-app Backend" feature before In-app Messages can be delivered to them.

For more details, see the In-app section for your platform:

Message Center Direct

Mobile app marketers will now have access to a new Mobile App campaign format, Message Center. The Message Center Campaign Designer will enable marketers to send messages directly to the Message Centers in the mobile app used by the recipients, without requiring an accompanying Push notification. This enables marketers to launch Message Center campaigns to mobile app users, even if users have opted-out of receiving Push notifications. Currently, mobile apps fetch Message Center messages at 2-hour intervals, so marketers will find it best suited for communications that are not time-sensitive.

To enable this feature:

  1. Request access to this feature by contacting your Customer Success Manager or logging in to My Oracle Support and creating a service request. This feature is currently released under our Controlled Availability program.

  2. For best results and performance of Message Center, your mobile app must use the Oracle Responsys Mobile App Platform Cloud Service SDK version 6.39 (18D) or later. The 6.39 version of the SDK contains key bug fixes for this feature. Oracle recommends that your mobile app always use the latest SDK.

  3. You must turn on Message Center in your code, using the SDK's setMessageCenterEnabled method. This applies even if you are already using SDK 6.37.0 or later OR are upgrading from an older SDK version to SDK version 6.39.0 or later.

For more details, see the Message Center section for your platform:

Recording Push Notification Permission Status in Responsys for Android app users

The Android SDK now captures Push Notification Permission Status for mobile app users and communicates it to Responsys. This ensures that for each app installation on an Android device, the latest Push Notification Permission Status is reflected in the CHANNEL_PERMISSION_STATUS_ column of the App Channel List.

Whenever a Device Registration is sent from the SDK to the Responsys Platform, the latest Push Notification Status is captured in the App Channel List for the Device Record.

To enable this feature, you must update your mobile app to the 18D / 6.39.0 SDK.


 

Changes and enhancements for Responsys 18C

PushIO SDK 6.38.0

PushIO SDK 6.38.0 will be available from the download page. This release supports Oracle Responsys 18C features. We recommend that customers use the latest SDK version, but there is no need to upgrade if the SDK updates are not applicable for your mobile app.

For details about obtaining and using the latest SDK version, see the Upgrade Guide sections for your platform:

New Standard Interactive Notifications available

Marketers now have access to 17 new Standard Interactive Notifications when they create Push campaigns. For the interaction buttons to be present in a Push notification, the mobile app associated with the campaign must be built with the 18C/6.38.0 SDK or greater.

For more details, see Interactive Notifications.

Mobile App Console Test Push supports multiple device IDs

You can now send a single test push from the Mobile App Console to up to 10 device IDs. For details, see the Test Apps topic.

SDK crash reporting

The SDK is capable of reporting crashes that happen within the SDK back to Responsys. This feature is enabled by default. You can use the setCrashLoggingEnabled method to disable or enable this feature.

For more details, see the Debugging & Logging sections for your platform:


 

Changes and enhancements for Responsys 18B

PushIO SDK 6.37.0

PushIO SDK 6.37.0 will be available from the download page. This release supports Oracle Responsys 18B features. We recommend that customers use the latest SDK version, but there is no need to upgrade if the SDK updates are not applicable for your mobile app.

For details about obtaining and using the latest SDK version, see the Upgrade Guide sections for your platform:

Important Updates to Mobile App Message Center

The Oracle Responsys Mobile App Cloud Platform SDK (Push SDK version 6.37.0 onward) retrieves "Message Center" messages from Responsys at fixed intervals every time a mobile app is launched. The Push SDK stores retrieved messages locally, and they are served from the local storage on the device to your mobile app on demand.

For more details, please refer to the following topics:

NOTE: Message Center messages may affect choices Marketers make in designing and editing Rich Push campaigns. Most Push Campaigns will not be affected by this, but Marketers should review the Mobile App Channel Configuration Guide for more information.

Cross-channel Conversion Tracking

Conversion tracking enables marketers using Responsys to evaluate how effective their marketing campaign is in driving a particular post-clickthrough action, such as making a purchase. With the Cross-Channel Conversion Tracking feature, Responsys extends its conversion tracking functionality, so that marketers can attribute conversions that occur in your mobile app to an email campaign.

For example, consider a "freemium" health and fitness mobile app that monetizes by having customers upgrade to a 'premium' version. The company sends email campaigns to customers to highlight the benefits of the premium service and then routes them to their mobile app, where customers are prompted to upgrade. When the customer does upgrade, this upgrade is then tied back to the email campaign that prompted the upgrade.

For Cross-Channel Conversion Tracking to work, Marketers create email campaigns that contain deep-linked URLs to their organization’s mobile app. The mobile app must be configured to record the click, wait for the conversion action, and then send the conversion to Responsys. With this feature, conversions on email campaigns (via deep linked URLs to mobile apps) that happen on a mobile app are now attributed to the email campaign. Marketers can view these conversion metrics in Interactive Dashboards, using the Browser Types report for the email campaign.

Mobile app developers must modify the mobile app to support Cross-channel Conversion Tracking. For more details, please refer to the following topics:


 

Changes and enhancements for Responsys 18A

New naming convention for Oracle Responsys quarterly updates

Beginning in 2018, Oracle Responsys is adjusting our terminology for quarterly product updates. Releases, which will now be known as "updates", will use the calendar quarter and the year to refer to the quarterly update.

For example, the first quarterly update in 2018 will be referred to as: Oracle Responsys 18A.

In addition, readiness material is published on the cloud.oracle.com site, providing a preview of new and changed functionality available in our latest updates.

NOTE: All pre-existing SDKs and documentation will continue to use the former 6.x numbering system and nomenclature. The SDK versions will retain the 6.x numbering system. All future documentation will include the new nomenclature where appropriate.

PushIO SDK 6.35.0

PushIO SDK 6.35 is available from the download page. This release supports Oracle Responsys 18A features. We recommend that customers use the latest SDK version, but there is no need to upgrade if the SDK updates are not applicable for your mobile app.

For details about obtaining and using the latest SDK version, see the Upgrade Guide sections for your platform:

NOTE: Although the Oracle Responsys product has adopted a new naming convention for its quarterly product updates, the SDK versions will retain the 6.x numbering system. However, the PushIO SDK version may skip numbers in its version naming sequence. For example, the SDK version moved from 6.33.0 to 6.35.0 in 18A, and it is 6.37.0 in 18B.

Interactive Notifications

When Marketers design Push Campaigns in Responsys, they now have an option to add greater interactivity to their Push Notifications through Interactive Notifications. Interactive Notifications enable Marketers to add actionable buttons to their Push Notifications, and they allow mobile app users to interact with Push notifications.

If you need buttons other than those provided in the Standard Interactive Notifications, Responsys supports adding Custom Interactive Notifications for mobile apps. Mobile app developers must define Custom Interactive Notifications in their mobile app code using the Mobile App SDK and must configure them for the app using the Mobile App Developer Console.

To learn more about implementing this feature for your mobile app, see Interactive Notifications.

When Responsys Link Tracking is used on calls-to-action in Rich Push and In-app message creatives, mobile app users are bounced off the browser and taken to the destination URL when they click the calls-to-action. This results in a poor user experience for the mobile app users.

The new feature "Customized User Experience for Links and Calls-to-action in Rich Push, In-app Messages" gives Mobile App Developers more control of how these links are handled. For example, if you want these links (including HTTP web links) to all be displayed within the mobile app, you can now do so. You can also fix the user experience of being bounced off a browser before being taken to a destination URL.

To learn more about implementing this feature for your mobile app, see Customized UX for destination URLs.