SanfordWhiteman

I think of this not as a Munchkin (Visit Web Page) issue but a click tracking (Click Email) issue.For Munchkin, it's fixable by stripping off unwanted query params before running Munchkin.init() (easy in FF/Chrome/Safari/IE10+). For click tracking, you don't get that luxury as the link is stored af...

+1 to everything Greg said. The maximum possible height of the form including visibility rules is not computed. It would be impossible for Marketo to do this on the server, in any case, since they have no idea of what other CSS you're applying to the form. (Not sure why you'd want to fit to the m...

You don't have to serialize, but use a sharding algorithm so updates for the same lead are processed by the same worker. There's no utility to attempting parallel upserts of the same record (and certainly no guarantee that updates will be applied in order).

Are you running upserts in parallel?

Rather than creating a field in Marketo for every field on the custom object, consider using a single Mkto textarea. You can store a very, very large number of fields as JSON text. It makes maintenance much easier and (to my mind) it is less clutter to have a single field used to transport all the...

Nice one!You didn't need to do that for Typeform, though. You can pass the Marketo token as a hidden field to and from Typeform, so the Thank You URL (on your website) gets associated with the lead.

You can include whatever variables you want in the page and have the onSuccess determine which value to switch in for the Thank You URL based on the current value of a query param. On a Marketo LP, you can include {{my.tokens}} proper. On a non-Marketo page, you can include the possible token valu...

Using the REST API for single form posts is not recommended.Forms 2.0 API posts are the way to go.

My demo specifically allows leads to upload a file along with a form. Did you actually try it?I also use a third-party service to accomplish this when the file sizes are more variable (the method above is suited for small images such as avatars). The service meshes effortlessly with Marketo. You ...

Post the URL of the form and I'll take a look. The CNAME trick can be easily foiled by an in-depth check, of course. You can route around just about anything like this (say, by going through a non-Marketo IP) but at a certain point there are diminishing returns.