Skip to content

Commit 54eef28

Browse files
authored
Custom Traits edit
1 parent 5249045 commit 54eef28

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

src/unify/Traits/custom-traits.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,7 @@
22
title: Custom Traits
33

44
---
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.
76

87
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.
98

@@ -44,19 +43,18 @@ analytics.identify("97980cfea0067", {
4443
Custom traits are mutable and update to the latest value seen by the user's Identify events.
4544

4645
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-
4846

4947

5048
## Reserved custom traits
5149

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.
5351

5452
> warning ""
5553
> Only use reserved custom traits for their intended meaning.
5654
5755
Reserved custom traits Segment has standardized:
5856

59-
| **Trait** | **Type** | **Description** |
57+
| Trait | Type | Description |
6058
|---------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
6159
| `address` | Object | Street address of a user optionally containing: `city`, `country`, `postalCode`, `state`, or `street` |
6260
| `age` | Number | Age of a user |
@@ -77,6 +75,6 @@ Reserved custom traits Segment has standardized:
7775
| `website` | String | Website of a user |
7876

7977

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)).
8179

8280

0 commit comments

Comments
 (0)