Comments on: Viagra, Salesforce, and the Power of Consumers http://www.grokdotcom.com/2007/02/26/viagra-salesforce-and-the-power-of-consumers/ Marketing blog focused on marketing optimization, improving website conversion rates, search engine marketing, web analytics, word of mouth, etc. Sat, 21 Nov 2009 19:57:59 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: Mica Kingsley http://www.grokdotcom.com/2007/02/26/viagra-salesforce-and-the-power-of-consumers/comment-page-1/#comment-267585 Mica Kingsley Sun, 21 Oct 2007 22:28:49 +0000 http://www.grokdotcom.com/2007/02/26/viagra-salesforce-and-the-power-of-consumers/#comment-267585 they'll have you suicidal suicida. Mica Kingsley. they’ll have you suicidal suicida. Mica Kingsley.

]]> By: Sebastien http://www.grokdotcom.com/2007/02/26/viagra-salesforce-and-the-power-of-consumers/comment-page-1/#comment-246925 Sebastien Thu, 11 Oct 2007 13:55:15 +0000 http://www.grokdotcom.com/2007/02/26/viagra-salesforce-and-the-power-of-consumers/#comment-246925 Spamming is a major problem when implementing a web-to-lead solution. Unfortunately the default Salesforce web-to-lead utility does not provide any anti spam functionalities yet, which might prevent some Salesforce user to successfully implement an effective Web-to-Lead strategy. For anyone willing to fill the gap between their website and Salesforce without worrying about spam, I suggest using FormVester (available form the AppExchange). FormVester generate leads form any of your existing online forms, without the hassle of reprogramming them…and it is spam-free. The reason is that, it works by adding a snippet tracking code into your website pages (that will execute a hosted script), so that, no OID number is ever exposed in the source code of the page. Spam bots are then not able to take advantage of this number ensuring a clean spam-free lead generation. An interesting other thing about FormVester, as opposed to the default Salesforce Web-to-Lead utility, is that it always checks if a lead already exists in Salesforce before creating/updating it (using a 6 rules based filter) so that it will never duplicate the lead. Give it a try!<a href="http://www.salesforce.com/appexchange/detail_overview.jsp?NavCode__c=&id=a0330000002YXhxAAG" rel="nofollow"> FormVester for AppExchange</a> Hope it will help! Spamming is a major problem when implementing a web-to-lead solution.
Unfortunately the default Salesforce web-to-lead utility does not provide any anti spam functionalities yet, which might prevent some Salesforce user to successfully implement an effective Web-to-Lead strategy.
For anyone willing to fill the gap between their website and Salesforce without worrying about spam, I suggest using FormVester (available form the AppExchange).
FormVester generate leads form any of your existing online forms, without the hassle of reprogramming them…and it is spam-free. The reason is that, it works by adding a snippet tracking code into your website pages (that will execute a hosted script), so that, no OID number is ever exposed in the source code of the page. Spam bots are then not able to take advantage of this number ensuring a clean spam-free lead generation.
An interesting other thing about FormVester, as opposed to the default Salesforce Web-to-Lead utility, is that it always checks if a lead already exists in Salesforce before creating/updating it (using a 6 rules based filter) so that it will never duplicate the lead.
Give it a try! FormVester for AppExchange

Hope it will help!

]]> By: benji jasik http://www.grokdotcom.com/2007/02/26/viagra-salesforce-and-the-power-of-consumers/comment-page-1/#comment-2564 benji jasik Tue, 27 Feb 2007 13:33:03 +0000 http://www.grokdotcom.com/2007/02/26/viagra-salesforce-and-the-power-of-consumers/#comment-2564 If you email your case, I'll take a look at it. We have some options now with validation rules to help with this until we have a formal product solution to this that should help alleviate some of your pain with this problem. If you email your case, I’ll take a look at it.

We have some options now with validation rules to help with this until we have a formal product solution to this that should help alleviate some of your pain with this problem.

]]>