Christophe Arn - 6 years ago
Successfully moved from 50 spam leads per day to 0...
- by adding a Google reCaptcha
- by validating fields values using jquery (email fields, phone number, etc.)
- by using a pHp form processor instead of the direct call to the Salesforce servlet
- by checking (in the pHp form processor) the sender details using the Askimet API
- by checking (in the pHp form processor) that the email address does really exists
Multiple bareers, true, but efficient enough.
Happy to provide services to anyone willing to secure his web-to-lead form
www.smarsys.com or email@example.com
Philip Faulconer - 6 years ago
I see from this post that many of you have had problems with spam on your web-to-lead implementation. My company launched our "Spam Captcha for Web-to-Lead" AppExchange application: https://appexchange.salesforce.com/listingDetail?listingId=a0N3000000B3nQREAZ This app is super simple to setup and then it blocks spam using the Google reCaptch solution.
Want to use our solution to block spam leads for free for the next three months? If so, simply install the AppExchange application and let me know that you found it through this thread so I can send you a coupon code.
Propeller Development is a Salesforce Cloud Alliance Consulting Partner and a Salesforce ISV (AppExchange) Partner. We've launched our "Spam Captcha for Web-to-Lead" AppExchange application. It's a really easy to use spam blocking solution for web-to-lead forms. It uses the industry leading Google reCaptcha solution to make sure a human is filling out the form.
In trying to address your spam problem, you may have discovered the following approaches. There are a number of DIY solutions for dealing with spam that vary in effectiveness and complexity. Here are several prominent approaches:
We think you'll prefer our solution, but there are also a few other AppExchange offerings:
Spam Check by Arrowpointe Corp.
This solution requires you to configure and use a Salesforce Site to implement - this requires serious technical skills.
JunkIt! by CloudLogistix, Inc.
This solution tries to clean up spam after it's already in your lead list. We believe it's better to prevent spam in the first place
All of the above approaches either require work to clean up spam after it's already in your lead list or require a lot of technical know-how to implement. We've worked hard to create a solution that's super easy to setup and use. There's a quick setup process and then you can forget about it as it works smoothly in the background.
Sephine Merlehan - 7 years ago
It's ridiculous that salesforce has not done something about this already.
We have had this problem for YEARS and this "Idea" has been here over a year with 3250 votes and nothing has been done about it?
Seriously considering switching away from SF.com. Now spammers have our oid there is nothing we can do.
Stony Grunow - 7 years ago
We keep on getting Web to Lead Spam, and haven't found a perfect solution yet.
What we have been able to do is identify 90 plus percent of it with automated filters since starting to use Daddy Analytics, which was originally designed to replace Salesforce for Google Adwords.
Ronald Jansen - 7 years ago
Hi, SalesForce Users.
To inform you: My original post is from October 2006. This is more than 6 years ago and the SPAMMERS get better every day.
Salesforce told me in 2006, the policy is to capture as much leads as possible. Making it difficult to post a lead is not wanted from a marketing perspective.
In the time other software has develloped that can helpt.
My advise: hide your OID, put a CAPTCHA on the webform; Make the CAPTCHA dynamic if possible (it should adapt itself automatic when more spam is suspected). The Drupal CMS has something like this that is called Mollum. This is a SPAM monitor and looks further than just your website. Hope this helps the reduce SPAM and get more quality leads.
Ronald Jansen - 7 years ago
My original post Web 2 Lead & webform spam is from a long time ago. Very strange Salesforce didn't do anything to make it more difficult for spammers. The same problem arises when you have a webform on your website without any protection. I have now integrated the Salesforce Web2Lead with a Drupal website; The OID is hidden and I've included a CAPTCHA.
Checking out the better Content Management Systems (like Drupal), you can find integration modules that solve problems. One of them is Form SPAM.
Suggest to use the web2lead integration if you can mask the OID with additional code or a standard module that is available for Drupal.
Elisabeth Stonehill - 7 years ago
We are newbies in the web-to-case and web-to-lead arena. And we have been discovered by the web-to-salesforce spammers. Naively, we created our original pages that exposed our OID. Despite the fact that we have validations on our submit pages, spammers are posting directly to Salesforce completely bypassing our forms (and servers).
It does seem like a simple solution would be for Salesforce to allow an organization to have a list of allowed referrer pages - and reject any posts that do not come from those locations.
But now we are going to have to try to put in place all sorts of mechanisms to slow down the spammers. Lots of us out there coming up with our own custom solutions that really should be handled by our common Service Provider - Salesforce.