Attributes
Define the attributes ARCY may store, choose which values an AI model may read, accept your agent's proposals, and check that identify() values arrive.
Settings > Install > Attributes lists the attributes ARCY may store. A key sent through
identify() that is not defined here is ignored: define first, then send
(Quickstart).
Before you start
Changes take an organization admin; a member sees the list and the Status column, which reads the environment in the address.
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
user_,organization_orplan_prefix puts it in that group. - Data type: Text, Number, Datetime, True/false, List, Object or Object list, changeable later. A value of the wrong type is refused, never converted.
- Description: optional.
- AI can read this value: on by default. Off, no AI model receives the value and the row wears AI off; text a visitor reads keeps it.
Either name is refused, on create or rename, when it names a card, a card number, a credit
card, CVV, CVC, a security code, a PIN, a password, a passcode or an IBAN, in English or
Turkish: ARCY never stores payment or credential data. pinned_at is fine.
Your agent's proposals
Hand it to your agent opens Declare attributes on ARCY MCP. Its proposals show greyed under Proposed by your agent: Accept all, Reject all, or Accept and Reject per row. Ask your developer, beside it, gives you a link to send instead (ARCY MCP).
Edit attribute changes the display name, description, the switch and, on your own
attributes, the data type. The five marked Set by ARCY carry no switch, refuse a sent
value and cannot be deleted; the fifth, user_last_intent, is written after each day closes
(Conversations). Delete attribute archives it: stored values stay, and
defining the code name again brings it back.
What it changes
Every defined attribute can be referenced in visitor-facing text and in a Persona field,
with {{ or Insert attribute.
Object and Object list are stored whole: they reach a Persona field only, filter only by whether they are set and cannot split a report. Each is limited to 10 KB, 5 levels of nesting, 200 array items and 50 object keys; one profile holds 64 KB of attributes. A value over a limit is refused and the rest of the payload kept.
Payment and credential data is never stored. A value that looks like a card number, an IBAN or an API key is refused on every path in and never logged.
The Status column counts identify() and flow saves alike.
| Status | Meaning |
|---|---|
| Never seen | Nothing has arrived for this key. |
| Arriving but refused | Every value so far was refused. |
| 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. This environment receives no attributes: check the Publishable key and
the identify() call on Installation.
A row reads Arriving but refused. The tooltip names the reason; fix the value in your code or change the data type.
A refused key names the whole profile. It is at 64 KB and nothing was removed. Send less, or a summary.
See also
Integrations
Find any tool ARCY works with, hear the events your page already sends, and connect the helpdesk or email address a handover lands in.
Events
Declare the events your product reports with track(), mark those that count as value, see how many arrived and how many ARCY reported, and catch an undeclared name.