Target group: landing page template builders
In Ternair Campaign various functionalities can be defined via the HTML-code of a landing page. These functionalities guide the user in filling out the data capture form that is used in a landing page.
Use function keys Ctrl-F to search the HTML-code.
Default data capture fields
The data collected via data capture forms is divided into default values and other values.
All default values that are collected are stored in the entity ‘Data capture’ and all other values are stored in the entity ‘Data capture properties’ under the source ‘Campaign Information (Ternair)’.
The following default profile data are stored in the entity ‘Data capture’:
All values not corresponding to one of the default values mentioned above are stored in the entity ‘Data capture properties’.
The following meta data is added to data capture records in Ternair Campaign:
The following form attributes can be used in a datacapture form.
Attribute to recognize the form. Can be placed on a form or div element.
Errors are shown under the text box by default. This attribute groups all errors above the form.
Validation labels are nog ignored using this attribute (when summary is active)
Save button. This attributes can only be used when <form> tag is not used. When the <form> tag is used the default submit can be used: <button type=”submit”>
This attribute replaces the “data-capture-form” content after it has been submitted successfully. This element is placed both on the form as well as on the success-content. On the form level this attribute has a value matching the id of the success element.
Attribute with value. Can only be used when using a <form> tag. This indicates a second landing page which is shown after successfully submitting the form.
|Form including success page
After saving data show a second landing page
The following input elements can be used in a data capture form.
This values is saved in the database.
Fields is validated / required.
Numerical field (integer). Only numeric values can be entered.
This field contains an email address. Value must contain an @.
Attribute with value. Values is shown in case input is invalid. Use in combination with data-capture-email.
Attribute with value. Value is shown in case field is empty. This attribute is placed once on list elements (Radio button, check box, drop-down)
Attribute with value. Values are used for prefilling text boxes.
|Text box lastname||
|Text box email||
|Text box shoe size||
Radio buttons, check boxes and drop-down elements
Attribute with value. When value matches data-capture-value the value is selected.
|Radio button (:radio)
| Drop-down (select)
Dividing the form in steps
Container attribute of the step (part of the form). Must contain a value. First step is 1, unlimited number of steps allowed.
|Text box achternaam
Button attribute to go to the next step. Next step is determined automatically (ascending).
Button attribute to go the next step. Next step is determined automatically (descending).
Button attribute with value. Button to go to jump to specified step.
Button attribute to ignore validation. For example return button.
By using default auto completion attributes users are helped when filling out the form. When an auto complete attribute is recognized by a browser these fields are filled out automatically.
N.B. auto completion is not (yet) supported by all browsers.
The check box ‘Data capture’ needs to be checked in the landing page template settings. This will generate the scripting that is required for the data capture functionalities in the landing page.
Furthermore multiple forms can be placed in one landing page. Use “data-capture-success” when saving the form(s) using different values.
jQuery does not have to be loaded in a landing page, this will be done by default.
Scripts should be placed on top of the page in order to prevent conflicts.