【前言】：早前我们介绍过如何创建并使用标准web-to-lead，随后又介绍了如何使用集成方式创建带附件的web-to-lead，那么这篇将以金融项目维护期内遇到的web-to-lead那些坑来盘点下你我他都关心的核心问题，以期为客户提供优质的解决方案。
1、【标准的web-to-lead有哪些限制？】：
每天使用web-to-lead捕获的线索个数为500条。
2、【超出限制后会遇到什么问题？】：
在维护金融项目的时候，客户经常报告线索丢失，那么可能你想问客户如何知道线索丢失的呢？其实它们使用web-to-lead提交表单时除了提交到sf外还提交了一份给Java的Database，这时它们通过差分可以判断是否丢失。那么这种问题一般都是捕获超出限制造成的。当超出限制时，管理员会收到一份邮件提示超限，丢失的数据会被记录在Email中。所以不要害怕数据丢失，只是手动入库比较烦！
3、【标准web-to-lead工作原理是啥？】：Web to lead form error message
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 whenever there's a service interruption, outage, or scheduled downtime. When the queue is empty, the leads appear in your org within seconds, but during outages or peak usage, the delivery may take longer--either way, the form doesn't communicate anything useful back to the calling website, can't display errors, or do anything directly related to your org's records. As far as your leads are concerned, the service is always available to capture their information.