SanfordWhiteman

Actually does work, just need to tweak the output slightly: http://blog.teknkl.com/those-bulletproof-buttons-are-also-tracking-proof/Voted up for an official setting to choose which tags + attribute combos will be rewritten (shouldn't be artificially limited to urn:schemas-microsoft-com:vml:roundrec...

It's craziness, eh? This is why I sigh when a client has upgraded to 2.0 without asking first...

Sean Day​ this post is a must-read: http://blog.teknkl.com/yes-you-can-use-emojis-in-marketo-subject-lines/

Totally.

Dupe like Dan said... also note that Velocity (email script) tokens can in fact be nested, or more precisely, share internal variables.So in your example:----BEGIN TOKEN 1----#set( $eventDescription = {"name" : "blah","date": "2017-02-15"} )----END TOKEN 1--------BEGIN TOKEN 2----${eventDescription....

I sympathize with this, and it's one of several good reasons that the small expense of running your LPs through your own CDN returns to you many times over.The immediate advice I'd give is to clone the page to a new LP now that testing is done (and move the URL over, too).

The absence of this feature is why I have no hesitation in saying most integrations are not professional-class (let alone enterprise-class). I'd still make the point for other reasons (the low API limit itself is still a DoS waiting to happen) but the fact that calls are shared is ridic. Big +10!

If you change this behavior, it means everyone who relies on this age-old, widely understood behavior suddenly has a possibly catastrophic change ("BC" == "Backward Compatibility"). That's not how professional software platforms need to work.Creating a new feature that behaves how you want, provided...

This behavior can't be changed as it would cause a catastrophic BC break. Perhaps a new feature that could be turned on per-instance or per-SC, but this cannot be the new default.The current behavior also makes sense because it avoids ambiguity. You need to consider cases where a date token is pull...

Thanks for updatin'.