Form Pre-Fill Feature Upgrade | Community
Skip to main content
Roxann_McGlump1
Level 5
April 4, 2019

Form Pre-Fill Feature Upgrade

  • April 4, 2019
  • 142 replies
  • 55123 views

With the evolving best practices and awareness around data privacy, Marketo will be upgrading how we handle form pre-fill.

What change is being made?

Starting April 24, 2019, Marketo will only pre-fill form fields if the URL used to navigate to the Marketo landing page contains a valid mkt_tok URL parameter value (which occurs when users click tracked links in Marketo emails). What that means is, any time a person is viewing a Marketo landing page with a form, the URL being used must contain the mkt_tok token in the query string, otherwise the form on that landing page will not be pre-filled. If the URL in the browser window does have a valid mkt_tok tracking token, then the form within the page will pre-fill as expected with data corresponding to the person record associated with that mkt_tok.

Also note that if you are embedding Marketo Landing Pages within other web pages using an <iframe>, the mkt_tok would need to be passed from the parent page to the <iframe> URL if you intend for form prefill to work within the <iframe>

​How did it work before?

Previously, Marketo landing pages would rely on Munchkin tracking cookies to identify known person records, and forms would pre-fill based on that cookie. Form pre-fill did not require being linked to a Marketo landing page from a tracked email link.

Why is this changing?

This upgrade is being made to provide a more consistent and more secure experience with Marketo’s forms. We have identified that, in the past, people have experienced scenarios where data pre-filled into a form didn’t always correspond with the actual person viewing the page. For example, people using a shared computer or those who may have been cookied incorrectly by clicking through a forwarded email, could end up viewing incorrect data associated with a different person.

To provide a more consistent customer experience, and as a security enhancement, Marketo is upgrading the conditions under which the form pre-fill will display known customer information. In short, pre-fill will only work when users clickthrough links in Marketo emails, demonstrating that they have ownership of the email address associated with the known person record. Below is a list of different scenarios and how form pre-fill will work moving forward.

Please note, these changes to form pre-fill will not affect any other functionality of Marketo Forms, including the progressive profiling feature.

ScenarioWill the form pre-fill?Notes
Clicking a tracked link in a Marketo email to a Marketo landing page with a form which has pre-fill enabledYesThe email link must have mkt_tok enabled. Links that are not tracked or that have mkt_tok disabled will not work.
Navigating directly to a Marketo landing page with a form which has pre-fill enabledNoA direct link to the landing page will not have the mkt_tok present in the HTTP request.
Refreshing a Marketo landing page with a form which has pre-fill enabledNoThe mkt_tok is stripped from the URL after Marketo Landing Pages load so refreshing the page will not include the mkt_tok in the URL. As a result, pre-fill will not work.
Clicking a link in a sample email to a Marketo landing page with a form which has pre-fill enabledNoThe sample email will not have a valid mkt_tok attached to the link and so will not pre-fill the form. If you wish to test form pre-fill you will need to use a real email from a Marketo campaign.

Navigating to a non-Marketo page that includes an embedded Marketo form which has pre-fill enabled

NoThis behavior does not change with the upgrade. Pre-fill has never been supported for Marketo forms that are embedded on non-Marketo pages.
Navigating to a non-Marketo page that includes an <iframe> pointing to a Marketo Landing Page that includes a form with pre-fill enabledWith custom implementationThe form within the Marketo Landing Page that is being loaded in the <iframe> will pre-fill if the mkt_tok value from the original HTTP request is passed along to the <iframe> URL
Visiting a Marketo page with a mkt_tok that is not associated with the same person record as an existing Marketo Munchkin cookie currently stored on the browserNoThis will prevent the wrong person’s information from being displayed in cases where a computer is shared, or an email with a mkt_tok tracked link is forwarded to another person that may already be cookied as a known person in your database.
Copying a Marketo tracked link from an email and sharing/pasting it externally (email, blog, chat, social media post, etc.) that enables another individual to click the tracked linkYesThe tracked link in a Marketo email will redirect to a URL with the mkt_tok included, so anyone clicking this link will reach a page and see pre-fill data associated with the known person record from the “to” line of the email.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

142 replies

Grégoire_Miche2
Level 10
April 15, 2019

Please keep in mind that iframe is not the preferred way to insert forms in a web site. It has performance and SEO drawbacks, at minimum. Embedded forms should be the preferred way. We have worked with a few web agencies in the past, on various CMS (Drupal, Wordpress, Kentico, Adobe Experience Manager, ...) and they never had any issue creating plugins that does a good work embedding forms and adding advanced code (@Sanford Whiteman​'s one) so that they have prefill, but also field reorder, advanced styling, GA/GTM integration, or Recaptcha v3... I would strongly recommend this way of doing it.

-Greg

Level 2
April 16, 2019

@Justin Cooperman​ @Steven Vanderberg @Roxann McGlumphy​

Hi Guys. I think you need to do a series of webinars explaining this change. The combination of the three week notice and the complexity of it does not make for comfortable, confident, happy customers, at least in my case. I've just spent an hour and 15 mins reading through the article and comments, attempting to digest and understand and am still unsure I fully understand the changes.

Many thanks to @Sanford Whiteman​ and other users jumping in with the Marketo team to help clarify this.

Christophe_Chan
April 18, 2019

Jim is making a very good point here.

Why don't you (aka Marketo) let your customers/users choose to disable/enable the feature of form pre-filling based on the Munchkin tracking cookies to identify known person records?

Please vote this up.

Many thanks!

Dan_Fitzpatrick
April 25, 2019

Hi All. It's the day after the change was planned to be implemented, but it appears to me it has not been. Has anyone heard any updates on timing for this?

Darby_Jones1
Level 1
April 25, 2019

Are you saying this nullifies the new change? If we set it up in this way, am I correct in asserting that it will use munchkin cookies to pre-fill data from known records?

SanfordWhiteman
Level 10
April 25, 2019

If you read my response you'll see tokens can't be used directly for all field types (and Jay was just using this as an example of how the policy can be circumvented).  Use my Pre-Fill method (linked in the thread) and the old behavior is restored.

Raymond_Johnson
Level 3
April 26, 2019

Based on the comments above, the timing was 4/24 for London customers, 4/26 for all other customers. I've tested our instance this morning, and the change hasn't been implemented yet for us?

Steven_Vanderb3
Adobe Employee
Adobe Employee
April 26, 2019

The change will happen after business hours tonight.

Level 3
April 29, 2019

Jay, thank you for the workaround, however we do have another scenario where we need to pre-fill picklist values (which doesn't have default values) before this update it was getting filled now it's not. Any suggestion will be appreciated

SanfordWhiteman
Level 10
April 29, 2019

Read my responses, I already linked to the solution many times.