Whenever we use tokens in our emails and I create a text version (we have Email Editor 2.0 enabled), the token works fine in the HTML email, but shows up as a bunch of code in the text version.
Is anyone else having this problem? Does anyone have any solutions?
Solved! Go to Solution.
are you using a rich text token or text only? Are you saying you created a text version of the email and the token?
When you test it, do you run a sample or a live email to your seed list?
The tokens that seem to be the issue are rich text tokens. And I am referring to the text version of the email. It will copy automatically from HTML, but the tokens will show up as HTML code in both the Marketo previewer and in the test email I send myself.
Go to Admin > Email > Edit Text Editor Settings > Root Block Elements > Email / Snippet Editor and you probably want "None".
Hi Nick and Tony,
We are having the same issues. Updating the Root Block Elements>Email / Snippet Editor to "None" didn't solve it. Bummer. Any other suggestions?
What result are you guys expecting from a Rich Text (i.e. HTML) token in a non-HTML email?
I know it's not designed to work this way, but it would be nice if the "Copy from HTML" functionality formatted the rich text to plain text like it does when you click that button for non-tokenized text in the email body.
But that wouldn't affect the token value as it changes over time, just the the token name (which is kind of the idea of tokenization, that a change immediately propagates).
Hopefully I'm just missing something. In the text editor, my rich text program token looks like this:
Text version of email using token:
That's great. But when I preview or actually send the email, some of the HTML formatting comes over as plaintext:
Even after the change Tony suggested.
This is the expected behavior.
At runtime (send time) the HTML is not down-shifted into a text representation. Nor, in a wide range of cases, would you want it to be. Try running textContent() on a link that wraps text, for example. You'll get all the inner text, including carriage returns, and none of the HTML-based formatting, like margins and paragraph containers, that stops words from running together. It's not a conversion that's safe to make without hand-editing (you can still edit the text version of an email, but you wouldn't ever be able to edit the automatic text-ifying of an HTML token).