Formulayt uses a top-down hierarchy of fields, form types, and gates.
Each level has a specific purpose, with configuration flowing down to the levels below it.
Fields
Fields define what data is collected and how each field behaves.
Fields can define:
Data type, such as text, phone number, or picklist
Validation, such as using regex to block personal email addresses
Pre-population
Language translation
Rules and conditional behavior
A field can be reused across multiple form types and gates.
Form types
Form types define which fields are used and how the form is structured.
A form type controls:
Which fields appear and their order
Whether fields are required or optional
Field behavior, such as single-page or multi-step forms
Progressive profiling
A form type can be used by multiple gates, allowing the same form structure to be reused across different gate experiences.
Gates
Gates define the individual experience and content presented to the user.
A gate controls things such as:
Content, define the gate type and experience such as, contact us, download, or redirect
Messaging
Meta-data
Gate-specific settings
Each gate can use a form type while having its own content and configuration.
How the hierarchy works
The relationship can be thought of as:
Field → Form type → Gate
For example, you might have a form type called Download Lead Form that is used by several download gates:
Form Type: Download Lead Form
↓
Gate: "Download the 2026 Report"
Gate: "Download the Case Study"
Gate: "Download the Industry Guide"
Each gate uses the same form type, so they share its field configuration and structure while retaining their own gate-specific content and settings.
Changes propagate down the hierarchy
Changes made at a higher level affect everything using that configuration:
Changes to a field affect every form type and gate using that field.
Changes to a form type affect every gate using that form type.
Changes to a gate affect that individual gate.
For example, if you update a field rule, the change will apply wherever that field is used, including all gates using those form types.
This allows shared configuration to be managed at the appropriate level rather than repeated across individual gates.
Hidden fields
Hidden fields are always added to every form type and gate. They can be used to capture or pass information without displaying the field to the user.
Their behaviou can also be affected by rules and field settings.
Why the hierarchy is useful
The hierarchy allows you to create reusable configurations while still maintaining individual gate experiences.
You can:
Create and configure your fields.
Build reusable form types from those fields.
Create individual gates using those form types.
Configure each gate's individual content, messaging, and settings.
This means shared configuration can be maintained centrally, while individual gates can still provide different experiences.
Additional platform considerations
Styles
Styles control how the gate looks.
Styles can be used to control elements such as layout, typography, spacing, and colors.
Integrations
Integrations control where submitted data goes and how Formulayt connects with external platforms.