Your data model,
typed and validated.
Typed, validated contact attributes — with sensitive data marked as such.
Everything-is-a-string is a data-quality decision.
Custom fields are usually free text. A date arrives in four formats, a number arrives with a currency symbol, and a segment built on either quietly excludes half the people it should match. Worse, nothing distinguishes a job title from a health note.
Fields in SendNectar are declared with a data type, optional validation, and a sensitivity flag. Segments filter on real types, imports fail loudly instead of corrupting silently, and sensitive attributes are identifiable for retention and privacy work.
Custom fields, in detail.
Declared data types
Each field is text, number, boolean, date, or JSON — so comparisons, sorting, and date arithmetic behave the way you expect.
Validation rules
Attach validation to a field definition so bad values are rejected at the boundary rather than discovered in a broken segment.
Sensitivity flags
Mark a field as sensitive and it becomes visible to governance: retention policies, exports, and privacy requests can treat it differently.
Stable keys, editable labels
A machine key identifies the field for the API and imports while the human label can change without breaking anything downstream.
Brand-scoped definitions
Field definitions belong to a brand, so one client’s schema never leaks into another’s contact records.
Built into contacts
Custom fields sit alongside first name, last name, company, job title, country, locale, and timezone on the contact profile.
A field definition.
Six properties, and the reason each one exists.
- key
- Stable machine identifier used by the API, imports, and merge variables
- label
- Human name shown in the workspace — safe to rename
- data_type
- text · number · boolean · date · json
- is_sensitive
- Marks the attribute for governance, retention, and privacy handling
- validation
- Structured rules applied when a value is written
- Scope
- Defined per brand, alongside that brand’s contacts
Bring your provider.
Keep your brands distinct.
Start today.
Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.