From 3f4f5e4ddd53c54aba930f1295c163f614e90c09 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Thu, 25 Jul 2024 11:19:27 -0400 Subject: [PATCH] Update consent-in-retl.md --- src/privacy/consent-management/consent-in-retl.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/privacy/consent-management/consent-in-retl.md b/src/privacy/consent-management/consent-in-retl.md index 37b912ac12..8cbfe1454f 100644 --- a/src/privacy/consent-management/consent-in-retl.md +++ b/src/privacy/consent-management/consent-in-retl.md @@ -133,6 +133,9 @@ To add your first destination: 6. Enter the required information on the **Settings** tab of the destination. 7. Navigate to the destination settings tab and enable the destination. If the destination is disabled, then Segment won't be able to start a sync. +> info "Segment does not count Reverse ETL records filtered by Consent Management toward your Reverse ETL limits" +> Records filtered out by Consent Management are not counted as part of your Reverse ETL limits. For more information about Reverse ETL limits, see the [Reverse ETL Limits](/docs/connections/reverse-etl/#limits) documentation. + ## Validate your consent mapping You can validate that you successfully created your consent mapping in Segment Connections or supported Reverse ETL Actions destinations using the following methods.