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
  • 55118 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

Jim_McLemore
Level 2
April 8, 2019

I mean reading the marketo cookie that identifies them for the munchkin tracking scripts to Pre-fill, not the auto-fill from a cookie feature.  I believe both require a cookie though.

SanfordWhiteman
Level 10
April 8, 2019

OK, you're not really reading the cookie on the client side in that case but expecting Marketo to output the value in the Pre-Fill block (which happens on the server side).

And yes, that ability to truly Pre-Fill a hidden field would fail under the new behavior. But you don't need Pre-Fill if the session is already associated with the lead. The form post will be associated with their lead anyway.

Steven_Vanderb3
Adobe Employee
Adobe Employee
April 8, 2019

The changes cannot be applied to an instance before the scheduled release date (4/24 for London customers, 4/26 for all other customers)

Dan_Brown1
April 9, 2019

Hi @Roxann McGlumphy​,

Can you confirm if these changes will have any effect on tokens used in landing pages?

Roxann_McGlump1
Level 5
April 9, 2019

@Justin Cooperman​ can you confirm whether this will have any affect on how tokens are populated on landing pages?

Justin_Cooperm2
Level 10
April 9, 2019

No, the changes are defined precisely above. Other functionality is not impacted.

Justin_Cooperm2
Level 10
April 9, 2019

That's correct. If an end user previously filled out a marketo form (or clicked through a tracked link with mkt_tok) at any time in the past, that _mkto_trk cookie will be associated with the known lead in the Marketo Person Database on Marketo's back-end. This means all web views and click activity, as well as future form submissions will be associated with that known lead as is done before this change. This change is only impacting when a form is being pre-filled and, as Sanford noted, this does not impact hidden field auto-fill or other form features like progressive profiling.

Jim_McLemore
Level 2
April 9, 2019

That sounds good to me.  Is it possible to get someone to look at the way I have my LP and forms setup and ensure that they will function properly? I would suspect that general support might not be the best at validating that setup of this change.

SanfordWhiteman
Level 10
April 10, 2019

I can look at it if you link to it, but please open a thread in Products​.

Dan_Brown1
April 10, 2019

Thanks @Justin Cooperman​ for the clarification on tokens.

Sorry to dig further but just wanting to understand this change from a technical point of view so I have a further couple of questions:

1. So, to be absolutely clear: a visitor viewing a progressive form, that is cookied and known to Marketo, but where a 'mkt_tok' param does not exist, They will see the form progress for previously filled fields but they will not see any pre-fill functionality. Is that correct?

2. Will the contact details for a known visitor still be loaded into the page as they are now via the 'mktoPreFillFields' in situations where the 'mkt_tok' param was not apparent; or is progression being done server side so that no contact details exist in the page source?

3. Marketo will currently remove the 'mkt_tok' param from the URL on page load. For developers, is there an official way to fetch this token for re-use? Just thinking about scenarios where the user may go on a journey such as: email -> page -> page+form. Ideally we'd be able to carry the token across the journey via the URL if required. I know this could probably be done manually with JS, getting in before the Market logic runs, but just worried we could end up working against Marketo's logic and we could be susceptible to changes (Param renames, for example).

Let me know if the above needs any clarification.

Thanks,

Dan