Skip to content

Add information about Event Property Limits on Computed Traits #4008

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 9, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/engage/audiences/computed-traits.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ Engage currently supports the following types of computed traits:
- [Accessing your Computed Traits using the Profiles API](#accessing-your-computed-traits-using-the-profiles-api)
- [Downloading your Computed Trait as a CSV file](#downloading-your-computed-trait-as-a-csv-file)


> warning "Event Properties per Computed Trait limit"
> Segment limits the number of Event Properties on each Computed trait to 10,000. If your Computed Trait exceeds this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values.

### Event Counter

An Event Counter trait stores a count of an **event** over a period of time. For example, you can create a trait called `number_logins_90_days` based on a `User Logged In` event. You can also use event properties to only specific types of events.
Expand Down
2 changes: 1 addition & 1 deletion src/engage/product-limits.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ To learn more about custom limits and upgrades, contact your dedicated Customer
| Events Lookback History | 3 years | The period of time for which Segment stores audience and computed traits computation events. | |
| Real-time to batch destination sync frequency | 2-3 hours | The frequency with which Segment syncs real-time audiences to batch destinations. | |
| Event History | `1970-01-01` | Events with a timestamp less than `1970-01-01` aren't always ingested, which could impact audience backfills with event timestamps prior to this date. |

| Event Properties (Computed Traits) | 10,000 | For Computed Traits that exceed this limit, Segment will not persist any new Event Properties and will drop new trait keys and corresponding values. |
## SQL Traits

| name | limit | Details |
Expand Down