The Form block lets you collect supporter data directly on a landing page. Submissions create or update a person in your database and can automatically assign tags and custom-field values.
Adding a form
Drag the Form block from the Content sidebar onto your page.
Select the block and click Edit to open the form editor.
Add and configure your fields, steps, consent and success behaviour, then save.
Field types
Text – single-line input (also used for email, phone, ZIP and name fields).
Textarea – multi-line input.
Date / Birthdate – date picker.
Dropdown – single-select list (e.g. country, or your own options).
Radio buttons – pick one option.
Multi-select – pick several options (shown as a checkbox list).
Checkbox – a single opt-in, which can be linked to a tag.
File upload – let supporters attach a file. You can set the maximum file size (up to 50 MB), optionally restrict the allowed file types, and flag the upload as sensitive data.
Hidden field – capture a value without showing it to the supporter (e.g. a campaign or affiliate code passed in the URL).
Text part – a static text block placed between fields, for instructions, section intros or legal text. It collects no data and supports formatting such as bold and links.
Field options
Every field can be marked optional (fields are required by default) – including the email field, so supporters can submit without an email address.
Edit each field's label, description, placeholder and – for dropdown, radio and multi-select – the list of options.
Fields can be mapped to core person fields, custom fields or tags. Matching data is saved to the person record on submit.
Multi-step forms
Split a longer form across up to 3 steps. Assign each field (and text part) to a step; supporters move through the form with a Next button and submit on the final step.
Recognising recipients of a CamBuildr email
When you link to the page from a CamBuildr campaign email or automated email, add the prefill link placeholder to the link:
https://your-page.org/sign?{{ var:prefill_link }}Instead of putting the recipient's address in the URL, this passes a signed token that only CamBuildr pages can read. The form then greets the visitor by name and shows their address masked — j***@example.com — with a That's not me option beside it. The email input stays hidden while the card is shown, and the submission is matched to the right person on our servers.
If the visitor chooses That's not me, the fields reappear empty and whatever they type is used instead. An address typed into the form always wins over the recognised one.
The token fills in the first and last name only. To pre-fill anything else, combine it with the named parameters below, for example ?{{ var:prefill_link }}&zip={{ var:zip }}.
Pre-filling from the URL
Field values can be pre-filled through URL parameters, for example ?zip=1010. This is how you fill a form from a link written anywhere else — your own website, another tool, or a link that has to carry more than the name.
The parameter name is the same name you use as a variable in emails: firstname, lastname, email, phone, gender, title_pre, title_post, birthdate, zip, city, street, country_code – and for a custom field, its slug, e.g. ?membernumber=12345. Each field in the form editor shows the parameter name to use for it.
Because the names match, a link in a CamBuildr email can pass the variables straight through and every recipient gets their own data pre-filled:
?firstname={{ var:firstname }}&zip={{ var:zip }}Putting an email address in the link is no longer the recommended way. ?email={{ var:email }} keeps working and existing emails need no changes, but the editor now warns you when an email puts person data inside a link URL — that value is personal data and can be read by the target site, its analytics and its server logs. Since a form block always sits on a CamBuildr page, use the prefill link above for these links.
The older parameter names – name, surname, zip_code, country, country_alpha2, and custom fields addressed by their numeric field ID – keep working, so existing links do not need updating. If a link carries both names for the same field, the older one wins.
Hidden fields capture URL parameters silently, which is useful for attribution and tracking codes.
Consent & data protection
Enable a disclaimer checkbox with your own text, or use multi-consent to capture separate, per-tag consents (each can be mandatory or optional).
When opt-in is required, supporters receive a confirmation email (double opt-in) before the record is finalised.
Spam protection (reCAPTCHA) is applied automatically when it is enabled in your settings.
After submission
Choose what happens on success: show a thank-you message, or redirect to a URL.
Optionally forward the submitted values to the redirect URL as parameters. Be deliberate about this one: the values then travel in the URL of the target page, where its analytics and server logs can read them. Leave it off unless the target really needs the data, and never use it for sensitive fields.
Show social sharing buttons on the success screen.
Styling
Match the form to your page with primary and secondary colours, a transparent or coloured background, rounded edges and a custom button label.