Dave_Roberts

As Jo mentioned, you'll want to replace the "#" in the VML code with the same variable you've got in the link below. It might look commented out, but that comment isn't a generic HTML comment, it's a Microsoft conditional comment which will actually show up in Outlook. Here's a link to check out mor...

It looks like the VML (Outlook) code you're using for the buttons has the href attribute set to "#". When there is not a link in there, Outlook doesn't recognize the button as a link and does some weird things to display it. This might be what's causing the issue for you, but should probably be fixe...

I'll pile on here to agree with what everyone's said so far. The root of the issue here is most likely what happens to an email once it hits your inbox. Generally the way the email is coded for sending from Marketo to "inbox unknown" is that it has to be able to be received by all the different inb...

No worries, good questions get good answers 🙂 Thanks for raising the question here, a lot of times it'll end up helping folks in the future who run into a similar question to have some options/ideas.

I'm fairly certain that the only way to go about this is via training or a QA process -- the way I've seen it handled in the past is to have the author (editor) hand off the completed asset to another team member or QA team (think branding, spell check, etc) to put a second set of eyes on stuff befo...

No problem, glad I was able to help. When you've got a minute would you mind marking that answer as correct b/c there's a bunch of other ideas in this thread and that'll help anyone else in the future who runs across an issue like this to find a solution more easily. Thanks again for working thru al...

Thanks for following up and giving the button switch a try. I've read thru some of the other suggestions here and would have thought that one of those should have solved the problem. I did some add'l testing this morning and setup a Guided LP template with some variables to match your situation. Wh...

Here's a few additional suggestions:You do not need the mktoModuleScope attribute on your variable - that's an email thing. You might want to choose to use an anchor tag OR a button tag for your button rather than nesting a button inside of an anchor tag. I'd recommend going with the tag (b/c it's editable in using the Rich Text Editor) and adding a class to it for styling... something more like:HTML

​CSS/* default button state */.button { padding: 5px 15px; background-color: transparent; color: #000; border: 1px solid #BBB; border-radius: 6px;}/* active button states (hover, active and focus) */.button:hover, .button:active, .button:focus { background-color: #BBB; color: #fff;}

You'd be further ahead avoiding the Free-Form Landing Pages all together. I think the only reason those are still an option is b/c there are some really old systems that were using them so they couldn't be retired and perhaps some folks that just haven't caught up to speed over the last 10 years. F...

I'm fairly certain that "Mobile Enabled" has something to do with the legacy (Free-Form) version of Landing Pages. Guided Landing Pages are inherently "Mobile-Enabled" -- it's a more modern infrastructure compared to the ancient Free-Form pages which require something like this b/c they were develop...