First make sure that the form is actually part of the page and not hosted in an iframe. If the form is hosted in an iframe then the only way to enrich the profile based on the visitor's input is to have the BlueConic script placed in the iframe as well. This article explains why.
Another important aspect to consider is how the form is actually handled by the site. Traditionally, forms are submitted using the HTML DOM form submit, which is e.g. triggered by clicking a 'submit button'. A lot of websites however choose to prevent the default submit event and handle the form programmatically e.g. by triggering an AJAX request to send the input data to the server and not have the page reloaded completely. The rules of the Form Listener need to configured to fit the way the form is handled by the site.
Finally there is the way the form is (initially) loaded into the page. Traditionally the form is just part of the HTML body of the page. Some sites however, especially sites which embrace the Single Page Interface model, choose to load the form dynamically, after the HTML body has loaded.
If you are not sure how the site is actually handling or loading the form, simply try the different rule variations to find the variation the works for you.
The different listen rule variations are:
- Write data to a profile property when the surrounding form is submitted
This corresponds to the traditional way of submitting and loading forms.
- Write data to a profile property when a custom form is submitted
This also corresponds to the traditional way of submitting forms but lets you manually choose the form. Whenever the form is dynamically inserted into the page this should be the first variation to try.
- Write data to a profile property when a custom defined form is submitted
This variation should be used when the fields are not located inside the form that is programmatically submitted by the site. Either manually choose the position on the website or use the visual picker to select the form.
- Write data to a profile property when a custom position is clicked
This variation should be used when the form submit is handled programmatically by the site. You manually choose the position on the website, which after it is clicked should trigger a profile update.
- Write data to a profile property when the location hash changes
This variation should be used when the form submit is handled programmatically by the site and the URL in the browser is appended with a specific hash (e.g. "#success") as a result. Enter the hash name without the "#" so BlueConic can determine a successful submit has taken place.