Update Product limits (#4277)

* updates

* Update src/connections/rate-limits.md

Co-authored-by: rchinn-segment <[email protected]>

---------

Co-authored-by: rchinn-segment <[email protected]>

Author: markzegarelli

src/connections/rate-limits.md

@@ -1,12 +1,16 @@
 ---
-title: Rate Limits
+title: Product Limits
 ---
-These rate limits were added to product documentation on August 31, 2020.
+These limits were updated on February 22, 2023.
 
-## Inbound Data Ingestion API Rate Limit
+## Event properties ingestion limit
+
+Events ingested by Segment have a limit of **10,000** properties per individual event received. For example, two Track events named "Page Viewed" and "Signup completed" each have their own limit. Segment will not persist properties beyond this limit, and will drop any corresponding values.
+
+## Inbound data ingestion API rate limit
 
 If within a ten minute period a Customer's sources (in aggregate) send more than 60 million events (average of 100,000 events per second) without prior arrangement, Segment reserves the right to queue any additional events and process those at a rate that does not exceed 60 million events in any ten minute period.
 
-## Outbound Downstream Destination Rate Limits
+## Outbound downstream destination rate limits
 
 Most destinations have their own rate limits that Segment cannot control. In some instances, Segment is able to ingest and attempt to deliver data faster than the downstream destination is able to accept data. Outbound requests to a destination may also fail for other reasons outside of Segment's control. When requests to downstream destinations fail, Segment makes additional attempts to deliver the data (retries). However, when more than 1,000 requests per second to a downstream destination fail or when the failure rate for a downstream destination exceeds 50% for more than 72 hours, Segment reserves the right to reduce the number of retries until the condition is resolved.

src/connections/spec/index.md

@@ -7,9 +7,12 @@ The Segment Spec provides guidance on meaningful data to capture, and the best f
 
 {% include components/reference-button.html href="https://university.segment.com/introduction-to-segment/324252?reg=1&referrer=docs" icon="media/academy.svg" title="Segment University: The Segment Methods" description="Check out our high-level overview of these APIs in Segment University. (Must be logged in to access.)" %}
 
+> warning "Event and Product Limits"
+> Events ingested by Segment are subject to defined [Product Limits](/docs/connections/rate-limits).
+
 The Segment Spec has three components.
 
-First, it **outlines the semantic definition of the customer data we capture across all of Segment's libraries and APIs**.  There are six API calls in the Spec. They each represent a distinct type of semantic information about a customer. Every call shares the same [common fields](/docs/connections/spec/common/).
+First, it **outlines the semantic definition of the customer data Segment captures across all libraries and APIs**.  There are six API calls in the Spec. They each represent a distinct type of semantic information about a customer. Every call shares the same [common fields](/docs/connections/spec/common/).
 - APIs
   - [Identify](/docs/connections/spec/identify/): who is the customer?
   - [Track](/docs/connections/spec/track/): what are they doing?
@@ -18,13 +21,13 @@ First, it **outlines the semantic definition of the customer data we capture acr
   - [Group](/docs/connections/spec/group/): what account or organization are they part of?
   - [Alias](/docs/connections/spec/alias/): what was their past identity?
 
-Second, it **details the event data we capture across some of our cloud sources and destinations**.
+Second, it **details the event data Segment captures across some cloud sources and destinations**.
 - Cloud Sources and Destinations
   - [Email](/docs/connections/spec/email/)
   - [Live Chat](/docs/connections/spec/live-chat/)
   - [A/B Testing](/docs/connections/spec/ab-testing/)
 
-Third, it **shares the events we recommend you track for a particular industry based on our experience working with thousands of customers**. When you respect these specs, we can map these events to particular features within end destinations like Google Analytics and Facebook Ads.
+Third, it **shares the events Segment recommends you track for a particular industry based on experience working with thousands of customers**. When you respect these specs, Segment maps these events to particular features within end destinations like Google Analytics and Facebook Ads.
 - Industry Specs
   - [Mobile](/docs/connections/spec/mobile/)
   - [E-Commerce](/docs/connections/spec/ecommerce/v2/)