The six types
Without a declared type, every value is treated as text — and then a date of birth stored as
15/03/1990 gets no “after”/“before” in segments and doesn’t show up in the Date / Birthday trigger, which only offers Date or Date & time fields. That’s why the import runs automatic detection and asks for your review.
How the type is set
- On import: when creating a new field from a column, Cliqo detects the type from the values and shows review notes — ambiguous dates (is 12/05 May 12 or December 5?), postal codes that would lose their leading zero if turned into numbers, yes/no columns with empty cells.
- In forms: every extra field you create is born with the type you chose — in the pop-up, Text, Number, Date or Yes/no; in the form inside the email, under Save to › Create field, Text, Number or Date.
Rules that save you headaches
- Dates accept the Brazilian format (
15/03/1990) and the international one (1990-03-15), with real calendar validation — 31/02 doesn’t pass. - A value that doesn’t match the type becomes text, never discarded — you don’t lose data because of one nonconforming cell.
- On import, the field key is normalized (lowercase, spaces become
_; accents and symbols are removed): “Data de Nascimento” and “data_de_nascimento” are the same field. Prefer keys without accents — “aniversário” becomesaniversrio. The form inside the email’s Create field, on the other hand, swaps an accented letter for the plain one: “País” becomespais. - Different forms add up, they don’t overwrite: a pop-up that saves “size” doesn’t erase the “birthday” another form saved on the same contact.
Where the fields show up
- Segments — in the Customer data dimension, under “Your custom fields”. “Greater than”/“less than” (or “after”/“before”) only appear when the stored value is a number or a date in
yyyy-mm-ddformat. - Personalization — in the editor, Personalize › Your fields menu:
{{aniversario|em breve}}. - Contact profile — in the panel that opens when you click a contact, Custom fields section.