If I have PURLs enabled for a landing page, shouldn't the form on my landing page prepopulate? | Community
Skip to main content
January 13, 2014
Solved

If I have PURLs enabled for a landing page, shouldn't the form on my landing page prepopulate?

  • January 13, 2014
  • 9 replies
  • 4085 views

I want to send out a direct mail campaign with PURLs generated by Marketo. I'm testing it and haven't been able to get the data to pre-populate on my form. Any help would be appreciated.
 

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
Hi Mike, You said it was a Marketo form on a Marketo page. So navigate to the page in Marketo. You will see which forms are used on that page. Click on it to go to that form. Next click edit to start editing. Please note changes will result in new drafts for every page that uses that form. It might be wise to clone the form and only use it on that page you want. In the form itself you can select the default value. This is where you can insert the token.

9 replies

SanfordWhiteman
New Participant
July 31, 2017

Why use a pURL for this? An unadvertised, unindexed LP has the desired behavior.

Tracey_Bartz1
New Participant
July 31, 2017

Because we're driving people to it via direct mail.

SanfordWhiteman
New Participant
July 31, 2017

OK. Well, the idea behind opting-in to tracking with a pURL is that direct mail can be physically rerouted very easily (i.e. given to/taken by a colleague). If you're ready to take the risk, you can hide the form and submit it automatically, then refresh the page. Then everything is logged by Munchkin.

Justin_Cooperm2
New Participant
August 22, 2016

Here is the current behavior (although we are actually considering changing it):

Assume you are not cookied at all (you've never visited a landing page):

  • When you go to a pURL the tokens on the page WILL be replaced with the value for the lead the pURL corresponds to.
  • Forms will NOT pre-fill (forms only pre-fill based on the user's cookie). We do not pre-fill a form simply because the user navigated to a pURL in the address bar.
  • There is a workaround for forms by making the "Default Value" of your fields a lead token. So, you could make First Name's default value {{lead.First Name}} and it will essentially "prefill" but it's not using Marketo's out-of-the-box prefill functionality.
  • "Visited Webpage" will NOT be logged unless the user fills out and submits a form on the page. Just hitting the page will not log this activity for the lead corresponding to the pURL.

Assume you are already cookied:

  • When you go to a pURL the tokens on the page WILL be replaced with the value from the cookie (NOT the lead linked to the pURL). The cookie always wins.
  • Forms WILL pre-fill (since forms pre-fill based on the user's cookie) with the values corresponding to the cookied lead (NOT the lead linked to the pURL).
  • "Visited Webpage" WILL be logged for the cookied lead (NOT the lead linked to the pURL), even if they don't submit a form.
SanfordWhiteman
New Participant
August 22, 2016
  • There is a workaround for forms by making the "Default Value" of your fields a lead token. So, you could make First Name's default value {{lead.First Name}} and it will essentially "prefill" but it's not using Marketo's out-of-the-box prefill functionality.

And you can create mktoPreFillFields using tokens.  Which is why there are 2, rather than 0, ways to prefill forms on a previously uncookied visit to a pURL, both of which are easy and indistinguishable from regular prefill. That's not the part that can't be done.

The part of pURLs that is definitively broken (as opposed to mildly annoying) is that an anonymous cookie overrides the known lead's Marketo Unique Code/Name.  That's what leads people to think they just plain don't work.  The solution -- which I'll blog about when I get a chance -- involves clearing the cookie before redirecting to the pURL, then associating the old activities.

Justin_Cooperm2
New Participant
August 22, 2016

Yeah, I agree with that. That's not great behavior for already cookied ANONYMOUS leads. We'll look into all this and see if there's some improvements we can make.

January 29, 2014
Thanks Diederik, I was able to get it to pre-populate the data some of the time. It's not a 100%, but it's a start.
Abaran
New Participant
August 22, 2016

Hello

Have you been able to find a reliable solution? I just came off the phone with Marketo support and according to them PURLs cannot pre-populate forms.

I like the idea of using tokens in the form as default values. How is the form know which lead it would take if from? Is this coming from the unique name in the PURL? How reliable is this when the user has cookies on his/her PC/MAC?

Thanks

Axel

SanfordWhiteman
New Participant
August 22, 2016

I just came off the phone with Marketo support and according to them PURLs cannot pre-populate forms.

This is so incorrect it's almost funny.

I wish more people actually understood what "the problem" is with pURLs, including Marketo employees.  There is so much misinformation being repeated.  It's the new "progressive profiling doesn't work on embedded forms" or something.

Accepted solution
January 16, 2014
Hi Mike, You said it was a Marketo form on a Marketo page. So navigate to the page in Marketo. You will see which forms are used on that page. Click on it to go to that form. Next click edit to start editing. Please note changes will result in new drafts for every page that uses that form. It might be wise to clone the form and only use it on that page you want. In the form itself you can select the default value. This is where you can insert the token.
January 14, 2014
Diederik, where I would access the HTML for the form?
January 14, 2014
Jamie, correct Marketo form on a Marketo landing page. Landing page is approved Mark. Dierderik, I will try your suggestion. Thank you all for the feedback!
January 14, 2014
I use this for our US campaigns. Pre-populating forms works on cookie base. pURLs will set the cookie on the page load, but the cookie wasn't present on the page load yet, so the form is not pre-populated until you press F5 to reload the page. What does help is to edit the form itself. Put tokens inside the form values (e.g. {{lead.First Name}}). Now when you use pURLs, you will see the forms are pre-populated.
January 14, 2014
...Also I would check to see if you have any drafts of the landing page not yet approved.
January 13, 2014
To confirm, is this a Marketo form on a Marketo landing page?

Has prepopulation worked on your account previously, or is this the first try?