Dan_Stevens_

I just finished testing... AND IT WORKS!!!! Thanks so much, Justin Cooperman​! BTW, it's not just the DOCTYPE that caused the issues, but Marketo was also stripping the xmlns definitions within the tag, just after the DOCTYPE. These critical three lines of code are also being preserved.

Existing idea (a different use-case, but nested functionality nonetheless): . I agree, it would be very helpful to allow tokens to be nested within existing tokens.

I agree - especially as we try to enforce brand-compliant assets within our emails and landing pages. It gets tricky when the call-to-action text expands beyond the width of the button (like when we translate to German text).

Couldn't agree more - this is long overdue. The current approach does not scale well with a global organization with 20+ workspaces.

This is a boolean field (0/1; TRUE/FALSE). What is your use-case for communicating an actual "unsubscribed"/"subscribed" value? For example, when you run a smart list and include the "unsubscribe" field, the value will be TRUE or FALSE. That's worked well for us.

While I agree that code cleanup in the wysiwyg editor often causes more harm than good, the other issue - actually the main one that Marketo has yet to fix - has nothing to do with the editor. It's simply stripping out compliant code that's pasted/entered into the HTML window of the template. ​

One use-case is a re-use a flow-step with multiple choices. Of course, setting this up a separate smart campaign could work and just "request the campaign" from the main smart campaign - but that's not always an option.