Skip navigation
All Places > New York User Group > Blog > 2017 > August

     It's easier to customize a Marketo form if it's completely destyled to start. A float or margin-left that doesn't seem to respond to !important can drive a designer crazy, and time spent on CSS specificity & cascade behavior isn't well spent.

My li'l snippet for removing Marketo's built-in styles has seen a lot of use via the Community and a few code versions (now at the venerable v1.103) but it hasn't appeared on the blog before.

Here's a sample form with the Simple theme:

And here's that same form after running destyleMktoForm to reset it to browser defaults (check out the Times New Roman):


Let's dive into the destyleMktoForm function a bit, since I always insist on a teachable moment

Read the full post on TEKNKL :: Blog →

     Continuing this series thanks to a prod from user KS on the Field Limits doc:


Does URL field type have a character limit?


     Indeed it does: 255 characters.  And unlike with Integer fields this restriction is in sync with the SFDC field type of the same name, which also is limited to 255.


     This wouldn't be a problem, save for the fact that Marketo can't truncate longer URLs (including pathnames and query strings) to a guaranteed working URL.


     See, an implicitly-fully-qualified domain name like or not including any leading or trailing URL components like https:// or the /path/name?query=string must indeed be under 255 characters. (In fact it must be under 253.)


     So if you're only storing pre-parsed domain names, there's no problem with the max field length.


     But if your source could be a full Referrer URL, or a long URL from your product catalog, it's certainly possible to go over 255 characters.



Read the full post on TEKNKL :: Blog →

     If there's one official Marketo doc that needs some edits, it's the Marketo Field Limits by Field Type rundown.


     Unfortunately, that article has incorrect info and some sins-of-omission.


     Be warned: most of this post is (necessarily) dry and technical. But I always find competing claims to be interesting, almost regardless of the topic. Maybe you will too! Plus, even experienced high-level programmers (meaning languages other than C and C++) don't have this stuff at their fingertips, and may make implementation mistakes as a result. So if you're in a meeting and want to show some mild “data scientist” chops, these are good facts to drop.


     I'll be adding to this series over time. To start off...



From the doc:



Values are limited to between -9223372036854775808 and 9223372036854775807.


     This is technically correct.


     Marketo stores Integer fields as signed 64-bit integers — signed meaning they can be negative or positive — so they fall into the range of -(2^63) to +(2^63-1). It can be useful to look at the high number in an easier-to-read way:


9 223 372 036 854 775 807


     So 9 quintillion, 223 quadrillion, 372 trillion something.


     If such a number seems unimaginably high in a martech scenario, I fully agree (though don't forget the ol' Grain of Rice parable).


     But the truth is you can only safely go up to the max value if you don't integrate any other apps with Marketo. No Salesforce, no JavaScript, no 32-bit PHP apps or older databases. When you integrate, the actual limit can be a tiny fraction of that.



Read the full post on TEKNKL :: Blog →

     When you use the default Forms 2.0 embed code, the form descriptor loads asynchronously. This means the inner HTML of the <form> tag isn't rendered until after the initial scaffolding of the page is finished drawing (often immediately after, but always after).


     (The descriptor is the meat of the form config, managed in Form Editor: the fields, field order, validation rules, inter-field dependencies, custom CSS styles, all that stuff.)


     Let me take care to say that this is a totally sensible default. Marketo can't know how many other asynchronous components are present on your page. You could have multiple content panes filled via Ajax, as and a bunch of other 3rd-party asynchronous widgets. In the absence of other info, and not knowing if the site is a complex corporate website or a simple (non-Marketo) LP, it makes sense to not have the form block other parts of the page from loading.


     Nevertheless, in practice you may notice an uncomfortable reflow of other elements as the <form> builds out its content, bulging into a larger area of the page. Floats can shift to a new row and such.



Read the full post on TEKNKL :: Blog →

     If you want to tweak your robots.txt for protection against unwanted search engine indexing, the widely-circulated answer is that only Marketo Support can do this.


     That's not actually true, though. You can do it yourself.



Read the full post on TEKNKL :: Blog →