In CamBuildr, Fields represent a convenient method for storing individual's data. For fundamental values, CamBuildr already provides an array of field options. Certain fields are designed to only accept values in specific formats to maintain data integrity. This becomes important when integrating your CamBuildr with other tools or when uploading data.
Value in Cambuildr | Valid Format | Field Name |
Valid Email Adresse | ||
Frist Name | Text | firstname |
Last Name | Text | lastname |
Gender | m for male | gender |
Phone Number | Text | phone |
Adress | Text | address |
City | Text | city |
ZIP | Number | zip |
County | Valid two characters ISO Code (AT, DE, ...) | country_alpha2 |
Birth Date | DD.MM.YYYY or YYYY-MM-DD | birthdate |
Action Context | Text | context |
Action Value | Number | value |
Action Tags | tag1, tag2, tag3, … | tags |
Action: Disclaimer Text | Text | disclaimer_text |
Action: Disclaimer Accepted | Boolean (true/false) | disclaimer_accepted |
In addition to the Core Values, you have the flexibility to create your own custom Fields. For these fields, you're able to establish personalized validation rules within the settings.
Which value identifies a person?
Every person record carries values that never change for the lifetime of that record. Use one of these whenever you need a stable reference to a person — for example when matching CamBuildr against another system:
Person ID — the number in the URL of the person’s detail page (
…/cambuildr/people/4711). Use it for API calls and for matching against your own systems.{{ var:identifier }} — the distinct identifier of the person, available as a placeholder in emails and links. It is generated once when the person is created, and it is what one-click unsubscribe links are built on.
{{ var:hash }} — the hash of the person, also generated once. It is the value behind the
recparameter in recruiter links, which attributes a sign-up to the person who recruited it.
The email address is not a permanent identifier. It is the value CamBuildr uses to recognise a returning person when a form is submitted, but it can be changed at any time on the person’s detail page — the person keeps the same Person ID, identifier and hash. The email field on a landing page form can also be optional, and submissions without an email address are not connected to a person record at all; they can only be seen and downloaded on the Form Entries tab. If you are building an integration or an export mapping, key it on the Person ID or {{ var:identifier }}, never on the email address.