| SharpSpring allows you to create dynamic forms that can be placed on your site wherever you choose. Occasionally, you may need to pass hidden field values into a custom field within SharpSpring. This article details how to pass these values to a custom field from a SharpSpring form.
|
Available with: | ||||
| Marketing Automation | ✓ | ||||
| CRM Ultimate | ✓ | ||||
| CRM PRO | ✓ | ||||
| CRM Free | ✓ | ||||
| Toolbar: | |||||
  |
|||||
| Users: | |||||
| Administrators | ✓ | ||||
| Company Managers | ✓ | ||||
| Marketing Managers | ✓ | ||||
| Sales Managers | |||||
| Salespersons | |||||
| Jr. Salespersons | |||||
Hidden Field Differences
| When you pass hidden field values, the value can vary based on what page of your site the form is submitted on. For example, if you use the same Contact Us form across multiple pages of your site, you can pass a different value across each page. | ||
|
Alternatively, if you create a hidden field in the Form Builder, the hidden value will be the same regardless of where an individual fills out the form. If you have a script that grabs the browser URL location and places it in a hidden field, you can have the location logged in the contact record. |
Note: SharpSpring offers Professional Services to assist with custom coding.
|
|
| This value would end up being unique, per placement of the SharpSpring form script. This would be impossible to do using the hidden field option in the Form Builder. The hidden field option in the Form Builder is still valuable, but passing hidden fields provides a bit more flexibility for type of information you can fetch. | ||
Obtaining Hidden Field Information
Form embed codes can be modified. For system fields, you can pass your own values into these fields. For custom fields, instead of using the field name, you will need to use the field's system ID. To obtain a fieldID value, do the following:
|
|
User Menu > Settings in SharpSpring's top toolbar.
Options > Copy fieldID to Clipboard to the right of the custom field.
Adding Hidden Fields to Form Embed Codes
|
Once the fieldID value has been obtained, it will need to be inserted into a form. In order to do so, the form's embed code will need to be modified. To edit a form embed code to add a hidden field, do the following:
As an example, if the custom field is stored in a JavaScript variable called
This procedure assumes that you are editing the embed code for the first time. If you cannot find |
|
|
|
Note: The value replacing
Anon can be a static value in quotes, a JavaScript variable, or JavaScript code that returns a value. These values are collected when the form is displayed, and any changes to them after the form is rendered will not be recognized. |
||
|
Important: If there are two slashes (//) before
ss_form.hidden, delete them. They will prevent the hidden field from passing through otherwise. |
||
|
Important: Fields being passed as hidden fields using this method should not be added to the form in the form editor. Passing these fields as hidden fields creates blank space at the bottom of the form.
|
||
Frequently Asked Questions
Q: How do I pass multiple values?
A: Separate the values with commas.
{'field_96971777': prodName, 'field_01010101': anotherValue}
Q: How do I pass a static string using the hidden field?
A: Include the string within single quotation marks.
'12345'
Q: How do I pass a referrer field?
A: You will need to use ref_ instead of field_.
ss_form.hidden = {'ref_96971777': prodName};