Justin_Cooperm2

Valerie, I think there is some confusion here. This feature is very similar to when a user marks an email as spam. In this case, sometimes a user's email service will notify Marketo via a feedback loop that the message was marked as spam. The user is not directed to any live URL, they just click "ma...

If you want a US-formatted date (ex: "9/22/2016") for pacific time, here you go:#set( $myDate = $date.getSystemDate() )#set( $calendarObj = $convert.toCalendar($myDate) )## Change Time Zone to Pacific (System Time is Central)$calendarObj.add(10,-2) #set( $output = $date.format('M/d/yyyy', $calendarO...

@Valerie, as Sanford said, this has nothing to do with your email's content. This is a "header" of the email message that we add to your emails to make that button work correctly in things like gmail, outlook.com, iOS, etc... Basically, you don't have to worry about it, Marketo will unsubscribe the ...

For #2, modules count as a "marketo-specific element" so existing modules in an individual email also do NOT take on template changes. This is both expected and desirable. The idea is once you insert a templatized module into your email, that module now lives on its own in the email. This is why you...

someone likes me

It's because when you load a template it appends it to the email...we don't scan the existing contents and try to determine where to put the template contents. My recommendation would be only load a template with an empty compose window, then you can add your signature. You can also file an idea to ...

We support this. It's the "list-unsubscribe" header in the email, which sends the email to a mktomail.com address

I can't reproduce your issue.But, I probably know why you are seeing this. This is how it works:In Email 1.0, we only had "rich text" elements. You would define them in your template as "mktEditable". If you created an email from the template and CHANGED the default contents of one of those "rich te...

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

Yeah, can you paste a screenshot of both smart lists and results? Did you click "refresh" on both? That definitely shouldn't happen.