I've tested the above and it's working fine. Now, what's next? Do I have another Trigger for Data Value Changed for ReCAPTCHA_Verified? |
Yep.
If so, how do you know which form the lead just filled out? Are you storing the form name in some other Marketo field in the Filled Out Form trigger? |
You can store the form names in a history field if you need this info, but remember, until you delete the lead completely (which you should after a time to save both $ and database clutter) the Filled Out Form activity is in the the lead's history. So you can run a Smart List to see which "people" were bots and then group by the form(s) they came in from.
What you most need to manage aren't the persistently failing leads, but those that already exist as good leads but are later submitted by a bot (a targeted attack against that person, who knows?). So check that the lead was created by the bad form fillout. Of course you also should be blocking/staging field updates or else you're letting somebody overwrite fields even if they fail the ReCAPTCHA (this happens before you even check Google). There are many form data cases that the vast majority of people don't bother with, unfortunately.
Does your workflow handle multiple form submissions? For instance, if you had two, three, or four forms that the user could fill out. Would you have to have separate webhooks and triggers for each form to prevent collisions (i.e. submitting two+ forms at the same time)? |
In theory, not just different webhooks but different hidden fields to store ReCAPTCHA end user responses. But really, if you only take positive action when somebody passes ReCAPTCHA (otherwise, they're quarantined) it doesn't matter if the bot forces itself to fail the Google endpoint lookup by submitting a lot of forms. They'll still fail.
.png)