A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
26

New Spring 17 Feature Both Web-to-Lead and Web-to-Case now have out of the box reCAPTCHA support. When creating the form you will now see "Enable spam filtering (recommended)" and "reCAPTCHA API Key Pair" fields: Here's the former solution, without using CAPTCHA: turn the "URL" field into a dedicated honeypot / gotcha on your Web-to-Lead form. Render it ...


8

Depending on how many leads you are getting daily, you may be able to plead your case to your rep and get the value increased. Shell Black has verified this is possible. If it is consistently much higher, you would be better off creating a custom solution to generate your leads via the API.


8

There's not much you can do to protect your web to lead forms without additional code. In fact, this is why there are solutions on the matter (see Help & Training). The problem stems from the fact that salesforce.com isn't in control of the form, and has no way to submit any errors back to the original form. This is a necessary trade-off in order to ...


8

You can do this from JavaScript using Web-to-Lead (as suggested in a comment by greenstork): function webToLead(firstName, lastName, email) { var form = document.createElement("form"); form.method = "POST"; form.action = "https://webto.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8"; // Your org ID var elementOID = document....


7

Both Web to Lead and Web to Case generate basic HTML to pass onto your website developer that would pass queries straight into Salesforce. Web to Lead is normally Sale driven, e.g. someone interested in a product or receiving a call back from a Sales person. Web to Case is normally Customer Service driven, e.g. My product doesn't work help me please. Both ...


5

Config solutions You could define a workflow rule? Firing condition would be on lead creation (when certain criteria are met like stuff defined here + any fields you decide to have in the form) Action would be an outbound message flying back to your website. If not an outbound message - maybe an email alert going to dedicated mailbox that's readable by ...


5

The Web-to-Lead form is actually not directly connected to your org. Instead, the Web-to-Lead form submits the data into a queue via the POST'ed form, and it is asynchronously sent to your org at a later point in time. Using this design, salesforce.com can continue to capture leads for your site even during maintenance, so that you don't miss any leads ...


4

Make a small site from site.com in your own salesforce. Go to setup->app setup->develop->sites You will get a URL from here that will go into the facebook app that you create. The app will diret the person to this site(much like it happens in IBIBO etc) and his/her information is sent to that site. The site's visualForcePage captures this information and ...


4

After much searching, I found the answer. If the return URL is on a different domain to the current domain, it will ask the user to click first: The redirect page is being displayed due to some security measures that Salesforce has in place with our web to lead infrastructure. In cases when a GET method is utilized and the referring URL (as ...


4

The Web-to-Lead function allows you to set up a form post to Salesforce to create new Lead records - documentation, video.


4

As for apps that you can use to collect the leads, I'm a fan of Form Assembly. Easy to setup, maintain and does some snazzy lookup logic so you can avoid dupes.


4

You might be interested in sfdc-web2anything, which can directly create contacts. If that's not your thing, a trigger on lead could definitely convert leads on creation, if you'd like. Take a look at the LeadConvert object and the Database.convertLead function call. Here's a simple trigger that reaches this objective: trigger web2LeadConvert on Lead (after ...


4

Yes, any time there's a potential for a sale, it is originally a Lead. Once the Lead is Qualified, it becomes an Opportunity (a potential sale). Leads merge in to existing Account and Contact records upon conversion (based on Account Name and Contact Name). This is the intended flow, and is probably the easiest way to manage your sales cycle.


4

Web-to-Lead form is only part of the HTML that is generated in Salesforce specific to what needs to be captured on the form, based on the selections that you may have made. You then provide this generated HTML to the webmaster which is then incorporated on any external website. As long as the external website's webmaster/developer can configure the HTML to ...


3

As others have said, the first and easiest thing to do is file a case / contact your AE and request this limit be lifted. They will hopefully do this for you; raising it to 1000 isn't normally a big deal for Salesforce. If they don't do this, then you'll need to get the Leads into SF via the API (presuming you have Professional with the API add on, or ...


3

Curling Web-to-Lead has bitten me before via both funky character encodings and validation rules. Can you share the data you are testing with and I'll try? Edit: I tried submitting to your Web-to-Lead code, complete with a unicode smiley face, substituting in my own oid and sans the CAPTCHA. The lead went in OK. To eliminate one more variable from the ...


3

You are hitting the browser's same origin security policy. This means that your JavaScript can only make AJAX calls back to the same origin of the containing page - in this case http://domainname.ext. You are trying to make an AJAX call to Salesforce and that gets blocked. CORS (cross origin resource sharing) relaxes this restriction by letting servers ...


3

If you use https, it's encrypted. Otherwise, it's not. The security is entirely up to you.


3

I highly recommend you save yourself a lot of trouble and don't try to "reinvent the wheel". Instead, go and download the free jQuery Validation Plugin. Here are some links to a couple of related posts you may find helpful with some tips on how to implement it: Wes Nolte's Blog The Silver Lining and on Stack Overflow: https://stackoverflow.com/questions/...


3

That's not what crmprogdev was saying, he was saying you don't have access to ld.id or the oldMap in the before insert context. We don't know what GetLeadBranches is doing but if you need the IDs you need to change it to after insert.. By putting if(ld.ID != null){} you're completely negating the before insert part of this trigger, but considering your ...


3

I've solved related issues with a strategy like this: In before insert trigger; set a custom field Has_Been_Round_Robin_Assigned__c to FALSE In your lead assignment rules, the first rule checks the aforementioned custom field for false and assigns the Lead to a Queue called 'Pending Assignment' . Be sure to uncheck the email box on the right side of this ...


2

No, unfortunately - this will be tricky on two counts: Salesforce do not serve Cross Origin Resource Sharing headers and browsers will abort the request with XMLHttpRequest ... is not allowed by Access-Control-Allow-Origin. The visitor never knows if WebToLead fails. Say a validation rule prevents the upsert, you will receive a failure email but your ...


2

I think you would need a trigger to handle this, since Workflow cannot create an Activity. Here's a rough outline of the steps for an After Insert trigger: Lead is created Check if Lead Source is Web2Lead. If not, exit. Create new Activity Assign Activity to the new Lead Copy Lead.Description into Activity Insert Activity Later on, this Activity would ...


2

In drupal, when creating the webform, for some reason, the Name and ID of the Campaign_ID weren't the same, and it looks that Salesforce does NOT recognize "campaign_id" as the name. The problem is that it seems that this field is Case Sensitive. Changing the name and id from: campaign_id to --> Campaign_ID solved the problem.


2

If your dropdown values have the OwnerID values (or something you could find via SOQL) you could set them via trigger. Have the dropdown map to a custom field on the Lead Have the Lead set to a default owner Have the trigger inspect the custom field and update the OwnerID appropriately


2

On my side I am also changing the form destination via JS. This would be equally effective against robots that do not run JS as some of the other solutions proposed. <form action="http://www.example.com/sorry" ...> <script> jQuery("#investor-web-to-lead-form").attr("action","https://www.salesforce.com/servlet/servlet.WebToLead?encoding=UTF-8"); &...


2

You can have attachments added to Leads (you can enable that on the setup of the Leads page layout object). As for adding attachments from the web form itself - I am not aware of a standard setting, but a short google search, brought 2 options http://boards.developerforce.com/t5/General-Development/web-to-lead-form-with-attachment/td-p/336137 The second ...


2

From the comments on your question it appears you are looking at the logs from a Sites user. I assume you are hosting the Web2Lead form in Sites somewhere. I ran the following test and it seemed to fire the after insert Trigger as expected. As such, I'd suggest checking the log that gets created for the /servlet/servlet.WebToLead operation to see if there ...


2

so there are a couple of tricks you can do. Background: you can include custom fields in your web to lead, and use css/html to hide them and or pre populate the data. so, with that in mind, I like to do the following. Put the form on the page, with an unpopulated, hidden field called "Web2lead__c" or some such. Strip out the OrgID from the form. ...


2

Duplicate value error messages are typically related to unique fields or custom errors by apex or app exchange de-duplication packages. Based on your errormessage it is likely that the Contract_Number__c field is unique, and no 2 lead records can have the same value for that field. In testing with CURL, you may have tried to insert the same lead twice. To ...


Only top voted, non community-wiki answers of a minimum length are eligible