March 2023 update: The deprecation of the legacy URL patterns will occur on August 1, 2023.
June 2022 update: We have decided to extend the deadline until the end of 2022 with support of old URL patterns ending in January 2023. More information to be provided once a precise date has been chosen.
In 2021, Marketo Engage made changes to the URL structure for Landing Pages, Forms, and Images & Files assets. On August 1, 2023 we will be deprecating usage of old URL structures and these references will no longer load on the web.
Why is this change being made?
Technical Details
Landing Pages
Images & Files
Forms
What customer action is required?
Why is this change being made?
When a Marketo Engage subscription is not configured with a branded CNAME, Design Studio assets use a common hostname shared among all customers on the same pod. This behavior can be exploited in a phishing attack where a user cannot be sure a link to a Marketo Engage hosted asset belongs to the business they expect it to belong to. By updating each instance to use its own unique hostname, it is clearer to users the destination of URLs they are accessing.
Now that all Marketo Engage subscriptions have been migrated to our new URL structure for some time, we will be ending support to the legacy, more vulnerable URL structure.
Technical Details
Landing Pages, Form embed code, and resources stored in Images & Files had URLs updated from a hostname shared among all subscriptions on the pod to a hostname unique to each Marketo Engage subscription. Subscriptions configured to use a custom CNAME for their landing pages were minimally affected by this change.
Landing Pages
Subscriptions without a configured landing page domain
Landing page paths will changed to a unique hostname for your subscription.
Legacy: http://na-sj01.marketo.com/lp/123-ABC-456/unsubscribePage.html
Current: http://123-ABC-456.mktoweb.com/lp/123-ABC-456/unsubscribePage.html
Subscriptions with a configured landing page domain
Landing pages will continue to load from your configured landing page domain. No changes will be made.
Before: http://example.marketo.com/unsubscribePage.html
After: http://example.marketo.com/unsubscribePage.html
Images & Files
Subscriptions without a configured landing page domain
Paths to resources stored in Images & Files changed to a unique hostname for your subscription.
Legacy: http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png
Current: http://123-ABC-456.mktoweb.com/rs/123-ABC-456/images/cuteKitten.png
Subscriptions with a configured landing page domain
Resources stored in Images & Files will continue to load from your configured landing page domain. No changes will be made.
Before: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png
After: http://example.marketo.com/rs/123-ABC-456/images/cuteKitten.png
Forms
Subscriptions without a configured landing page domain OR subscriptions without landing pages secured by SSL
Legacy:
<script src="//app-sj01.marketo.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//app-sj01.marketo.com", "123-ABC-456", 1);</script>
Current:
<script src="//123-ABC-456.mktoweb.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//123-ABC-456.mktoweb.com", "123-ABC-456", 1);</script>
Subscriptions with a configured landing page domain secured by SSL
In our October 2020 release, we updated our form embed code to load from the landing page domain when it is secured by SSL. No further changes will be made.
Before:
<script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>
After:
<script src="//example.marketo.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1"></form>
<script>MktoForms2.loadForm("//example.marketo.com", "123-ABC-456", 1);</script>
What customer action is required?
You will need to audit the source code of your web pages to see if these URL patterns are in use by your business. If you have web pages or form usage that pre-date 2021 it is possible they are using the legacy URL pattern. Most customers configure a CNAME and secure it via SSL early in the life of their instance, minimizing the impact on Images & Files URLs. Prior to our October 2021 release, all form embed codes used the legacy URL structure. If you have usage of Marketo forms from prior to 2021 it is very likely they will need to be updated to use the new URL pattern, which can be found by copying the form embed code from the Form asset page.
For Marketo Landing Pages and Emails, if you used the Image picker or Form picker that are included in the Landing Page editor or Email editor then no change is necessary. If you hard coded references to images or forms using the legacy URL pattern instead of using the pickers then these references will need to be updated to the new URL pattern.
Customer Support does not have the ability to perform this audit for you.
To begin preparing for this change, we suggest doing the following:
.png)