Salesforce Wordpress plugin
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

=== WordPress-to-lead for Salesforce CRM === Contributors: stonydaddydonkeylabscom, nickciske Tags: crm, contact form, contactform, wordpress to lead, wordpresstolead,, salesforce, salesforce crm, contact form plugin, contact form builder, Wordpress CRM Requires at least: 2.8 Tested up to: 3.7 Stable tag: 2.1 License: GPLv2 Donate link:

WordPress-to-Lead for Salesforce CRM creates a solid integration between your WordPress install(s) and your account!

== Description ==

WordPress-to-Lead for Salesforce CRM creates a solid integration between your WordPress install(s) and your Salesforce CRM account! People can enter a contact form on your site, and the lead (or case) goes straight into Salesforce CRM: no more copy pasting lead info, no more missing leads: each and every one of them is in for you to follow up.

Check out the screencast


You can fully configure all the different settings for the form, and then use a shortcode to insert the form into your posts or pages, or you can use the widget that comes with the plugin and insert the form into your sidebar!

Please see this WordPress-to-Lead Demo video to get a full grasp of the power this plugin holds, and visit the Salesforce WordPress page. Check out this page to learn more about CRM for Small Business.

Previous contributors:

== Screenshots ==

  1. An example form generated with WordPress-to-Lead for Salesforce CRM (with optional CAPTCHA) -- both post and widget forms are shown in the TwentyEleven theme
  2. The backend administration for WordPress-to-Lead for Salesforce CRM
  3. The new form editor (multiple forms, hidden fields, add new fields, thanks URL, lead source per form)

== Installation ==

  1. Upload the plugin folder to the /wp-content/plugins/ directory or install via the Add New Plugin menu
  2. Activate the plugin through the 'Plugins' menu in WordPress
  3. Enter your Organisation ID on the WordPress-to-Lead plugin configuration page.

== Frequently Asked Questions ==

= How do I setup Web to Lead/Case for my SalesForce Account? =

Setting Up Web-to-Lead

Setting Up Web-to-Case

= How do I setup a Web to Case form? = Choose Web to Case in the Form Settings (bottom of the form editor page).

= Where do I find my Salesforce organisation ID? = To find your Organisation ID, do the following steps:

  1. Log in to your account
  2. Go to Setup » Company Profile » Company Information
  3. You'll find the Organisation ID in the lower right hand corner of your screen

= How do I use the checkbox field? = Like any other field. Note that it is a single checkbox, not a checkbox list.

Checkbox lists and radio buttons will be in a future update.

= How do I use the select (picklist) field? = Use it like any other field -- however you'll need to specify the options (and optional values) for each field using the options box (far right).

The value box for a select list is the default value (the one selected on a fresh form).

` //Use same data for display and value passed to SF one|two|three

//Use different data for display and value passed to SF, require user to select something (assuming field is required) Select One: | name1:value1 | name2:value2

//Use different data for display and value passed to SF name1:value1 | name2:value2 `

Note: Leading & trailing whitespace is trimmed when names and values are displayed, so feel free to use spaces to make things more readable.

= How do I use the HTML field? =

  1. Optionally enter a label (field will display full width if a label is not entered.
  2. Enter HTML code in the options box.

Note: You cannot use the HTML box to enter a custom field, as only "known" fields are submitted to salesforce and HTML fields are not submitted (just displayed). Be careful to avoid the <form> or </form> tags in an HTML field as they will likely break your form.

= How do I change the order of input fields? = Right now, the only way of ordering input fields is by changing the position numbers on the right hand side of the input fields table in the admin settings. Drag and drop re-ordering is on the roadmap.

= How do I apply my own styling to the form? = Instructions for disabling or overriding the CSS are included on the plugin settings screen (see Style Settings).

= Is it possible to make multiple forms with this plugin? = Yes, version 2.0 introduces this feature. Version 2.1 allows you to duplicate forms to reduce re-entering data.

= How do I change the Lead Source that shows up in Salesforce? = You can easily change this by going into the WordPress-to-Lead admin panel and, under form settings, changing the Lead Source for that form. Daddy Analytics uers can set this to blank to have it automatically filled.

= Can I change the submit button? = Of course you can! Go into the WordPress-to-Lead admin panel and, under Form Settings, change the text from the default "Submit" to whatever you'd like it to be!

= Will I lose data if I upgrade to 2.0? Do I need to change anything? = Nope! The plugin will migrate your existing data to the new format. Your existing form will become Form 1 and be output by the [salesforce] shortcode).

= How do I show my other forms? = Just use [salesforce form="X"] (X is the form number). Or select a form number in the widget.

= I put my campaign name in the Campaign_ID field but it's not working = The Campaign_ID field requires the Campaign ID -- the name will not work. To find the Campaign_ID, go your the campaign page and look in the URL bar for the ID:


In this example, 621U000000IJat is the Campaign_ID -- make sure you use the ID from the campaign you want the lead attached to and not the example ID shown here.

= Does the return/thanks URL have to be on my site? = No, as long as it's a valid URL it will work. However it should be an absolute URL regardless of where it is located. e.g. not just /thanks/

= Is there a limit to how many leads can be captured? = While the plugin has no limits, SalesForce does limit API calls per day:

The daily limit for Web-to-Lead requests is 500. If your organization exceeds its daily Web-to-Lead limit, the Default Lead Creator (specified in the Web-to-Lead setup page) receives an email containing the additional lead information.

See also: How many leads can we capture from our website?

== Other Notes ==

= Filters =


Change the API url the plugin posts data to

` add_filter( 'salesforce_w2l_api_url', 'my_w2l_api_url' );

function my_w2l_api_url( $url ){ return ''; } `


HTML of the form before it's returned to WordPress for display


Change from name (user confirmation)


Change from email (user confirmation)


Change from name (admin notification)


Change from email (admin notification)


Adding this code to your functions.php file will add 3 emails to the list. You can add as many as you want and each will get an admin notification email.

` add_filter('salesforce_w2l_cc_admin_email_list','salesforce_add_emails');

function salesforce_add_emails( $emails ){

//uncomment line below to remove site admin //unset($emails[0]);

$emails[]=''; $emails[]=''; $emails[]='';

return $emails; } `

== Changelog ==

= 2.1 =

  • Add drop down field type (thanks jbuchbinder)
  • Improve form HTML (thanks jbuchbinder)
  • Add from and reply to options for emails (thanks jbuchbinder)
  • Add delete checkbox to form editor (thanks jbuchbinder)
  • Add HTML field type (thanks jbuchbinder)
  • Add simple checkbox field (thanks jbuchbinder)
  • Add ability to duplicate forms (thanks jbuchbinder)
  • Add WPCF7 CSS integration option (thanks jbuchbinder)
  • Add wrapper divs with class names to visible fields
  • Remove Powered by SF for all forms
  • Make required field indicator consistent with message
  • Comments to lead option (thanks simonwheatley)
  • Global DaddyAnalytics settings added to make integration easier
  • Added filters to aid in extending the plugin
  • Hide fields with no label in admin and user email
  • Required fields now trim whitespace from the value before validation (e.g. a space or tab is no longer a valid value)
  • Fixed checkbox/label alignment
  • Readme improvements
  • Added daily limit info to FAQ
  • Removed previous contributors no longer involved in plugin development, added credit to readme
  • Refactored and cleaned up codebase
  • Added filters to allow code based overrides of select features (see Other Notes for details)
  • Added Web to Case option (per form setting)
  • Fixed first field being added having a duplicate position to last field
  • Select fields can have a default value set

= 2.0.3 =

  • Captcha image now works on subfolder installs (e.g. /wordpress/)
  • Removed captcha dependence on including wp-load.php

= 2.0.2 =

  • Small formatting fixes (checkbox spacing and submit button CSS)

= 2.0.1 =

  • Fixed issue with captcha URL being broken on some installs
  • Added several filters, including one to allow editing of the distribution list for new lead notifications and one to allow filtering of the form HTML before output
  • Fixed bug where captcha would wrap outside form on some themes
  • Fixed bug where forms other than id 1 did not show field labels in emails
  • Fixed bug causing unexpected output upon activation
  • Fixed bug that caused form to always be in 'sidebar' mode
  • Now supports more than 1 form per page
  • Forms now have a unique ID for use with CSS and jQuery: salesforce_w2l_lead_[ID] and salesforce_w2l_lead_[ID]_sidebar
  • Fixed a bunch of notices and warnings

= 2.0 =

  • Improved internationalization
  • Multiple forms can be created and inserted via shortcode or widget
  • Spam protection (with optional captcha)
  • Fixed "Cannot use object of type WP_Error as array" bug
  • Fixed bug that showed successful submissions as "Failed to connect to"
  • Hidden fields can now be used
  • Campaign_ID can now be set per form
  • Widget now hides description text upon submission
  • Admins can receive an email of submissions
  • Users can request a copy of their submission (if enabled)
  • Custom return/thanks URL can be defined per form
  • Country field added

= 1.0.5 =

  • Fix in backend security, preventing XSS hack in the backend.

= 1.0.4 =

  • CSS fix for when sidebar widget and contact form are on the same page.

= 1.0.3 =

  • Fix in email verification.

= 1.0.2 =

  • One more escape, plus a check to see whether the email address entered is valid.

= 1.0.1 =

  • Added escaping around several fields to prevent XSS vulnerabilities.

= 1.0 =

  • Initial release.

== Upgrade Notice ==

= 2.1 = This version includes most of the functionality in the "jbuchbinder" GitHub fork many users installed. Most users should not experience any issues upgrading. However, the "current date" field is not included in this release.

= 2.0 = This version fixes a bug that caused the plugin to appear broken, despite sending leads to