Justin_Cooperm2

Regarding the first point, the tokens should always be replaced with values corresponding to the person being sent the email. I will take a look at the support case, not sure what happened in your specific case.Regarding the second point, Gregoire already explained a bit, but it is only the Marketo ...

I remember some other community threads that discussed it previously, but can't find them now. Search in here is painful

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...