[FAQ attached below this article]
On August 31, 2020, Marketo Engage will implement a new retention policy specifically for Sent & Delivered Email activities. Under this policy, data for these two activity types will be stored for a rolling 90-day period from the activity date for use in Smart Lists. This is a change from the current default retention period of 25 months, and from the current Extended Data Retention subscription option period of 37 months.
Upon the policy taking effect, data older than 90 days for these two activities will be deleted and no longer available for export. Any Smart List with the “Was Sent Email” and “Was Delivered Email” filters (including NOT Was Sent and NOT Was Delivered) should be updated to ensure the maximum lookback date is 90 days. If the lookback date is greater than 90 days, the Smart List will continue to function, but only activities that are 90 days old or less will qualify.
In 2020, we are improving critical parts of the underlying Marketo Engage infrastructure, including Batch campaign processing, similar to the Trigger campaign improvements made in 2019. This new infrastructure, in combination with the new retention policy, is expected to result in shorter lead time with large email sends and faster segmentation processing to deliver significantly faster processing to our customers. Note, the revised retention policy is one, among several, aspects that come together to deliver this improved performance, but broadly speaking reduced retention helps with faster database look ups and search across the run-time infrastructure.
What's NOT Changing?
Aggregated data – including Reports, Dashboards, and Analytics – will not be affected by this change (unless they reference a Smart List with these activities). The new policy will not affect any activity type other than Sent and Delivered (for example, Was Opened activity data is not affected). Further, this change does NOT affect Engagement Program casts.
What Customer Actions Are Needed?
First, you'll want revisit where and how you're using these two activity types. Audit your Smart Lists and ensure the date ranges for these two activity types are less than 90 days - if you must use a date greater than 90 days, we suggest running a process to export to an external system. You will need to create this before the new retention policy takes effect on August 31, 2020. Information on how to export activities using APIs can be found on our Developers Documentation website.
We appreciate you understanding as we move toward an enhanced Marketo Engage experience for all customers. Please download and review the FAQ attached below for further suggestions, workarounds and additional information.
... View more
Beginning with our July release on July 31, 2020, Marketo Engage user interface (UI) will no longer be supported in Internet Explorer browsers.
Why is this change being made? In order to continue to innovate with Marketo Sky, we are focusing on development for the most utilized browsers, including Google Chrome, Mozilla Firefox, and Apple Safari.
What will happen if I use Marketo Engage with Internet Explorer after July 31, 2020? Accessing Marketo Engage using Internet Explorer may result in undesirable behavior when interacting with the user interface. Customer Support will not be able to troubleshoot bugs encountered only in Internet Explorer.
Will this impact customers visiting my landing pages or filling out forms? Internet Explorer will continue to be a supported experience for customer-facing assets such as landing pages and forms. This change is strictly for the Marketo instance UI.
What if I am required to use Internet Explorer? We encourage customers with business requirements to use the Microsoft Edge browser, Microsoft's new Chromium-based browser, which features an Internet Explorer compatibility mode.
... View more
How does this impact Marketo?
How does Munchkin operate?
On a person’s first visit to a page on your domain, a new anonymous person record is created in Marketo. The primary key for this record is the Munchkin cookie (_mkto_trk) which is created in the user’s browser. All subsequent web activity on that browser is recorded against this anonymous record. In order to be associated with a known record in Marketo, one of the following methods should be used:
The person may visit a Munchkin-tracked page with a mkt_tok parameter in the query string from a tracked Marketo email link.
The person may fill out a Marketo Form.
REST Associate Lead call must be sent.
Once one of these actions is completed, the cookie and all its associated web activity will be associated with the known record.
How is Marketo planning to address ITP concerns?
Do I need to do anything to take advantage of these updates?
In order to leverage the new behavior and take advantage of the greater expiry period and tracking capabilities, ensure that you have configured the following:
A Landing Page CNAME
Secured Landing Pages (i.e. HTTPS)
For external pages, you must have configured a Landing Page Domain or Domain Alias with a Top-Level Domain (TLD) matching the external domains which you wish to track
For example, if you have pages on the domain www.example.com which are tracked, you must have configured an LP Domain or Alias which is a subdomain of example.com, like munchkin.example.com
What happens if I do nothing?
Munchkin’s ability to track users across sessions on the same domain will remain limited by ITP to either 1 or 7 days based on the browser and browser version used by the visitor. As of this posting, this only affects visitors using the Safari browser, although Chrome & Firefox may follow suit with their own versions.
When will the solution be launched?
These changes will begin as a staggered roll-out to customers who have opted into the Munchkin Beta channel in conjunction with the January 2020 Marketo release. Once the solution has been released to all beta customers, the roll-out to our entire customer base will begin in mid-to-late February. All customers should expect to have the solution by end of March 2020.
Google Chrome Update (Feb. 2020):
Google recently announced that the Chrome browser will block all third-party cookies within two years; however, s ince Marketo uses 1st party cookies, this update regarding 3rd party cookies will NOT affect your Marketo tracking efforts. For further context about 3rd party cookies in general, and the industry shift away from using them, please see the following article for Adobe's stance across the Experience Cloud Solutions:
... View more
As of November 30, 2019, all the familiar content on the Marketo Engage Status Page has been migrated and is now available on the Adobe Status Page . This move allows us to leverage Adobe’s more robust and efficient monitoring platform for not only the standard alerts and scheduled maintenance, but also hotly-requested functionality including pod-specific status updates and proactive notifications!
October 31, 2019: The functionality to subscribe to notifications at the solution and pod level released on the Adobe Status Page. Customers may begin exploring and subscribing to various notifications.
November 30, 2019: Marketo Status Page was deprecated and a redirect to Adobe Status Page was put in place. Moving forward, please refer to this article for up-to-date System Uptime and Deliverability Scores.
January 8, 2020: To better prepare you for upcoming changes and scheduled maintenance, we have increased the previous two-day ‘lead time’ of these notifications based on impact. Service Maintenance 30-day lead notifications are now available on Web/Mobile/Tablet surfaces and via Email notifications.
Opt-In to Adobe Status Page Subscriptions
For step-by-step instructions on how to opt-in to Adobe Status notifications, please refer to this article: Subscribe to Adobe Status Notifications
How do I see previous issues or maintenance?
1. Go to: https://status.adobe.com/ 2. Click "Experience Cloud" 3. Click "Adobe Marketo Engage" 4. Select the appropriate Service 5. Click the dots on the date line to view the details of what occurred on that day
What do the colors mean on the Status page?
1. Blue is for maintenance 2. Red is for a major issue 3. Orange is for a minor issue
... View more
**Nov. 11, 2019 update: In a continued effort to integrate with Adobe's release structure, we are shifting the deprecation of TLS 1.0 and TLS 1.1 to January 13, 2020. To align with Adobe’s world-class standard for security, we will be deprecating support for Transport Layer Security (TLS) 1.0 and 1.1 starting December 13, 2019 January 13,2020. Systems integrating with Marketo that are not compliant with 1.2 protocol could potentially lose access to Marketo Engage services. To maintain your Marketo Engage access, please ensure that all client systems are TLS 1.2 compliant before January 13, 2020. For a list of TLS 1.2 compliant browsers and frameworks, see the tables at the bottom of this communication. What is Transport Layer Security (TLS)? Transport Layer Security (TLS) is a security protocol that provides privacy and data integrity between two communicating applications. It is deployed widely for web browsers and other applications that require data to be securely exchanged over a network. TLS includes two layers: the TLS Record protocol and the TLS Handshake protocol. The Record protocol provides connection security. The Handshake protocol enables the server and client to authenticate each other and negotiate encryption algorithms and cryptographic keys before data exchange. Why is Marketo Engage making this change? Most requests for Marketo Engage web services originate from TLS 1.2 compliant systems, with low traffic from TLS 1.0 and 1.1 systems. TLS 1.0 was first published in 1999, with newer versions 1.1 in 2006, and 1.2 in 2008. As technologies age, security threats evolve, and so must industry standards. To stay aligned and protect our systems from security risks identified with older TLS versions, we are mandating a minimum TLS 1.2 supported connection to ensure secure connections. There have been documented attacks against TLS 1.0 using an older encryption method and the older versions are more vulnerable than TLS 1.2. For more information, see Attacks Against TLS/SSL. When will this change happen? TLS 1.0 and TLS 1.1 deprecation will take place on January 13, 2020. After the date of deprecation, you will not be able to connect to Marketo Engage services using browsers or applications not compatible with TLS 1.2. Marketo Engage encourages users to quickly abandon older versions of TLS to avoid exposure to security vulnerabilities. How does TLS affect you? Marketo Engage services are web-based and can only be engaged through a secure network connection. TLS helps ensure a secure and reliable connection between your browser or server and Marketo web services, which includes anything that uses Marketo’s API, such as REST, SOAP, Munchkin, RTP, Mobile, and more. As technology evolves, security standards are upgraded to ensure higher levels of privacy and data integrity. However, older applications are not updated to include the latest standards. As the acceptable level of security rises, these older, less secure applications are left behind. To be able to connect to Marketo Engage services, update your browsers and application frameworks to a version that supports TLS 1.2. How does TLS affect your customers? Marketo Engage landing pages will be served to your visitors through TLS 1.2 secured connections. Any browser updated since late 2013 (except Chrome, updated since 2017) will be TLS 1.2 compliant; further, Apple, Google, Microsoft, and Mozilla have all announced their plan to completely disable TLS 1.0 & 1.1 support by the first half of 2020, so we expect very minimal impact to visitors. If visitors report a loss of connectivity to Marketo Engage hosted landing pages as a result of this change, they will need to update to a compatible browser version. What error message will return to a non-compliant connection? The exact error messaging returned depends on the browser or application framework being used to connect to Marketo Engage web services. Some examples include but are not limited to: Unable to connect to the service Service not available Error in connection To resolve these errors, the browser or application framework must be updated to a version compatible with TLS 1.2. TLS 1.2 Compatibility Desktop Browsers Desktop Browser Compatible Versions Release Date Google Chrome V30+ March 20, 2017 Mozilla Firefox V25+ October 29, 2013 Internet Explorer IE 11 October 17, 2013 Microsoft Edge All versions Opera V17+ October 8, 2013 Apple Safari V7+ October 22, 2013 Mobile Browsers Mobile Browser Compatible Versions Google Android OS Browser Android 5.0+ Chrome for Android V30+ Firefox for mobile V27+ Opera Mobile V57+ Apple Safari IOS 5+ Application Frameworks Java .NET OpenSSL Java 8, or later .NET 4.6, or later OpenSSL 1.01, or later Java 7, with TLS 1.2 enabled in app .NET 4.5, with TLS 1.2 enabled in app
... View more