Hello Sandford,
for that question, I would need to talk with our web devs - but as far as I remember, there were issues with styling the forms in Marketo, and that some functions did not work well (such as custom lightbox behaviour or making the form responsive was straining because overriding Marketo's standard settings). And istn't a marketo form obligatory for using the Form API?
We do keep the possibility of Denial of Service in mind, but that is a different story.
So back to the topic, I guess it is not possible that the "Data value changed" trigger works on fields with previous value empty?
And istn't a marketo form obligatory for using the Form API? |
No, it's not necessary.
You can use the Forms API -- a background Marketo form submit -- to submit values from a custom form.
We do keep the possibility of Denial of Service in mind, but that is a different story. |
Well, it's kind of the same story, since even a minor attack on a REST-based form will bring it down and the rest of your REST-based integrations, too, unless there's actual technical protection.
| So back to the topic, I guess it is not possible that the "Data value changed" trigger works on fields with previous value empty? |
It works on fields that change from blank to empty.
It doesn't work on fields that are created non-empty alongside a new lead.