What data fields store

A data field stores a single JSON value per lead — typically an array of objects (e.g. a list of selected products) or a single object (e.g. calculation results). The slug always starts with df_ (e.g. df_quotation_lines, df_selected_products). The field is empty until something writes a JSON value to it via JavaScript or an HTTP request JSON map.

Writing to a data field

In a Hubhus form or webpage, write to the field using jQuery: jQuery('#df_slug').val(JSON.stringify(yourData)). The hidden input with id="df_slug" is injected by Hubhus — use this ID to set the value before form submission. Data is only saved when the form is submitted (or auto-saved). Always stringify the data before setting the value.

Reading data fields on webpages

On campaign webpages (display to lead), use the hh-data-fields.value component to render data field values: <hh-data-fields.value field="df_slug" />. For structured data (arrays), use hh-data-fields.array with a template for each item. In email/SMS templates, use {{df_slug}} or iterate via template loops.

JSON Schema validation

Define a JSON Schema on the field to validate the structure of stored data. Hubhus validates against the schema on save — invalid data is rejected. This prevents bad data from entering the system. Schema also enables autocomplete in the Hubhus playground. Important: never make a breaking schema change (e.g. removing or renaming keys) on a field with existing lead data — old values must remain valid, or perform a conscious migration.