Every Marketo field has a Friendly name, a Token name, a Form Field name, a REST API name, a SOAP API name, and a Velocity name — and they may all be different!
Feels weird to be writing about this at such a late date, but there’s misinformation going around, perhaps AI-influenced.
The spur for this post was the erroneous claim that Marketo Forms 2.0 uses REST API names as Form Field names. That is, if the REST API name is email the corresponding form field is <input name="email">.
That’s clearly untrue, as you can see by inspecting the HTML of a basic form:
But even the response I gave on the Nation — No, it uses the SOAP API name — isn’t true 100.00% of the time. Don’t get me wrong: it’s true enough to get you through 99.99% of scenarios, and infinitely true-er than the false claim about the REST API name. It’s certainly true for the system field that holds the lead’s email address, i.e. the one with the default Friendly Name Email.
(Knowing all the different names a field can have makes it harder to refer to fields, right? We usually choose the Friendly Name, even if that one can change over time!)
&nbs
