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

Form Pre-Fill Feature Upgrade

  • April 4, 2019
  • 142 replies
  • 55076 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.

142 replies

New Participant
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.

Grégoire_Miche2
New Participant
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

Yanir_Calisar9
New Participant
April 14, 2019

@Jay Jiang​

Yes

We've developed the plugin a while ago and last week we added this free option of automatically pass the mkt_tok from the URL to the iframe forms.

Also, I've developed this javascript: Auto iFrames tagging to support the new Marketo upgrade​ as a "custom implementation" that is required for the scenario:

Navigating to a non-Marketo page that includes an <iframe> pointing to a Marketo Landing Page that includes a form with pre-fill enabled.

SanfordWhiteman
New Participant
April 12, 2019

The behavior when a link is forwarded and the secondary (unintended referral) recipient has an anonymous Munchkin session, or no session at all, has not changed. Their form will Pre-Fill. After all, that's the exact same experience the original recipient would have, the first time they get a Marketo email. The Pre-Fill must work in that case.

When the Munchkin session is already associated with a lead other than the same lead for whom the mkt_tok was generated, the form will not Pre-Fill. This has upsides, and just as clearly has downsides.

Steven_Vanderb3
New Participant
April 12, 2019

If someone's browser is already cookied on your website, and they click on a link they received in a forwarded email from another person, the information will not pre-fill.

If someone's browser ISN'T cookied on your website, and they click on a link they received in a forwarded email, the information will pre-fill.

The circumstances in which a forwarded email link can cause form pre-fill has been narrowed.

New Participant
April 12, 2019

Thanks for the response!  I'm a little confused though... that's the behavior now, right?  We have a huge problem where people forward emails and then new people register and all the information is incorrect or we're missing information. We know the "Forward to a Friend" link would fix this but people are just not trained to do that.  But this documentation says that if someone is forwarded the e-mail who does exist in the database, it will not be pre-filled, right?

SanfordWhiteman
New Participant
April 12, 2019

Remember, no ads on the Community per the guidelines. (And obviously you don't do anything "directly" from the cookie.)

Tim_Bohn2
New Participant
April 12, 2019

Our enterprise customers use this solution for content gating and form management.

It pre-pops and performs progressive profiling directly from the Marketo cookie, so won't be affected by the change.

Content Gating : The #1 Enterprise Solution - Gated Content .com

Might be useful for some.

Grégoire_Miche2
New Participant
April 12, 2019

We usually setup subscription centers so that they cannot be entered directly from the web site. The reason being you cannot control whether or not the person owns the email address they are entering.

We setup the preference centers in a way where if no mkt_tok is present or is a fake (fetches no email address from Marketo), the visitor is redirected to a page where the enter their email address, then are sent an email with a link to the preference center.

-Greg

SanfordWhiteman
New Participant
April 11, 2019

1) How will this affect forms used in RTP/Web Personalization? We have numerous campaigns that use embedded forms within a dialog campaign.

Expect no forms to be Pre-Filled automatically unless they're on a page that was directly linked to in an email.

2) Will this reduce the number of leads that get the wrong tracking information? For instance, we have members who share an email address and member a receives an email to opt-in to something which uses a hidden form post. They opt-in, assuming they used a shared device, and get cookied as member b. This essentially changes member a's name to member b and gets tracked under member b's activity log.

No, I would not say this change would make your case less likely. If an email is sent to member B, and the link in the email goes straight to the form, then member B's info will be shown. You're saying member A and B have the same email address. Hence the dedupe key value (Email) is still correct. They change the First Name and Last Name only, that's going to update the record in the database.