Skip to content

Commit 76e58fa

Browse files
committed
add note to retl page
1 parent 685fdb8 commit 76e58fa

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/connections/reverse-etl/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ Follow these 4 steps to set up Reverse ETL and learn what each component is abou
2626
3. [Add a destination](#step-3-add-a-destination)
2727
4. [Create mappings](#step-4-create-mappings)
2828

29-
> info ""
30-
> The UI navigation and interface will look different from what's presented in the docs until Reverse ETL rolls out to all users for GA.
29+
> info "Enforce consent preferences stored in your warehouse with Consent Management
30+
> Use Consent Management to enforce your end users' consent preferences across your downstream Reverse ETL supported destinations. See the [Consent in Reverse ETL documentation](/docs/privacy/consent-management/consent-in-retl/) for more information.
3131
3232
### Step 1: Add a source
3333
A source is where your data originates from. Traditionally in Segment, a [source](/docs/connections/sources/#what-is-a-source) is a website, server library, mobile SDK, or cloud application which can send data into Segment. In Reverse ETL, your data warehouse is the source.
@@ -92,7 +92,7 @@ To add your first destination:
9292
After you’ve added a destination, you can create mappings from your warehouse to the destination. Mappings enable you to map the data you extract from your warehouse to the fields in your destination.
9393

9494
To create a mapping:
95-
1. Navigate to **Conections > Destinations** and select the **Reverse ETL** tab.
95+
1. Navigate to **Connections > Destinations** and select the **Reverse ETL** tab.
9696
2. Select the destination that you want to create a mapping for.
9797
3. Click **Add Mapping**.
9898
4. Select the model to sync from.

0 commit comments

Comments
 (0)