SOLVED

Tokens vs 'view as webpage' email template

Go to solution
Highlighted

Tokens vs 'view as webpage' email template

Currently I am working on new email templates. Since it is best practice to include a 'view as webpage' link, we will finally start using this within the new templates. But now I have a problem with this.

Once a lead is created, fields like 'business unit address', 'social media links', 'contact page' and 'unsubscribe page' are filled with HTML so they fit with the email template. Every lead gets different links to different pages depending on their country and language. Within the email template we use tokens to populate the right business unit address, social media links, contact page and unsubscribe page. This all works when testing and sending emails. The HTML is transferred into the icons etc

Problem HTML 2.png

But..

We include a 'view as webpage' link in the email. If you open this webpage, you will see the actual HTML and not the icons etc..

Problem HTML.png

Any solution for this?

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Tokens vs 'view as webpage' email template

Hi again Marit,

The functionality only works when you send the email through "send sample" or "send email" flow step.

-Greg

View solution in original post

10 REPLIES 10
Highlighted

Re: Tokens vs 'view as webpage' email template

Hi Marit,

How is your "view as web page" set up ? the {{system.viewAsWebpageLink}} token should be used as the href value in the <a> tag.

Typically

If you cannot read this email <a href="{{system.viewAsWebpageLink}}">Click here</a>

-Greg

Highlighted

Re: Tokens vs 'view as webpage' email template

Hi Greg,

Thanks!

Yes it is build this way! <a href="{{system.viewAsWebpageLink}}" style="color: #00bae9; text-decoration: none;">View as a webpage</a>

Highlighted

Re: Tokens vs 'view as webpage' email template

Hi again Marit,

The functionality only works when you send the email through "send sample" or "send email" flow step.

-Greg

View solution in original post

Highlighted

Re: Tokens vs 'view as webpage' email template

That's too bad

Thanks for your answer Greg

Highlighted
Level 10 - Community Moderator

Re: Tokens vs 'view as webpage' email template

Tokens* are supported in Web View.  In fact if you're seeing the contents of your tokens, they're obviously being fetched correctly. It sounds more like there's something strange in your markup (HTML).

*But not email script tokens.

Highlighted
Level 2

Re: Tokens vs 'view as webpage' email template

Is there an existing Idea on Community where we can upvote the problem of Email Scripts not being accessible to the web view? Or is there another way to make custom object data visible to the web view version?

Level 10 - Community Moderator

Re: Tokens vs 'view as webpage' email template

It's acknowledged as a bug, so it doesn't need an Idea. Marketo support actually didn't know it wasn't working on all instances: apparently, there are some instances/pods on which it functions as we'd like.  I have a case open and am waiting for a sucessfull update.

Highlighted
Level 1

Re: Tokens vs 'view as webpage' email template

Hi Sanford,

 

Did we ever get a resolution to this bug; email scripts not being rendered in webpage view for emails?

 

Thanks.

Highlighted

Re: Tokens vs 'view as webpage' email template

Email Scripts should execute in the web viewer. If they don't, it's a bug.

Tokens will also be replaced in the web viewer, however they currently they will all be HTML-encoded. We have a ticket open to bypass HTML-encoding tokens for fields that have been set that way in Field Management HTML Encoding Settings.