Skip to content

Commit b7309cc

Browse files
authored
Merge pull request #4752 from segmentio/jfoskin-patch-3
Schema Unique Limits.md
2 parents ad55c3d + a6b791a commit b7309cc

File tree

1 file changed

+11
-7
lines changed

1 file changed

+11
-7
lines changed

src/connections/schema-unique-limits.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,24 +2,28 @@
22
title: Segment Schema Limits
33
---
44

5-
**How many unique events can be logged in my Segment Schema table?**
5+
#### How many unique events can be logged in my Segment Schema table?
66

77
While you can technically track unlimited events with Segment, only the first 4,000 events will be visible on the Schema page for a given Source. After you hit the 4,000 event limit, all future events will still be tracked and sent to your Destinations. They will not, however, be logged in the Segment Schema table.
88

9-
**How many unique event properties can be logged on the event details page?**
9+
#### How many unique event properties and traits can be logged on the event details page?
1010

11-
While you can track unlimited event properties with Segment, the event details page for a specific event can only show the first 300 properties. After you hit the 300 property limit, future properties are still tracked and sent to your Destinations, but they won't appear on the event details page. This limit includes nested properties in an event's `properties` object.
11+
While you can track unlimited event properties and traits with Segment, the Schema page has the following default limits:
1212

13-
These limits can also affect the traits and properties that you can see in the Computed Trait and Audience builder tools in Engage. If expected traits or properties do not appear in these tools, contact the [Segment Support team](https://segment.com/help/contact/){:target="blank"}.
13+
* Properties: The event details page for a specific event can only show the first 300 properties by default.
14+
* Traits: The Identify page can only show the first 300 traits by default.
15+
16+
After you hit the limit for both properties or traits, future properties and traits are still tracked and sent to your Destinations, but they won’t appear on the event details page. This limit includes nested properties in an event’s properties object.
1417

18+
These limits can also affect the traits and properties that you can see in the Computed Trait and Audience builder tools in Engage. If expected traits or properties do not appear in these tools, contact the [Segment Support team](https://segment.com/help/contact/){:target="blank"}.
1519

16-
**How can I clear the Schema if I have hit the limits?**
20+
#### How can I clear the Schema if I have hit the limits?
1721

1822
If you hit any of the limits or would like to clear out old events or properties, you can clear the Schema data from your Source Settings. In your Source, navigate to Settings, then Schema Configuration. Scroll down to the **Clear Schema History** setting.
1923

2024
![Clear your Schema data with Clear Schema History](images/schema_config_clear_schema.png)
2125

22-
23-
**How can I clear/archive properties in my source schema?**
26+
#### How can I clear/archive properties in my source schema?
2427

2528
At this time, you cannot clear or archive old event properties individually. An alternative for this is to archive the event itself, and then clear the archive. After you clear the archive, the event will re-populate in the schema with only the current properties.
29+

0 commit comments

Comments
 (0)