SanfordWhiteman

OK. That code looks very hard to maintain (string constants should be kept as separate as possible, and I would recommend using a lookup table of IDs and classes). But if it works for you...

You want to add a Forms 2.0 onSuccess listener (this isn't specific to lightboxed/unlightboxed).For example: MktoForms2 :: Thank You HTML​.

What's in the robots.txt for your domain? Paste the whole thing here or tell me an example URL.

Just add the classes yourself, as in MktoForms2 :: Radio Button Images

All the logic you talk about can be done by attaching Munchkin function calls to single or multiple pointer/touch events (mouseenter, mouseout, etc.).However, you will have to engage a front-end developer to do this. It's technical work that is not part of the canned Marketo offering.If you want to ...

John, obvs. that would work, but when you're parsing client-side that means you are going to use up your API calls on unwanted records.

Depends on your layout, but you can do something like this.I also recommend looking at my destyled form demo here. If you're looking to do major overhauls of the form layout, you should strip out as many of the built-in styles as possible.

It's extremely easy to run Munchkin::viewWebPage after 10 seconds so you can report on those interesting views.Whether that metric always means what you think it means is up to you...

It's very disappointing if you were explicitly told that LP views will not be counted correctly. Sounds like Mkto Support was shooting themselves in the foot. Quite honestly, I'd go back and say that's not an acceptable response. When you say "huge," what are the raw numbers and the deltas? What ...

Just add a margin with CSS:.mktoFormRow { margin-bottom: 20px !important;}