You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/privacy/consent-management/consent-in-retl.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ To enforce consent stored in your warehouse, build a Reverse ETL model that iden
19
19
Before you can enforce consent stored in your warehouse, take the following steps:
20
20
-**Set up your third-party consent management tool and create consent categories**. Take note of your consent categories and the key or ID associated with each category.
21
21
-**Know how your company uses each destination**. You need to know which destinations to map to each category.
22
-
-**End-user consent stored in a warehouse that [Segment supports for Reverse ETL](/docs/connections/reverse-etl/#step-1-add-a-source)**. Segment supports Reverse ETL capabilities in Azure, BigQuery, Databricks, Postgres, Snowflake, and Redshift data warehouses. Other data warehouses are not supported.
22
+
-**Store your end user consent in a warehouse that [Segment supports for Reverse ETL](/docs/connections/reverse-etl/#step-1-add-a-source)**. Segment supports Reverse ETL capabilities in Azure, BigQuery, Databricks, Postgres, Snowflake, and Redshift data warehouses. Other data warehouses are not supported.
23
23
24
24
## Step 1: Create consent categories in the Segment app
25
25
@@ -54,6 +54,7 @@ After you set up consent categories in the Segment app, you must identify the co
54
54
> error "Creating a data model that does not include information about consent preferences results in no consent enforcement"
55
55
> If you create consent categories in your workspace but fail to identify columns that contain consent preferences in your data model, events flow to all destinations in your workspace regardless of end user consent preferences.
56
56
57
+
### Identify consent when building your model
57
58
To identify consent when building your model:
58
59
1. Navigate to Connections > Sources and select the Reverse ETL tab. Select your source and click **Add Model**.
59
60
2. Click **SQL Editor** as your modeling method.
@@ -69,6 +70,7 @@ To identify consent when building your model:
69
70
11. Select **Add consent mapping** to identify columns for all of your consent categories.
70
71
12. When you're satisfied with your consent mappings, click **Save**.
71
72
73
+
### Update your Reverse ETL mode to include consent
72
74
To update an existing Reverse ETL model to include consent enforcement:
73
75
1. Navigate to **Connections > Destinations** and select the **Reverse ETL** tab.
74
76
2. Select the source and the model you want to edit.
0 commit comments