From 0a655f5fe229d5235e7b197425514462590132b2 Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Wed, 17 May 2023 11:01:06 -0400 Subject: [PATCH 1/5] Schema Unique Limits.md --- src/connections/schema-unique-limits.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/connections/schema-unique-limits.md b/src/connections/schema-unique-limits.md index d6de057dac..3fa139989c 100644 --- a/src/connections/schema-unique-limits.md +++ b/src/connections/schema-unique-limits.md @@ -23,3 +23,8 @@ If you hit any of the limits or would like to clear out old events or properties **How can I clear/archive properties in my source schema?** 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. + +**What are the default limits per source schema?** +- Event limit default 4000 +- Properties limit default 300 +- Traits limit default 300 From 5ac80d377dc1987a654db39081ed11b98ebd3fe8 Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Tue, 6 Jun 2023 11:39:10 -0400 Subject: [PATCH 2/5] Update schema-unique-limits.md --- src/connections/schema-unique-limits.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/src/connections/schema-unique-limits.md b/src/connections/schema-unique-limits.md index 3fa139989c..72c750e36f 100644 --- a/src/connections/schema-unique-limits.md +++ b/src/connections/schema-unique-limits.md @@ -8,10 +8,15 @@ While you can technically track unlimited events with Segment, only the first 4, **How many unique event properties can be logged on the event details page?** -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. +While you can track unlimited event properties and traits with Segment, the Schema page will have the following default limits: -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"}. +* Properties: the event details page for a specific event can only show the first 300 properties by default. + +* Traits: the Identify page can only show the first 300 traits by default. +After you hit the limit for both properties or traits, future properties/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. + +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"}. **How can I clear the Schema if I have hit the limits?** From 14cb38fd5a15c4d0b2f2e7c38bf0c4d3e9de9552 Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Tue, 6 Jun 2023 11:42:26 -0400 Subject: [PATCH 3/5] Update schema-unique-limits.md --- src/connections/schema-unique-limits.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/connections/schema-unique-limits.md b/src/connections/schema-unique-limits.md index 72c750e36f..7b14b6a125 100644 --- a/src/connections/schema-unique-limits.md +++ b/src/connections/schema-unique-limits.md @@ -29,7 +29,3 @@ If you hit any of the limits or would like to clear out old events or properties 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. -**What are the default limits per source schema?** -- Event limit default 4000 -- Properties limit default 300 -- Traits limit default 300 From 37e3d3af319d6a8da68aca28f926cc3619bc142b Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Thu, 8 Jun 2023 09:49:51 -0700 Subject: [PATCH 4/5] Apply suggestions from code review --- src/connections/schema-unique-limits.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/connections/schema-unique-limits.md b/src/connections/schema-unique-limits.md index 7b14b6a125..817e0e586f 100644 --- a/src/connections/schema-unique-limits.md +++ b/src/connections/schema-unique-limits.md @@ -6,15 +6,15 @@ title: Segment Schema Limits 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. -**How many unique event properties can be logged on the event details page?** +**How many unique event properties and traits can be logged on the event details page?** -While you can track unlimited event properties and traits with Segment, the Schema page will have the following default limits: +While you can track unlimited event properties and traits with Segment, the Schema page has the following default limits: -* Properties: the event details page for a specific event can only show the first 300 properties by default. +* Properties: The event details page for a specific event can only show the first 300 properties by default. -* Traits: the Identify page can only show the first 300 traits by default. +* Traits: The Identify page can only show the first 300 traits by default. -After you hit the limit for both properties or traits, future properties/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. +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. 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"}. From a6b791aa617bf26d134a0363de996e8b7b856a78 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Tue, 13 Jun 2023 08:27:32 -0700 Subject: [PATCH 5/5] created headers --- src/connections/schema-unique-limits.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/connections/schema-unique-limits.md b/src/connections/schema-unique-limits.md index 817e0e586f..808434b6b0 100644 --- a/src/connections/schema-unique-limits.md +++ b/src/connections/schema-unique-limits.md @@ -2,30 +2,28 @@ title: Segment Schema Limits --- -**How many unique events can be logged in my Segment Schema table?** +#### How many unique events can be logged in my Segment Schema table? 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. -**How many unique event properties and traits can be logged on the event details page?** +#### How many unique event properties and traits can be logged on the event details page? While you can track unlimited event properties and traits with Segment, the Schema page has the following default limits: * Properties: The event details page for a specific event can only show the first 300 properties by default. - * Traits: The Identify page can only show the first 300 traits by default. 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. 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"}. -**How can I clear the Schema if I have hit the limits?** +#### How can I clear the Schema if I have hit the limits? 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. ![Clear your Schema data with Clear Schema History](images/schema_config_clear_schema.png) - -**How can I clear/archive properties in my source schema?** +#### How can I clear/archive properties in my source schema? 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.