Skip to main content
All CollectionsConfiguring OperateConfiguring Operate - Lead
Tailoring Web To Leads HTML for Multiple Websites
Tailoring Web To Leads HTML for Multiple Websites
S
Written by Sean Patterson
Updated over a week ago

A scenario for using Web To Leads is to re-use the same block of HTML, as generated by Operate, and tailor this for each website page from which Leads will be collected.

In this way, one can set different values for attributes of the Leads created, and then compare those Leads in reports afterwards.

The report may then highlight which website pages have been most useful in generating new Leads, have been most valuable in marketing and which have been most valuable in concluding sales.

To do this, one must decide which attribute(s) will be used to classify Leads. This may be one or more of the standard attributes for Leads provided by Operate. Alternatively, one may add Custom Fields to further describe and compare Leads generated. Refer to essensys Operate Custom Field Types and How to Set Them Up.

When the attributes have been chosen, include these in the Configuration of your Web To Leads Form. Refer to Web to Lead in essensys Operate for a description of this - including on how to hide these fields in your Form. It may be beneficial to hide the fields upon which a Lead will be classified so that users do not change the measurements that you are going to make.

Once the HTML has been generated and tailored for hidden fields, you must then decide which values to set for the classifying attributes for each website on which your page will be posted.

For example. you may decide to add a Custom Picklist Field to Lead to record the Web To Lead Source:

Ensure that this field is included in the Web To Leads Form:

Trying out the generated HTML shows the following dialog:

The generated HTML can be editted to hide the Picklist field. The HTML may need to be editted outside of Operate for this and opened in your browser. Add a <div hidden> tag and attribute to the beginning of line for the classifying attribute, and </div> afterwards.

<div hidden>
<label for="ud_WebToLeadSource">Web To Lead Source</label><select id="ud_WebToLeadSource" name="ud_WebToLeadSource" title="Existing System"><option value="-- Not Specified --">-- Not Specified --</option><option value="Google">Google</option><option value="FaceBook">FaceBook</option><option value="Yahoo">Yahoo</option><option value="Own Website">Own Website</option></select>
</div>

The resulting form will look like:

The whole generated HTML will need to be copied for each classification of Lead and, in each copy, the above statement must be edited so that the Picklist value is set for the way in which the resulting Leads are to be classified.

For instance, for a variant of the HTML that sets the Web To Lead Source to Own Website, insert a selected attribute on the option tab on the line for our classifying field:

<div hidden>
<label for="ud_WebToLeadSource">Web To Lead Source</label><select id="ud_WebToLeadSource" name="ud_WebToLeadSource" title="Existing System"><option value="-- Not Specified --">-- Not Specified --</option><option value="Google">Google</option><option value="FaceBook">FaceBook</option><option value="Yahoo">Yahoo</option><option value="Own Website"selected>Own Website</option></select>
</div>

Repeat this for the other values of the field in the other copies of the HTML.

Send each variant of the HTML to your webmaster to add to your different websites.

When reporting on the Leads generated, build your Operate Report Using Advanced Filters in essensys Operate Reports to include the Web To Lead Source field.

Did this answer your question?