Steven_Vanderb3

In our June 2022 release notes, we have announced that functionality Forms 1.0 assets will be completely removed from Marketo Engage including the ability for form submissions to be made to the leadCapture/save endpoint. This change will irreversibly break Forms 1.0 assets on Marketo Engage Landing Pages or embedded in external websites so that they can no longer accept submissions. Our modern Forms asset, Forms 2.0, will continue to be supported and will face no interruptions.   To aid in identifying which Forms 1.0 assets are in your subscription we have created a tool accessible by users with the Admin role. To use the tool, follow these instructions:   Navigate to Admin -> My Account. Take note of your data center in the “Support Information” panel. In your URL bar, navigate to app-[your data center].marketo.com/supportTools/formIdentification. In the tool, click “Get Form 1.0 List”. Your list of Forms 1.0 assets are returned. Each Form name is a hyperlink that will open in a new tab to the Form Asset page where you can view more information including what Marketo Landing Pages the Form is used on. Only references to Marketo Landing Pages will be of concern; references to these Forms will continue to work in Smart Lists filters.   The Forms 1.0 assets will be disabled on October 14, 2022 with no option for extensions or exceptions. Please complete your review of your form usage beforehand and replace any in-use Forms 1.0 asset with an equivalent Forms 2.0 asset.     ... View more

After March 11, 2022, access to Marketo Sky will be removed from all Marketo Engage subscriptions as we focus on delivering our next-generation experience. We are bringing some of our most popular Marketo Sky innovations to our next-generation UX so that teams can continue taking advantage of them without needing to navigate to Marketo Sky.   Campaign Priority Override: Ensure that high-priority trigger Smart Campaigns execute as soon as possible with the ability to override the standard campaign priority ranking. Lower-priority trigger Smart Campaigns can also be lowered in priority to free up processing resources for other high-priority tasks.   Asset Deactivation: Maintain control of your time-sensitive assets and campaigns with the ability to schedule their automatic deactivation at a specified date and time.   Access to other Marketo Sky exclusive functionality will be lost when access is removed after March 11, 2022. These features will return in the future as we continue to release redesigned assets in our next-generation UX. ... View more

In January 2021, we released the Submit Form API endpoint to give Marketo Engage integrators the ability to submit to Marketo Forms through a supported and authenticated REST endpoint. Thanks to customer feedback we were able to identify a lack of parity for critical functionality such as correct handling of duplicate records and support for Program Member Custom Fields. These issues blocked some integrators from successfully onboarding onto the Submit Form API endpoint.   In our August release, we have enhanced the Submit Form endpoint to handle duplicate records the same way as Marketo forms. When there are duplicate records that match an email address submitted to the form, the endpoint will update the record with the most recent Last Modified Date.   In our October 22, 2021 release, we plan to release support for Program Member Custom Fields for the Submit Form REST API endpoint. We understand that integrators will need time to update and test these new changes before they can fully onboard onto the Submit Form endpoint. To allow additional time for migration, we are delaying blocking programmatic POSTs to the /save2 endpoint to our January 21, 2022 release. This will be the final extension.   Programmatic submissions to our form endpoints remain unsupported despite this delay. Please work to update integrations submitting via this method to one that is supported: Marketo Engage forms on Landing Pages or using the embed code, our Forms2.js API, or the Submit Form API endpoint.   Previous announcement: https://nation.marketo.com/t5/product-documents/updated-april-2021-upcoming-changes-to-the-marketo-engage-form/ta-p/306631 ... View more

Overview Form pre-fill offers convenience to your customers but bares the risk of their private identifying information leaking to others if an email with a link to a landing page is forwarded or shared to unintended recipients. Currently, pre-fill on Marketo Engage Forms is controlled at the Form or Global level https://docs.marketo.com/display/public/DOCS/Disable+Pre-fill+for+a+Form+Field. Administrators lack granular control over pre-fill so that they can control it on a per field basis.   This beta introduces the ability to mark a field as “Sensitive” in Field Management. A Sensitive Field will have pre-fill disabled for that field on all forms globally in the subscription. The ability to enable pre-fill for that field will be disabled in the form editor for all users. An example use case is:   You have a form with pre-fill enabled on a landing page for users to register for a webinar. You collect the following fields on the form: First Name Last Name Company Name Title Email Address You have designated First Name, Last Name, and Email Address as “Sensitive” in Field Management. When someone clicks on a link in their email to the landing page, only the Company Name and Title fields will pre-fill with the lead’s values. Users editing the form are not able to override the setting to turn pre-fill on for the First Name, Last Name, or Email Address fields. Beta Details This beta will allow you access to the Sensitive Fields functionality. During the beta you must: Report on defects found during beta testing within one (1) business day. Answer survey questions as needed. Provide feedback regarding product documentation and help systems. In return, you will get: Involvement in the development cycle, which includes the ability to influence the final code and submit enhancement requests prior to release. More stable code due to multiple individuals testing in many environments. One-on-one contact with Product Management. Resulting knowledge gained from participating in the beta test program. Joining the beta If you are interested in participating in this beta, please do the following:  Sign up for the beta with your contact information: Beta Signup    If you haven’t already, join the Adobe Experience Cloud Feedback Panel. This panel gives you exclusive access to alphas and betas across the entire suite of Adobe Experience Cloud, and gives you the opportunity to provide feedback via surveys, studies, strategy meetings, and other activities. https://experienceleague.adobe.com/#feedback   After registering, you will receive a welcome email asking you to complete your profile which includes the option of signing the beta agreement.   Once we have confirmed the beta agreement has been signed, we will reach out to schedule a call and feature enablement.   The beta will be ongoing until April 30, 2021. We look forward to working with you and hearing your feedback! ... View more

Bots continue to be a growing problem for publicly facing forms on the web. The Marketo Engage Product team would like to hear about your experience if your company has implemented a custom CAPTCHA solution to protect your Marketo forms and landing pages from bot submissions, or if you're planning to in the near future. Please fill out the form below if you are interested in discussing this topic with our Product Management team.   https://forms.office.com/Pages/ResponsePage.aspx?id=Wht7-jR7h0OUrtLBeN7O4epuYNI0IWZLgH1mr3nTaPdUNjBTWVVYTVc3RFIwNFJVT00wUzMwRlVJNi4u ... View more

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 will be making changes to the URL structure for Landing Pages, Forms, and Images & Files assets.   Why is this change being made? Technical Details Landing Pages Images & Files Forms What customer action is required?   When is this change being made? Starting January 21, 2021, we will begin gradually provisioning new Marketo Engage subscriptions with the new URL structure. On March 5, 2021, all new Marketo Engage subscriptions will be provisioned with the new URL structure in place.   For existing Marketo Engage subscriptions, we will begin gradually rolling this change out beginning April 1, 2021. More details on our rollout timeline will be released in March, 2021.   April 2021 update Starting in March 2021, a subset of new Marketo subscriptions will be provisioned with the new Design Studio URL structure. Beginning with our May 7th release, all new subscriptions will be provisioned with the new Design Studio URL structure.   Existing subscriptions will be gradually migrated through a rollout beginning May 20th.    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.   Technical Details Landing Pages, Form embed code, and resources stored in Images & Files will have 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 will be minimally affected by this change.   Landing Pages Subscriptions without a configured landing page domain Landing page paths will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/lp/123-ABC-456/unsubscribePage.html After: 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 will change to a unique hostname for your subscription. Before: http://na-sj01.marketo.com/rs/123-ABC-456/images/cuteKitten.png After: 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 Before:               <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>               After:               <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? Marketo Engage subscriptions provisioned after May 7, 2021 will have the new URL structure already in place for all Design Studio assets.   Existing Marketo Engage subscriptions will be migrated in a staggered rollout to the new URL structure during nightly maintenance cycles beginning on May 20th. There will be no downtime, but landing pages may experience a short period of degraded performance during migration.   Existing URLs and references will continue to work after the migration to the new URL structure until June 30, 2022. 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.   To begin preparing for this change, we suggest doing the following: Configure your Landing Page URLs with a CNAME https://docs.marketo.com/display/public/DOCS/Customize+Your+Landing+Page+URLs+with+a+CNAME Secure your Landing Pages with SSL https://docs.marketo.com/display/public/DOCS/Add+SSL+to+Your+Landing+Pages Begin updating pages where you embed Marketo Engage forms with the new embed code introduced in our October 2020 release (requires secured landing pages) Begin an audit of where you reference Design Studio assets on the web. This will help you begin a plan to update any existing references to our older URL structure before we begin deprecation in 2022. Generally this will be on non-Marketo pages, as our Landing Page editor will automatically format embedded images and forms in a compatible manner. Only references hardcoded to the old URL structure need to be updated, e.g.   http:// na-sj01.marketo.com /rs/123-ABC-456/images/cuteKitten.png. Relative references will continue to work without need changes e.g.  /rs/123-ABC-456/images/cuteKitten.png. Please work with your web developer to determine where you may need to make updates. ... View more

October 2021 Update https://nation.marketo.com/t5/product-documents/update-to-deprecation-of-programmatic-form-submission-methods/ta-p/317522#M1062 In January 2021, we released the   Submit Form API   endpoint to give Marketo Engage integrators the ability to submit to Marketo Forms through a supported and authenticated REST endpoint. Thanks to customer feedback we were able to identify a lack of parity for critical functionality such as correct handling of duplicate records and support for Program Member Custom Fields. These issues blocked some integrators from successfully onboarding onto the Submit Form API endpoint.   In our August release, we have enhanced the Submit Form endpoint to handle duplicate records the same way as Marketo forms. When there are duplicate records that match an email address submitted to the form, the endpoint will update the record with the most recent Last Modified Date.   In our October 22, 2021 release, we plan to release support for Program Member Custom Fields for the Submit Form REST API endpoint. We understand that integrators will need time to update and test these new changes before they can fully onboard onto the Submit Form endpoint.   To allow additional time for migration, we are delaying blocking programmatic POSTs to the /save2 endpoint to our January 21, 2022 release. This will be the final extension.   Programmatic submissions to our form endpoints remain unsupported despite this delay.   Please work to update integrations submitting via this method to one that is supported: Marketo Engage forms on Landing Pages or using the embed code, our Forms2.js API, or the Submit Form API endpoint. April 2021 Update   In November 2020, we announced that we will forbid programmatic Form POST submissions to our /save and /save2 endpoints beginning May 7, 2021. The reason for this change is to reject methods of unsupported form submissions used by bots to fill customer databases with spam data.   We understand that many customers may need more time to update the integrations to use a supported method such as the Forms2.JS API or the Submit Form REST API endpoint. We have decided to extend the deadline in which we will begin blocking all programmatic Form submissions to take place on October 15, 2021. Programmatic FORM submissions continue to be unsupported and while we are temporarily delaying enabling validation to reject these submissions, we cannot ensure uninterrupted submission following  upcoming product and infrastructure changes.   For customers that still wish to block this method of form submission to address bot attacks,   will allow you to opt-in to form submission validation on your subscription. This validation will check that form submissions are coming from Marketo Forms, Forms2.js API, or the Submit Form REST API and will reject it otherwise. This is expected to block many common sources of bot attacks.   However, if you have a form integration that currently uses programmatic Form POST to submit lead data, enabling this feature will also block your Form submissions. We encourage all customers to migrate to a supported method of form submissions as soon as possible to protect their subscriptions from bot attacks.   The original announcement is below for reference. The details remain the same aside from the schedule to block programmatic form POST submissions.   What’s changing? In our May 7, 2021 release, Marketo Engage will be making changes to our form platform to protect the stability and security of our infrastructure:   Forms 1.0 will be fully deprecated, resulting in loss of functionality of any remaining Forms 1.0 assets still in use. Marketo Engage will begin rejecting form submissions made through unsupported methods, such as programmatic form POSTs to the leadCapture/save and leadCapture/save2 endpoints.   Why is this change being made? On August 1, 2017, Marketo Engage deprecated the Forms 1.0 editor, removing the ability to create or edit Forms 1.0 assets. This change will complete our end of life efforts for Forms 1.0.   In addition, we have found that our Form endpoints “leadCapture/save” and “leadCapture/save2” are common targets for bot attacks. To protect the stability of the Marketo Engage infrastructure, and to aid customers in maintaining a clean database, we are completely disabling the “leadCapture/save” endpoint and enforcing checksum validation on the “leadCapture/save2” endpoint.   What customer action is required? Forms 1.0 deprecation Provisioning of Marketo Engage subscriptions with the ability to create Forms 1.0 assets ended December 31, 2014. If your subscription was provisioned after this date, then it will not have Form 1.0 assets. Forms 2.0 assets will be unaffected by this change.   Marketo Engage subscriptions provisioned before December 31, 2014 may still  be utilizing Forms 1.0 assets on their landing pages and website. These forms will need to be remade in our Forms 2.0 editor and replaced wherever they are still being used.   Programmatic Form POST deprecation Some integrations may be performing programmatic form POSTs to “leadCapture/save" or “leadCapture/save2” to submit data into Marketo Engage databases. This method of data ingestion has always been unsupported and will cease to work as part of this deprecation. All integrations using programmatic form POSTs must be updated to use our Forms 2.0 API, Push Lead REST API, or the Submit Form REST API endpoint releasing in the January 2021 release.   Customers using native Forms 2.0 assets on pages and/or the Forms 2.0 API do not need to take any action. Checksum validation will work natively with these supported methods.   What happens if customers don’t act? Customers that fail to replace any in-use Forms 1.0 asset with a Form 2.0 asset will find that their customers will be unable to submit to their 1.0 Forms.   Customers using integrations that perform programmatic Form POSTs to the “leadCapture/save” or “leadCapture/save2” endpoints will see these integrations fail, resulting in loss of form submission data.   Is my Form 1.0 or 2.0? Forms 1.0 and Forms 2.0 have different look and feel:   Forms 1.0 Forms 2.0 Marketo subscriptions provisioned after December 31, 2014 will only have Forms 2.0 assets. ... View more