If you would like an overview of the main features of Demandbase forms and how they work, you can watch this video here: https://www.youtube.com/watch?v=zh2JhI-kNVw.
As explained in Understanding Visitor Identification, Demandbase returns firmographic information using three APIs: IP, Domain, and Company Autocomplete.
The Company Profile that Demandbase returns to the Form Connector, however, will choose only one of the API return values. The Company Profile value is determined by the Form Connector's API priority order.
The default API priority order is Domain API -> IP API -> Company Name API. This means that if all three APIs identify the visitor, the Demandbase Forms Connector will use the information returned by the Domain API. Likewise, if the IP API and Company Autocomplete APIs return data, but the Domain API does not, the Forms Connector will use the information returned by the IP API.
Below is a video that demonstrates how the default priority works.
Demo form using API priority: http://codepen.io/demandbase/full/dGVzmR/
Any data within the object
Demandbase.Connectors.WebForm.CompanyProfile is the data the Forms Connector has currently selected.
Demandbase.Connectors.WebForm.dataSource indicates the API source of the data (domain, ip, and company).
The Demandbase Autocomplete drop-down is the visual representation of the Company Name API. The drop-down allows the user to search for company names and select them from the drop-down. If a company was already identified by the email domain API or the IP address API, then those companies will show up at the top. If both API calls identified a company, the company identified by the email domain will appear above the company identified by the IP address.
The rest of the companies that appear in the autocomplete drop-down will be based on:
- The text that was typed into the search field.
- The IP address's geolocation (as identified by the public IP registry).
This means that the rest of the companies will be in a geographic location near the user. For instance, if a user located in Buffalo, New York types 'Apple' into the search field, Apple's headquarter office in Cupertino will not show up in the dropdown. Rather, you would likely see a number of Applebee's locations in Buffalo, New York.
Once your Demandbase Tag has finished executing an API call to our servers, it will attempt to append the data from the API response into your form fields. Every form page that is integrated with Demandbase MUST have the correct field configuration for the data to append properly. This means that the 'name' or 'id' attributes of your form fields must match the configuration specified in the design reference during the implementation process.
If you no longer have a copy of your form design reference, you may ask your Demandbase CSM for a copy. It is important to make sure your form template matches the configuration specified in the design reference because your Demandbase Tag will be configured to match the design reference. If your form page has misspelled or missing input fields, the data will not append properly to the correct fields.
For a further overview of these potential pain points, you may watch the following video for a demonstration: https://www.youtube.com/watch?v=zVtTG-tOcGQ
Hidden Form Fields
Hidden form fields allow you to attach non-visible data to a form before submission. Sending data underneath a form is useful for a variety of reasons, but it is primarily valued for being discreet. To enable this feature, you would simply need to add hidden input fields to your form and then inform your Demandbase representative of the data mapping that you would like applied to these fields. The data mapping would need to relate the 'name' or 'id' attribute of the HTML input field to the firmographic information that you are looking to receive from Demandbase.