What this operation supports in Intercom
Updates custom (non-standard) attributes on a conversation, distinct from its core fields like state or assignee.
Implementation details
Custom conversation attributes need to already be defined in the workspace's data attribute schema before they can be set here -- this doesn't create new attribute definitions on the fly.
Operational considerations
Validating a value's type against the attribute's defined type before sending it avoids a request failing due to a type mismatch, like sending text to a field defined as a number.
Use cases
4–7 concrete use cases: store user preferences, tracking codes, or custom status indicators in conversations; enrich with external data.