Introducing Code Anatomy, an ongoing series of posts

Code Anatomy is a new series where you'll see how I build those critical little helper functions that make developing Forms 2.0 and FlowBoost scripts (as well

TYL: Use target="_blank" for multiple assets on the same LP

I keep some Marketo factoids close to the vest (hey, gotta get paid for something!) but if you read the fine print of my Community responses, you'll see

A little Velocity math trick and a note on empty lists

Couple of li'l technotes today in response to reader questions. Note #1: Generating random numbers in VTL First topic came from user PW. He'd been searching

Munchkin is broken (by default) for 2-letter TLDs

A question from top Marketo user GM in this post [https://nation.marketo.com/message/118377] led to an interesting, even disturbing, hour of troubleshooting. Finally, I've gotten

Sorting objects and lists in Velocity

A shameless reprint of my answer on this Community thread [https://nation.marketo.com/message/143082]. As Marketo user TR pointed out, the docs claim custom objects are sorted by

Using Marketo JSON fields in Velocity (and beyond)

I'm a big fan of using Text type fields (a.k.a. textareas) to store blocks of JSON. Such fields become a sort of poor rich man'

Using option groups (<OPTGROUP>) in Forms 2.0 picklists

Though Marketo forms use standard HTML input types (which is a very good thing for cross-platform compatibility) there are a few subtypes and niche uses that aren't supported

Safely customizing Munchkin options on Marketo LPs [Updated 2016-10-02]

Whether you're using a .ly or .io domain for coolness's sake, or if you legitimately operate out of a ccTLD like .fr or .mx, you need