Will_Thomas

Actually - I was able to find it. https://codepen.io/figureone/pen/RoKZWg looks to be the pen. Sorry for the spam.

Looking at the Wayback Machine - it looks like you do have the codepen embedded on the page, however your link ( https://codepen.io//figureone/embed/RoKZWg?height=550&theme-id=16924&slug-hash=RoKZWg&default-tab=result%2Cjs&user=figureone&embed-version=2&pen-title=MktoForms2%20%3A%3A%20Client-Side%20...

Hey Sanford - thanks for that article. I noticed though that the JS code you mentioned isn't actually linked on the page. Could you take a look at it? We're trying to do the exact same thing and I'd like to save my web team some work.>You can grab sample code from the Pen below.

Exactly. I'm trying to make this simple enough that my whole team can use it with little issue, which I could have done using my tokens. At this point though, sounds like a wash. Thanks anyways, I've been referencing your comments about velocity all over the forum.

The reason I was using Velocity was because we want to be able to randomize the order of dynamic content, as well. I was essentially trying to recreate segmentations here, so that I could use the velocity randomizer (which you created here Lightweight A/B testing using Velocity ) to determine the o...

I think you might be onto something there Courtney. Your comment triggered the marketo thread update email to be identified as spam itself.

I just built and sent one of Marketo's example templates to myself and it still had the phishing warning - but a blank template text email didn't have a warning. Looks like it's something to do with more complex html.

We had the same issue starting today - all emails we sent are getting flagged as potential phishing attempts, even ones we have been sending for years.

Thanks for posting this and to TrustArc for the content here - this has been the most concise overview of necessary changes I've seen so far. It'll really help us make sure we're compliant.