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 |
|---|---|---|---|
| 31 MAY 2019 | Created initial document. |
This guide outlines the information you need to know about new or improved functionality in this update.
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:
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 |
|
||
Intelligent Tracking Prevention Privacy Workaround
Apple has released an updated version of its Intelligent Tracking Prevention (ITP), shipped out in the new release of Safari on MacOS and iOS devices. ITP aims to protect user privacy by restricting the ability of advertisers and other services to track people around the web. In the latest ITP 2.* versions this is done by restricting the lifetime of first-party cookies to 7 days.
As a result, visitors using Safari are no longer recognized as “returning” if more than a week has passed since their last visit. For example, if a visitor lands on a website and qualifies into a Maxymiser campaign, but doesn’t return until 10 days later, they will enter the campaign as a brand new visitor and may see a new experience. Note that it is difficult to quantify how many visitors are affected by this policy as it will vary based on each site and visitor behavior.
As a workaround, as soon as a visitor comes to the site and whenever a cookie update is made, Maxymiser will automatically populate that value in localStorage. As soon as the browser (Safari in this case) clears the visitor cookie, Maxymiser will restore the most recent cookie value.
A note for campaign developers: it’s important to understand that while cookies spread across sub-domains, localStorage is origin-dependent. If Maxymiser cookies are cleared, only the data synced on the last visit to the visited sub-domain will be available for restoring.
This feature will ensure continued accuracy in testing and campaigns so visitors online movement has a continued flow.
Steps to Enable
To enable this workaround:
- Update your Maxymiser tag to the latest version through the CD API Deployment page under Site Setting in the Maxymiser UI.
- Change the storageType to: 'cookie-key-value-with-fallback'
- Deploy
No action in the Publish Center is required.
Responsys-Maxymiser Integration
Marketers can now deliver consistent experiences across web and email with the all-new Responsys-Maxymiser integration. Self-serve and easy to use, this integration empowers marketers to:
- Ensure consistent marketing messages across the customer journey
- Drive conversion and revenue by both testing and delivering personalized customer experiences
- Advance their optimization program without relying on development resources
Drive conversion and revenue by streamlining messaging across web and email campaigns.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
A Responsys and Maxymiser license are both required to leverage this integration.
Key Resources
The out-of-the-box integration with Adobe Analytics enables marketers to send Maxymiser element/variant combinations to Adobe Analytics for reporting. With this release, the following scenarios will now be accounted for in the Adobe Analytics integration.
- Leverage the Adobe Analytics integration with redirect campaigns without manual coding
- Set up multiple integrations with Adobe Analytics without manual coding
- No empty experience data is sent to Adobe Analytics when campaign content rules are not met
- Marketers can now define s.prop variable via a text field in the UI without relying on a developer to manually modify the integration script
Use the power of Adobe Analytics without having a developer code to create unique campaigns and testing scenarios tailored to your needs.
Steps to Enable
You don't need to do anything to enable this feature.
Low Traffic Stats Engine Enhancement
Marketers will now have the option to enable the low traffic stats engine at a campaign level, not just the site level. This approach reduces the test duration for low traffic tests and allows for faster campaign conclusion than using a standard traffic approach.
Viewing campaign metrics at the campaign level will allow for a quicker response time based on viewing metrics.
Steps to Enable
To enable this feature:
- Specify the preferred default traffic setting in the site admin page.
- The default preferred traffic setting will automatically be selected when creating a new campaign. To change for any given campaign, simply select an alternate traffic setting under Campaign Settings from the Campaign Overview screen.
Key Resources
Cross-Device Server Side Campaign Enhancement
With Maxymiser’s enhanced Server-Side API, developers can deliver consistent experiences across web and native apps. With Maxymiser now storing the “visitor state,” developers only need to specify Visitor ID, making it easier to test and personalize across devices.
Cross-device campaigns enable marketers to deliver consistent experiences across all devices for known users. Highlights include:
- Consistent multi-channel experience for both test and personalization campaigns
- Unbiased randomization
- Accurate conversion counting
This feature will streamline personalization and make it easier to test across devices.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
In order to provide a better onboarding experience, new customers will be shown a new welcome screen where they can invite new users, send the Maxymiser tag to developers, and quickly get started building campaigns.
This feature will streamline the process for new users so they can begin their work in Maxymiser immediately.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
A new welcome screen will be shown to all users on accounts with less than 3 campaigns. Once there has been 3+ campaigns created on the account, the welcome screen will no longer be the default screen, but can still be accessed via the left Site Menu.