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

Grant_Booth
Level 9
April 10, 2019

Kudos to Marketo for upgrading their security. This should've been done a long time ago. Fortunately we rarely use Marketo prefill - our tech savvy prospects are very sensitive about data security. Do progressive profiling instead!

Justin_Cooperm2
Level 10
April 11, 2019

I am committed to help you solve this problem if you're able to explain what you feel is being broken in your forms? Can you please email me details? jcooperman@marketo.com

I know you don't feel this is an upgrade, but I can definitely tell you that we get lots of negative feedback from customers about forms displaying other individuals information (for a variety of reasons).

Justin

Huihsing_Kiang3
Level 3
April 11, 2019

We use both pre-fill and progressive profiling and they compliment each other. It's understandable that Marketo needs to change it for security reason. I just wish they could get us at least 2-3 months to assess the potential impacts on our business and find an alternative solution. I think it's even worth a session in Marketo Summit.

Big thanks to @Sanford Whiteman for your awesome solution https://blog.teknkl.com/pre-fill-any-site-any-form/  You're saving me big time.

Jay_Jiang
Level 10
April 11, 2019

Just to confirm:

Pre-fill in Marketo forms won't work if mkt_tok is not present in the URL

BUT

If the same form fields are placed as tokens on a landing page without a mkt_tok, they'll still show

Image result for jackie chan what

Jay_Jiang
Level 10
April 11, 2019

You know people are just going to be adding hidden tokens to landing pages and then passing the values from the tokens to the form fields to do pre-fills now...

SanfordWhiteman
Level 10
April 11, 2019

Right, because otherwise tokens would no longer work in general.

The assumption (not universally accurate by a long shot!) must be that {{lead.tokens}} (a) will be invisible to the casual end user, i.e. used in HTML attributes or JS as opposed to displayed as-is; and/or (b) are used for less sensitive data than self-serviceable form fields, like just showing First and Last Name; and/or (c) don't provide an obvious path for updating their values (even if if in fact they're form-updatable) the way editable form inputs do.

SanfordWhiteman
Level 10
April 11, 2019

You know people are just going to be adding hidden tokens to landing pages and then passing the values from the tokens to the form fields to do pre-fills now...

Yep. But you actually have to output into XML (like my Pre-Fill solution does) to not break on certain datatypes and possible values.

Jay_Jiang
Level 10
April 11, 2019

This "upgrade" is just adding a workaround/inconvenience for your customers. We'll still be able to get pre-fills without mkt_tok tokens.

Level 3
April 11, 2019

We have implemented gated content in our blog and form pre-fill with auto submit based on the Marketo Cookie, after this change will we able to pre-fill and auto submit the form ? We don't use Marketo Email as most of the leads come to our Marketo Landing page from blog. What will be the impact after this on the above functionality ?

SanfordWhiteman
Level 10
April 11, 2019

auto submit based on the Marketo Cookie, after this change will we able to pre-fill and auto submit the form

Pre-Fill means filled from the Marketo database record. It doesn't mean filled from the URL or other source: that's called Hidden field Auto-Fill. It's not clear which one you're using.

It does not sound like you need to Pre-Fill the Email field if there's an existing cookie association. If (as you say) you're able to auto-submit a form at all, that means either:

     (a) the Munchkin session is already (from a previous pageview) associated with the lead, in which case you don't need to send the Email field (the existing session association holds); or

     (b) the Email field is Pre-Filled from the current mkt_tok query param, i.e. you've clicked on a tracked link in a Marketo email. This scenario is still fully supported.