Attributes
Define the attributes ARCY may store, import or export them as one file or accept what your coding agent proposes, and check that identify() values arrive.
Configure > Attributes lists the attributes ARCY may store. A key sent through
identify() that is not defined here is ignored: define first, then send.
Before you start
Defining, editing, importing, deleting and accepting takes an organization admin. A member sees the list, the status pills and Export. Status pills read the environment picked in the sidebar.
Setting it up
Press New attribute and fill in:
- Display name: what you see in the dashboard.
- Code name: the key your code sends. Permanent once created. Lowercase letters, numbers
and underscores, starting with a letter, no trailing underscore, up to 64 characters. A
prefix of
user_,organization_orplan_puts the attribute in that group. - Data type: Text, Number, Datetime, True/false, List, Object or Object list. A value of the wrong type is refused, never converted. Changeable later.
- Description: optional. For an Object, say what the document contains.
Then send the key from your Product (Quickstart); nothing shows before that.
Attributes file
Export downloads a JSON file of the attributes you defined, built-ins left out. Import adds every code name you do not have yet; one you already have is skipped untouched. A row that breaks a rule is refused with its reason; a file with a mistake is refused whole.
Hand it to your agent with the ARCY MCP opens the Declare attributes entry on ARCY MCP. Proposals show here greyed as Proposed by your agent: Accept declares all, Accept on a row declares one, Discard drops the rest.
Edit attribute changes the display name, description and, on your own attributes, the data type. Delete attribute archives it: stored values stay, and defining the same code name again brings it back. Attributes marked Set by ARCY refuse a sent value and cannot be deleted.
What it changes
Every defined attribute can be used in text visitors read: a widget text, a flow's public
name or step question, a Persona field. Type {{ or press Insert attribute.
Object and Object list are the exception. ARCY stores the document whole, so these two reach a Persona field only, filter only by whether they are set, and cannot split a report. To filter on one field inside it, send that field as its own attribute. Each value is limited to 10 KB, 5 levels of nesting, 200 array items and 50 object keys; one profile holds at most 64 KB of attributes. A value over a limit is refused; the rest of the payload is kept.
Each row carries a status pill for the selected environment:
| Pill | Meaning |
|---|---|
| Never seen | Nothing has arrived for this key. |
| Arriving but refused | Every value so far was refused. Hover for the reason. |
| Arriving, nothing stored | The key arrives with an empty value; null clears one. |
| Last seen | Values are arriving and stored. |
No sample values are stored.
When it goes wrong
Every row reads Never seen. Your Product is not sending attributes to this environment.
Check the token and the identify() call on Installation.
A row reads Arriving but refused. The pill's tooltip names the reason: wrong data type, over the size limit, a key ARCY computes itself, a failed built-in check, or a key that arrived before it was defined. Fix the value in your code or change the data type.
A refused key names the whole profile. The profile holds 64 KB of attributes. Nothing was removed; send less, or a summary instead of a document.