Skip to content

Commit 285eabd

Browse files
committed
adding missing item [netlify-build]
1 parent 242f2e2 commit 285eabd

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/privacy/consent-management/consent-in-retl.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@ plan: consent-management
55

66
With Consent Management in Reverse ETL, you can enforce your end-users' consent preferences that are captured by your consent management platform (CMP) and stored in your warehouse.
77

8-
To enforce consent stored in your warehouse, build a Reverse ETL mapping that identifies consent categories. You can create a new mapping or update your mapping to identify the columns that store information about end user consent preferences and then enforce these preferences in [Reverse ETL-supported Actions destinations](/docs/connections/reverse-etl/reverse-etl-catalog/) and the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/).
8+
To enforce consent stored in your warehouse, build a Reverse ETL mapping that identifies consent categories. You can create a "consent to" column mapping in a new data model or update an existing data model to include a "consent to" mapping.
9+
10+
[Reverse ETL-supported Actions destinations](/docs/connections/reverse-etl/reverse-etl-catalog/) and the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/).
911

1012
> info "Consent in Reverse ETL supports Reverse ETL-supported Actions destinations and Segment Connections"
1113
> At this time, Consent in Reverse ETL does not support enforcing consent in the Segment Profiles destination. To enforce consent data in your classic Segment destinations, use the [Segment Connections destination](/docs/connections/destinations/catalog/actions-segment/).
@@ -44,7 +46,7 @@ To edit or disable consent categories, view the [Configure Consent Management](/
4446
> success ""
4547
> If you've already added a [Reverse ETL source] to your workspace, you can proceed to [Step 3: Identify consent columns](#step-3-identify-consent-columns).
4648
47-
If you haven't already configured a Reverse ETL source in your workspace, follow the instructions in the [Reverse ETL: Create a source](/docs/connections/reverse-etl/#step-1-add-a-source) documentation to add your warehouse as a data source. When you've configured your Reverse ETL source, proceed to [Step 3: Identify consent columns](#step-3-identify-consent-columns).
49+
If you haven't already configured a Reverse ETL source in your workspace, follow the instructions in the [Reverse ETL: Add a source](/docs/connections/reverse-etl/#step-1-add-a-source) documentation to add your warehouse as a data source. When you've configured your Reverse ETL source, proceed to [Step 3: Identify consent columns](#step-3-identify-consent-columns).
4850

4951
## Step 3: Identify consent columns
5052

0 commit comments

Comments
 (0)