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

Albert_Alvarez
Level 2
April 10, 2019

its embarassing that this is being spun as an "upgrade" IMHO.  Marketo needs to be upfront about what happened here.  Is there some regulatory issue that came down and caused this?  We need transparency. 

Raymond_Johnson
Level 3
April 10, 2019

Agreed, I have an open support ticket where i brought up the CASL and GDPR implication because this is going to affect our subscription centers operations.

Steven_Vanderb3
Adobe Employee
Adobe Employee
April 10, 2019

We have further notifications planned that will appear in your instance when you log in.  Should appear within the next couple days.

Albert_Alvarez
Level 2
April 10, 2019

has similar impact for our subs centers as well! 

Albert_Alvarez
Level 2
April 10, 2019

This is really something that should have been communicated ages ago through customer success reps. To give customers little more than two weeks to figure out the impact to our instance, comminicate that impact to our stakehodlers and come up with solutions to remedy is unacceptable.  I've had some bad customer experiences with Marketo in the past but this def takes the cake.  As I said before, as customers we need transparency as to why this change is happening.  I find it hard to believe that some people complaining about cookies displaying other peoples info on shared computers from a shared link is the real driver behind such a switft change to functionality that clearly a lot of customers use and rely on.

SanfordWhiteman
Level 10
April 10, 2019

I find it hard to believe that some people complaining about cookies displaying other peoples info on shared computers from a shared link is the real driver behind such a switft change to functionality that clearly a lot of customers use and rely on.

I personally believe that is the legit driver -- that is to say, a VIP (internal or external) reacted very strongly once they realized how the feature has always worked. Your points are well taken regardless!

Anyway, let me lighten the mood with the GIF (I almost never GIF anywhere, let alone here) that should accompany all unwanted upgrades:

Justin_Cooperm2
Level 10
April 10, 2019

Albert,

We're 100% here to help. As you've seen from the details of this post and from the comments, a change like this wouldn't be classified as a "breaking change" as nothing for your end users will be breaking. This is mainly because pre-fill is an optionally enabled, convenience feature for Marketo Forms (also note that the functionality can be toggled at the field, landing page and/or subscription level at any time by Marketo Customers). Not only can the functionality be toggled by other users in your Marketo subscription at any time, published forms always need to account for scenarios where someone is either not yet known (very common) or situations where the past cookie cannot be relied on (user is on a new device, cleared cookies, different browser, etc.).

To summarize, there is nothing about Marketo Forms that will break without pre-fill. In some cases, a user would just have to fill their information into the form again in the future. This does not change the way the Marketo Forms Editor, Form APIs, and any other form features work.

Thanks,

Justin

Adobe Employee
April 10, 2019

@Jessica Kao​ - Note this comment in the original post that addresses a concern raised about progressive profiling, at the SVMUG meeting yesterday: "Please note, these changes to form pre-fill will not affect any other functionality of Marketo Forms, including the progressive profiling feature."

Albert_Alvarez
Level 2
April 10, 2019

Thanks for the comments Justin.  Unfortunately I would classify it as a break from our perspective, and certainly not an "upgrade".  Alot of our UX, incuding our subs page, relies on the for pre fill ( we have turned on for majority of our other forms as well).  Nothing we can do but go back and figure out how we need to adapt.  Doesnt change my opinion on the way this was rolled out.

Alayna_Flor
April 10, 2019

So with this change, is there a way for us to be able to find the forms that do use pre-fill to be able to audit this functionality? Maybe in some kind of report? Or do we reach out to our CSM? I'm sure there are many of you out there that inherited a very old Marketo instance where assets like forms can cause a ruckus without knowing they're problematic. So in my case, I'm not fully aware of all that exists but really want to be sure to take a look at them all if a report/list is available.