You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/unify/Traits/custom-traits.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,7 @@
2
2
title: Custom Traits
3
3
4
4
---
5
-
6
-
Custom traits are user or account traits collected from the Identify calls you send to Segment. For example, these could be demographics like `age` or `gender`, account-specific like `plan`, or even things like whether a user has seen a particular A/B test variation. From your sources, send custom traits as pieces of information that you know about a user in an Identify call.
5
+
Custom traits are user or account traits collected from the [Identify](/docs/connections/spec/identify/) calls you send to Segment. For example, these could be demographics like `age` or `gender`, account-specific like `plan`, or even things like whether a user has seen a particular A/B test variation. From your sources, send custom traits as pieces of information that you know about a user in an Identify call.
7
6
8
7
As opposed to [computed traits](/docs/unify/traits/computed-traits/) which are computed from your source data, or [SQL Traits](/docs/unify/traits/sql-traits/) which are computed from warehouse data, custom traits are created from source events you pass into Segment and have no trait limits.
Custom traits are mutable and update to the latest value seen by the user's Identify events.
45
44
46
45
When an audience that previously generated Identify events is deleted, the data for the audience key is still attached to profiles that entered the audience and becomes visible in Segment as a custom trait.
47
-
48
46
49
47
50
48
## Reserved custom traits
51
49
52
-
Segment has reserved some custom traits that have semantic meanings for users, and will handle them in special ways. For example, Segment always expects `email` to be a string of the user's email address. Segment sends this on to destinations like _Mailchimp_ that require an email address for their tracking.
50
+
Segment has reserved some custom traits that have semantic meanings for users and handles them in special ways. For example, Segment always expects `email` to be a string of the user's email address. Segment sends this on to destinations, like Mailchimp, that require an email address for their tracking.
53
51
54
52
> warning ""
55
53
> Only use reserved custom traits for their intended meaning.
|`address`| Object | Street address of a user optionally containing: `city`, `country`, `postalCode`, `state`, or `street`|
62
60
|`age`| Number | Age of a user |
@@ -77,6 +75,6 @@ Reserved custom traits Segment has standardized:
77
75
|`website`| String | Website of a user |
78
76
79
77
80
-
To learn more about using an Identify call to tie custom traits to profiles, [visit Segment's Identify documentation](/docs/connections/spec/identify/).
78
+
To learn more about using an Identify call to tie custom traits to profiles, [visit Segment's Identify documentation](/docs/connections/spec/identify/#custom-traits)).
0 commit comments