From 790facb38d6f33aa2c8b16032eaf0cfbe3e9dfb2 Mon Sep 17 00:00:00 2001 From: Gil Omer Date: Thu, 4 Sep 2025 15:18:59 -0400 Subject: [PATCH 1/4] update retl usage documentation --- src/connections/reverse-etl/system.md | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/src/connections/reverse-etl/system.md b/src/connections/reverse-etl/system.md index ea5676b20d..89730d43e3 100644 --- a/src/connections/reverse-etl/system.md +++ b/src/connections/reverse-etl/system.md @@ -51,19 +51,13 @@ State management: The `__segment_reverse_etl` schema and its associated tables ( To provide consistent performance and reliability at scale, Segment enforces default use and rate limits for Reverse ETL. ### Usage limits -Reverse ETL usage limits are measured based on the number of records processed to each destination – this includes both successful and failed records. For example, if you processed 50K records to Braze and 50K records to Mixpanel, then your total Reverse ETL usage is 100K records. +Reverse ETL usage limits are measured based on the number of records processed to each destination – this includes only successful records. For example, if you processed 50K records to Braze and 50K records to Mixpanel, then your total Reverse ETL usage is 100K records. Processed records represents the number of records Segment attempts to send to each destination. Keep in mind that not all processed records are successfully delivered, for example, such as when the destination experiences an issue. -Your plan determines how many Reverse ETL records you can process in one monthly billing cycle. If you've reached your Reverse ETL limit, contact your sales representative to discuss an add-on that increases your Reverse ETL record allotment. To see how many records you’ve processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab. +Segment tracks how many Reverse ETL records you process in one monthly billing cycle. To see how many records you've processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab. Note that Segment will not block Reverse-ETL syncs due to usage. -Plan | Number of Reverse ETL records you can process to destinations per month | How to increase your number of Reverse ETL records ----- | --------------------------------------------------------------------------- | --------------------------------------------------- -Free | 500K | Upgrade to the Teams plan in the Segment app by navigating to **Settings > Usage & billing**. -Teams | 1 million | Contact your sales representative to upgrade your plan to Business. -Business | 50 x the number of [MTUs](/docs/guides/usage-and-billing/mtus-and-throughput/#what-is-an-mtu)
or .25 x the number of monthly API calls | Contact your sales rep to upgrade your plan. - -If you have a non-standard or high volume usage plan, you may have unique Reverse ETL limits or custom pricing. To see your Reverse ETL limits in the Segment app, select **Settings > Usage & Billing**. +Segment tracks your Reverse ETL usage for visibility purposes, but your syncs will continue to run regardless of usage. If you have questions about your Reverse ETL usage, contact your Segment representative. ### Configuration limits From 2e7d158aa133229a38b66f3232a9b26bbda0ba4d Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 4 Sep 2025 16:56:38 -0400 Subject: [PATCH 2/4] Update src/connections/reverse-etl/system.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/reverse-etl/system.md | 1 - 1 file changed, 1 deletion(-) diff --git a/src/connections/reverse-etl/system.md b/src/connections/reverse-etl/system.md index 89730d43e3..58a6153372 100644 --- a/src/connections/reverse-etl/system.md +++ b/src/connections/reverse-etl/system.md @@ -57,7 +57,6 @@ Processed records represents the number of records Segment attempts to send to e Segment tracks how many Reverse ETL records you process in one monthly billing cycle. To see how many records you've processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab. Note that Segment will not block Reverse-ETL syncs due to usage. -Segment tracks your Reverse ETL usage for visibility purposes, but your syncs will continue to run regardless of usage. If you have questions about your Reverse ETL usage, contact your Segment representative. ### Configuration limits From 68f3d114217b20f5f19e96a42de7e351188ce52f Mon Sep 17 00:00:00 2001 From: Gil Omer <80776787+gilsegment@users.noreply.github.com> Date: Thu, 4 Sep 2025 16:56:49 -0400 Subject: [PATCH 3/4] Update src/connections/reverse-etl/system.md Co-authored-by: forstisabella <92472883+forstisabella@users.noreply.github.com> --- src/connections/reverse-etl/system.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/system.md b/src/connections/reverse-etl/system.md index 58a6153372..3d2ff0b4aa 100644 --- a/src/connections/reverse-etl/system.md +++ b/src/connections/reverse-etl/system.md @@ -55,7 +55,9 @@ Reverse ETL usage limits are measured based on the number of records processed t Processed records represents the number of records Segment attempts to send to each destination. Keep in mind that not all processed records are successfully delivered, for example, such as when the destination experiences an issue. -Segment tracks how many Reverse ETL records you process in one monthly billing cycle. To see how many records you've processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab. Note that Segment will not block Reverse-ETL syncs due to usage. +Segment doesn't limit how many Reverse ETL records you can process in one monthly billing cycle. + +To track how many records you've processed using Reverse ETL, navigate to **Settings > Usage & billing** and select the **Reverse ETL** tab. For questions about Reverse ETL usage, contact your account team or reach out to [Segment support](segment.com/help/contact){:target="_blank”}. ### Configuration limits From 9c1d77732e463c6be23852400d1d0918957be15d Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Fri, 5 Sep 2025 10:40:13 -0400 Subject: [PATCH 4/4] rm addtl references to "limits" --- src/connections/reverse-etl/system.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/reverse-etl/system.md b/src/connections/reverse-etl/system.md index 3d2ff0b4aa..2b4ff49a71 100644 --- a/src/connections/reverse-etl/system.md +++ b/src/connections/reverse-etl/system.md @@ -50,8 +50,8 @@ State management: The `__segment_reverse_etl` schema and its associated tables ( ## Limits To provide consistent performance and reliability at scale, Segment enforces default use and rate limits for Reverse ETL. -### Usage limits -Reverse ETL usage limits are measured based on the number of records processed to each destination – this includes only successful records. For example, if you processed 50K records to Braze and 50K records to Mixpanel, then your total Reverse ETL usage is 100K records. +### Usage +Segment measures Reverse ETL usage measured based on the number of records processed to each destination – this includes only successful records. For example, if you processed 50K records to Braze and 50K records to Mixpanel, then your total Reverse ETL usage is 100K records. Processed records represents the number of records Segment attempts to send to each destination. Keep in mind that not all processed records are successfully delivered, for example, such as when the destination experiences an issue.