However, we have demonstrated that the addition of the debug mode has made a difference in some leads being accepted or rejected.
Correlation is not causation. Unless you have submitted the exact same lead data with and without the debug flag and had one accepted and the other rejected, you cannot assume one caused the other.
Our marketing consultant ran several tests from his iPhone and from Chrome for Mac, of which none were captured in Salesforce. Upon submission of the WordPress-to-lead form, this individual was forwarded to our custom “Thank you for your inquiry” page on screen, indicating a successful submission.
The redirect happens when SalesForce responds to the API call with HTTP 200 OK. That does not mean the lead was accepted. Unfortunately that happens after the API call and is beyond the control of the plugin to detect. That’s what the debug flag, logs at SF, and emails are for: diagnosing if your custom validation rules are rejecting leads. Note that your rules are rejecting leads based on the data submitted — the plugin just passes the info along and does not control that (nor have any insight into your validation rules).
Having rules that reject leads and/or improperly configured forms are outside the scope of support I can provide for the plugin (that’d be premium/paid support) as it’s not a bug in the plugin.
The plugin also has an “email the admin” feature which would trigger regardless of whether the lead is accepted. If you had that enabled, you have a copy of every submission (rejected or not) in that inbox. If you did not enable that, they may be somewhere in the murky depths of SalesForce, but that would be a support question for them, not me.
Once I implemented the ‘debug’ field this afternoon, however, our marketing consultant’s test inquiries are all being received, indicating that the debug implementation has changed whether inquiries are being accepted or rejected by Salesforce.
Great to hear. But I cannot fathom how or why this would make any change in a lead being accepted/rejected.
Note that there are other variables in play: max leads per day, the availability of the SalesForce API endpoint, validation rules possibly changing, the data in the form submission not being the same between tests, etc. Unless you’ve eliminated all other variables, you cannot assume the debug flag fixed it.
If it did, great, but don’t ask me for an explanation — I don’t have one — you could try asking SalesForce. I can’t even test your assertion as I’d have to replicate your SalesForce lead settings to do so.
This is very problematic for us. We are a small company that has recently invested our largest email marketing spend ever in just the last two month, with every campaign pointing towards a WordPress-to-lead form. We are terrified about the number of potential clients that have fallen through the cracks due to an unknown problem with the wordpress-to-lead form. Any insight you could provide that may help us track down missed leads would be tremendously appreciated. Thank you for your prompt reply.
I’m sorry to hear that you’ve had issues with your web to lead form, but the plugin is just an intermediary between your site and SalesForce — unless you can point to a bug, (which I’m happy to fix) there’s not much else I can do in this forum. Free support is very limited — see the support guidelines sticky thread for more details.
I would be happy to assist with resolving any issues with your particular situation/configuration by engaging in a working (paid) relationship where we could troubleshoot things directly, if that interests you.
Please contact us directly if you’d like to pursue that.
