Solved! Go to Solution.
I am desperate to solve this issue, and I'm not laughing...
I posted a recipe for adding a ReCAPTCHA to Marketo forms a couple of months ago -- search for it.
The claim that you can't add CAPTCHA to Marketo forms hasn't been true since webhooks have been available.
Thank you. I wrote that out of frustration/humor, but I'm not completely helpless. Possible solutions include:
1) Creating a "honeypot" or hidden field that filters anyone who fills it out to a Smart List for deletion Stop 99% of Your Spam Leads with Marketo | Fab Capodicasa | LinkedIn
2) Adding CAPTCHA - MktoForms2 :: reCAPTCHA (your link from another article)
3) Hiring a web developer - Add JavaScript validation to the header of your landing pages. This checks to see if JavaScript is enabled on the browser - and, if not, redirects the lead to a page that advises them to do so. Spam bots do not have Javascript enabled.
4) Adding a script that restricts certain parameters ex. Email Domain http://developers.marketo.com/blog/restrict-free-email-domains-on-form-fill-out/
While all of these are valid solutions I still find myself a bit lost here. My personal solution for the time being is to take the Smart Lists that I've already created (This article is helpful for setting those up - http://developers.marketo.com/blog/how-to-clean-your-marketo-database/ ) to identify the spam leads using several filters and simply add a Flow step to delete them as they're identified.
While all of these are valid solutions I still find myself a bit lost here.
Surely spammers aren't ramming through your reCAPTCHA. You mean you haven't rolled it out, right?
Exactly, I'm doing my due diligence before I move forward with any of the above steps.
OK. #3 still doesn't make any sense. Spambots don't care if there's a JS relocation or a <META> redirect. If they can discover and submit a rendered form on page X, they will. Now, if the form only exists after a script has run (as with Forms 2.0 embed code) you might realize some benefits; if the rendered page is inspected, the endpoint is clear to see, but that does take a bit more work.
For full protection, because Marketo endpoints always follow a clear architecture that doesn't even require a landing page to exist at all, you need to get away from the idea of concealing the form fields themselves and instead make the form fields' expected contents hard to spoof. This is why #1 can work by virtue of "expecting empty" and is really the core idea of #2.
Wow, great response. I actually came to the same conclusion as well (with a little less science) and made the recommendation for my team to apply solutions 1 & 2 to all future forms (and past as well). Especially because both are solutions that I could implement on my own.
In addition, I did setup the New Smart Campaign that identifies anyone who fills out fields on a form with entries I've identified with spam such as "123456" for phone number, etc. I set it run automatically once every hour.
I'll be a happy camper once all of this is setup and the spam is behind me. Thanks for talking this through with me. Cheers!
Thomas - would you be comfortable sharing your filtering criteria for the smart campaign?
Can I add CAPTCHA to a Marketo form?
No, you cannot, but you also should not need to. Marketo has a built in protection mechanism that helps tremendously with reducing the number of spam form fills. Adding a CAPTCHA would negatively impact your legitimate conversion rates.
3. Same as the first link.
If I weren't kinda desperate to solve this issue, I'd laugh 🙂
Unfortunately the three Marketo document links are no longer available