Store customer custom fields
Store selected server-side context on a Contact record.
The supported field
Contacts accept customFields as a freeform JSON object through PATCH /api/v1/contacts/:id. This is not a typed, workspace-wide attribute registry. Read the current contact before changing its fields; the update replaces the supplied object rather than defining an automatic per-key merge.
Keep writes server-side
Use the authentication required by the Contacts API from a trusted backend. The widget does not expose identify or update methods for arbitrary visitor attributes. Never embed an agent token in a public website.
Do not treat fields as authorization
A stored customer attribute is context, not proof of the visitor’s identity or permission to see an order. There is no general Settings > AI > Attribute access privacy toggle. Store only the information this workspace is authorized to process.
Check supported consumers
Do not assume every field automatically appears in a pinned profile layout, becomes searchable, drives routing or reaches the AI. Use the fields and rule conditions documented for the specific consuming feature.