Sanford, hopefully this will clear up some confusion. Let me give you a bit of background. Previously on our site we kept track of all the user's subscriptions and email preferences. Recently the decision was made to offload this responsibility to Marketo, so we're having to make changes within our site to no longer track the user's subscriptions and email preferences ourselves. The effort was made to migrate this data over to Marketo, but the problem is from the end-users perspective they don't know anything has changed. Meaning, they still login to our site and can edit their profile. However, when they're editing their profile they no longer see the options for their subscriptions and email preferences (since these got moved into Marketo), so instead they'll see a link in place of where this data used to be to "click here to manage your subscriptions and email preferences" which takes them to this marketo landing page I've been discussing.  Early on the discussion was to either keep the user on our site (on the same profile page) and just present a form to them (pulled from marketo) to allow them to manage their subscriptions/preferences here OR to create a separate landing page that we then just provide a link and send the user to a marketo landing page.  Does this clarify some of this? ... View more

Sorry, let me clarify what I meant by manually setting the values. In your JS you have something that looks like this:  var init_fields = { "Email" : "{{lead.Email Address}}" , "emailPreferencesPause" : "{{lead.Email Preferences - Pause}}" , "emailPreferencesPauseUTCTimestamp" : "{{lead.Email Preferences - Pause UTC Timestamp}}" } By manually setting the email field I meant I did this (just to see if the JS is firing):  var init_fields = { "Email" : "test@testing.com" , "emailPreferencesPause" : "{{lead.Email Preferences - Pause}}" , "emailPreferencesPauseUTCTimestamp" : "{{lead.Email Preferences - Pause UTC Timestamp}}" } It works when I manually set the values, so I know it's firing. Based on your last answer it sounds like this just simply isn't possible with how we're trying to do this. So then my question becomes is it better to just pull in the form into our own domain and have the user manage their subscriptions/etc through this form we're pulling in from Marketo?  ... View more

Sanford Whiteman‌ what do you mean? You can't use query strings for this on IE? ... View more

Jay Jiang, I appreciate you answering my questions here. I went through your pre-fill workaround and I can manually set the values for the fields in the form, but when I use the {{ lead.Email }} or {{ lead.Email Address }} it doesn't actually populate anything. I just want to be clear here, the user is on a separate domain and when they click on a link to view their profile they are presented with a link to "manage their subscriptions" this link takes them to a marketo landing page which contains the form I'd like to pre-fill with their data. On our domain (non-marketo) I'm making a request to associate the lead with the munchkin cookie already created.  My question is if I'm missing a step somewhere in order for the {{ lead.Email }} to work how you have in your pre-fill workaround? Is all that's required for this to work is for me to associate the lead 'before' sending them onto the marketo landing page? ... View more

Jay, this is actually what I was hoping I could do is pass the marketo user id or some other data as a query string over to the landing page and have it populate the form based on looking up the user's data with the data I'm sending it. However, I can't find any documentation on this type of functionality. Instead, it seems like you're supposed to associate the lead (which I am currently doing), but it still doesn't populate the form. According to Sanford, this functionality isn't readily available out of the box. Do you know of a way to just send some user data along with the query string to have the landing page pre-fill the form based on what's in the query string?  ... View more