Form Prefill Question | Community
Skip to main content
Karyn_Hill
Karyn_Hill
Level 4
February 15, 2019
Question

Form Prefill Question

  • February 15, 2019
  • 1 reply
  • 3343 views

Is there a way to prevent a "wrong" email address from appearing in a form prefill field? We have a form that is set to prefill that when people go to the page but for some people, it's pulling an email address that's not theirs. I believe in all cases that it's an email address the user has used in the past for one reason or another (searching for a user with that email address, for instance) but I'm not 100% positive.

Here is the Marketo landing page with the form. pages.mapi.net/OP-MAPI-Preference-Center-10_MAPI-Opt-in-Subscription-Management-V1.html

It has some hidden fields, which depend on the user's access. You should see four options. A full member will see eight options.

My understanding is that Marketo is using some form of logic to pull what it believes to be the appropriate cookie but I don't know enough about forms to know if I can help it be more accurate.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
February 15, 2019

Pre-Fill doesn't use any special lookup "logic" at all. It is always exactly accurate: it uses the lead that's currently associated with the session or pageview.

So if they're seeing data from a particular lead, that's because that lead clicked a Marketo-tracked email in the past, or filled out a Marketo form in the past, in that same browser.

    Karyn_Hill
    Karyn_HillAuthor
    Level 4
    February 15, 2019

    Then I must have something wrong on the form. It's prefilling that field on our employee's computers with email addresses of members who are thousands of miles away.

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    February 15, 2019

    This happens when employees have sent test emails to themselves, or clicked on links in forwarded emails. There's nothing wrong in your simple form setup that I can see; certainly it's possible to write all manner of custom code that could mess things up like this, but you don't have any.

      Terms & ConditionsAccessibility statement

      Loading footer...