Tokens aren't supported in the WYSIWYG preheader. It will work if you use your own custom one that is part of your template.Justin

Any web font should work fine. We don't do any validation on that stuff. Are you including the reference in a LP or Email Template? You're saying that when you "Approve" the template, it won't complete? That's not expected so if you can elaborate a bit we can look into it.Justin

Yes it works for shared Snippets

It's in our syntax doc:Default value (optional)mktoDefaultSnippetId: The numerical ID of the Marketo Snippet that should appear by default (will only work if a Snippet with that ID exists and is approved in that workspace).

This is planned to be released over the weekend. Should work on Monday.

This could be so many things Lauren. One thing I will guess is that you have your rich-text editor set to have a "root block" of either

or

Yes, we resolved it offline. It was just an issue with how the modules and containers were defined.

You can actually make any HTML element a rich-text region in your email using class="mktEditable". If you do this, you can add any inline styles you want to your email and they will be reflected if the user just opens up the rich-text editor and edits the text. We have a setting on the text editor t...

Easiest answer is that we're not yet living in a world where many email clients handle css that is in the section of the code. In fact, many will strip it out entirely. So, if you were to simply surround some text with

it may have unintended consequences...some email clients would fall back to som

If you edit anything in a template outside of a Marketo Element or Module (defined here: https://docs.marketo.com/display/DOCS/Email+Template+Syntax ), it will break the template from the email. At that point, modules that are currently in the email will still be there, but you won't be able to inse...