A Form Structure defines which fields are collected when a lead is created. It acts as the blueprint for forms, API payloads, and partner integrations.
- Ensures all leads follow a consistent format.
- Defines which fields are required and optional.
- Used in all forms generated by PalDock and in incoming API traffic.
- Typical use cases: when each offer or product has its own specific field requirements.
One structure, three ways in
A lead can reach PalDock through a hosted form, an embeddable form on the affiliate’s site, or the API. All three are served by the same structure.
A field you add appears in all of them at once, including in the API documentation your partners read. So does a field you make required, which is worth remembering when partners are already sending leads.
How it connects to offers and integrations
- A structure is attached to an offer, and an offer can have more than one. Two landing pages that differ by a single field can share one offer instead of being duplicated. See Multiple Structures for Offers and Integrations.
- An integration is built on exactly one structure. Its fields are what you map into the advertiser’s request, so an integration can only send what its structure collects.
If an advertiser needs a value that is not in the structure, add the field there first. Collecting it, hiding it, or filling it with Modify are then all options.
Deciding how many you need
One structure per offer is the normal case. Add another when the fields genuinely differ, not when only the wording differs.
- The same fields, different labels is a job for Translations or for editing the label, not a second structure.
- The same fields, different rules or scenarios does need a second structure, because validation and Modify are set per field.
- Different fields obviously needs a second structure.
Every extra structure is another place to maintain when an advertiser changes what they want, so the cost is real but it is paid later.
👉 For details about field types, validation, Modify, and translations, see the other pages in this section.
