Justin_Cooperm2

That's a bug that it doesn't interpret the LP Template tag. I will file a ticket.

I like the idea, but I wouldn't make it a template variable, I would actually make it so when you click "Edit Form" in the Guided LP editor that it could expose some lightweight customization for you.

Frank Passantino​ should be able to show you how some of this can be achieved today.

There's not a simple way for us to automatically know how you will use a template, but there's no reason you can't add the line inside your own templates. Have you tried that? Alternatively, you can just edit the values on an individual landing page using the method described here: http://docs.mark...

Is it resolved now? I see it working for me. I want to make sure it works for you as well.

The feature is supposed to be working but looks like we have an open P1 bug open this feature in both Email 1.0 and Email 2.0 (makes no difference). Should be fixed ASAP.P.S. switch to Email 2.0! It has full parity (+ more) with Email 1.0. We'll be moving all customers over anyway in 2017.

+1, and see mine. Our product offers support for local or global variables. Whether a variable is local or global is determined by how it is defined in the email template. If you mark them as mktoModuleScope="true" in your template, they will become local variables. If you want to make any changes t...

Greg is correct. We have delivered product functionality to enable variables to be either local or global in scope.Our syntax is defined here: Email Template Syntax - Marketo Docs - Product Docs and it is the mktoModuleScope attribute that determines whether your variables are local (true) or global...

We already have a ticket open on this one. Shouldn't be too long before we address it. Justin

We just released "module level variables" that supports this exactly the way you want. Just add mktoModuleScope="true" to any variables in your template you want to work that way.https://docs.marketo.com/display/DOCS/Release+Notes%3A+Summer+