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
+20-22Lines changed: 20 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Consent in Reverse ETL
3
3
plan: consent-management
4
4
---
5
5
6
-
With Consent Management in RETL, you can enforce your end-users' consent preferences that are captured by your consent management platform (CMP) and stored in your warehouse.
6
+
With Consent in RETL, you can enforce your end-users' consent preferences that are captured by your consent management platform (CMP) and stored in your warehouse.
7
7
8
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/).
9
9
@@ -23,7 +23,7 @@ Before you can enforce consent stored in your warehouse, take the following step
23
23
## Step 1: Create consent categories in the Segment app
24
24
25
25
> info "Limited availability of destinations"
26
-
> Reverse ETL supports the destinations in the [Reverse ETL catalog](/docs/connections/reverse-etl/reverse-etl-catalog/) and Segment Connections.
26
+
> Reverse ETL supports the Actions destinations in the [Reverse ETL catalog](/docs/connections/reverse-etl/reverse-etl-catalog/) and [Segment Connections](/docs/connections/destinations/catalog/actions-segment/).
27
27
28
28
1. From the [Segment homepage](https://app.segment.com/goto-my-workspace/){:target="_blank”}, select the Privacy tab and click **Consent Management**.
29
29
2. On the Consent management page, click **Create categories**.
@@ -40,12 +40,10 @@ Before you can enforce consent stored in your warehouse, take the following step
40
40
41
41
## Step 2: Identify consent columns
42
42
43
-
After you set up consent categories in the Segment app, you must identify the columns in your data warehouse that store end user consent by creating a *model*, or SQL query that defines the set of data you want to synchronize to your Reverse ETL destinations. When building your RETL data model, Segment recommends storing consent as a boolean of either `true` or `false` and mapping only one consent category to each column.
43
+
After you set up consent categories in the Segment app, you must identify the columns in your data warehouse that store end user consent by creating a *model*, or SQL query that defines the set of data you want to synchronize to your Reverse ETL destinations. When building your RETL data model, Segment recommends that you store consent as a boolean `true` or `false`value and map one consent category to one column.
44
44
45
-
<!--- todo: confirm with Atit that the true/false recommendation is still correct --->
46
-
47
-
> error "Creating a data mapping that does not include information about consent preferences results in no consent enforcement"
48
-
> If you create consent categories in your workspace but fail to identify columns that contain consent preferences in your data mapping, events will flow to all destinations in your workspace regardless of end user consent preferences.
45
+
> error "Creating a data model that does not include information about consent preferences results in no consent enforcement"
46
+
> 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.
49
47
50
48
To add your first model:
51
49
1. Navigate to Connections > Sources and select the Reverse ETL tab. Select your source and click **Add Model**.
@@ -57,37 +55,37 @@ To add your first model:
57
55
6. Click **Next**.
58
56
7. Enter your Model Name.
59
57
8. Click **Create Model**.
60
-
61
-
To edit a model:
62
-
1. Navigate to Connections > Sources and select the Reverse ETL tab. Select your source and click **Add Model**.
63
-
64
-
<!---TODO: finish the above step when I get access to a test environment --->
58
+
_(Optional): You can opt
65
59
66
60
> info "Consent categories in the Segment app must match consent columns identified in your data warehouse before continuing"
67
61
> If you create consent categories in the Segment app but fail to identify a column for each category you created in Segment, you will not be able to proceed until you enable a destination mapped to a consent category not identified in the data model.
68
62
69
-
## Step 3: Send events to your downstream destinations
63
+
## Step 3: Events flow to your downstream destinations
70
64
71
-
After you set up categories in the Segment app and create a RETL mapping that extracts consent information, you can send events to your downstream destinations.
65
+
After you set up categories in the Segment app and create a RETL model that extracts consent information, events begin to flow to your downstream destinations.
72
66
73
67
> info "Consent in Reverse ETL supports RETL destinations and Segment Connections"
74
68
> At this time, Consent in Reverse ETL does not support enforcing consent in the [Segment Profiles destination](/docs/connections/destinations/catalog/actions-segment-profiles/).
75
69
76
-
<!--- TODO: finish this step ^^^ --->
70
+
### Segment Connections destination
71
+
72
+
Segment automatically adds the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) to every event that's routed downstream to your Segment Connections destination. [Consent enforcement in Connections](/docs/privacy/consent-management/consent-in-segment-connections/) validates that only consenting data flows downstream to any classic Segment destinations connected to your Segment Connections instance.
73
+
74
+
### Reverse ETL Actions destinations
75
+
76
+
Segment automatically filters out data from users who have not consented to the category mapped to your destination.
77
77
78
78
## Validate your consent mapping
79
79
80
-
You can validate that you successfully created your consent mapping in Segment Connections, Segment Profiles, and supported Reverse ETL Action destinations using the following methods:
80
+
You can validate that you successfully created your consent mapping in Segment Connections or supported Reverse ETL Actions destinations using the following methods:
81
81
82
-
### Segment Connections
82
+
### Segment Connections destination
83
83
Open the Source Debugger for your Reverse ETL source and confirm that the [consent object](/docs/privacy/consent-management/consent-in-segment-connections/#consent-object) appears on every event and that the consent object has the categories you mapped in [Step 2: Identify consent columns](#step-2-identify-consent-columns).
84
84
85
85
<!--- ### Segment Profiles
86
86
Open the [Profile Explorer](/docs/unify/#profile-explorer) and verify that your profiles contain the [Segment Consent Preference Updated](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) event. --->
87
87
88
-
### Supported Reverse ETL Actions destinations
89
-
Segment automatically filters out data belonging to users who have not consented to the category that a supported Actions destination is mapped to.
90
-
91
-
<!--- TODO: rewrite the above sentence--->
88
+
### Reverse ETL Actions destinations
89
+
Segment automatically filters out data from users who have not consented to the category mapped to your destination.
92
90
93
-
To verify that this is working as intended, open [Delivery Overview](/docs/connections/delivery-overview) for a supported Actions destination and view some of the events that were successfully delivered to the destination. The events in your destination should only come from users that consented to send data to the category that your supported Actions destination belongs to.
91
+
To verify that this behavior is working as intended, open [Delivery Overview](/docs/connections/delivery-overview) for a RETL-supported Actions destination and view some of the events that were successfully delivered to the destination. The events in your destination should only come from users that consented to send data to the category that your supported Actions destination belongs to.
When an end user visits your web or mobile app, they set **consent preferences**, or make decisions about the types of data they want you to collect, use, and share. These consent preferences are typically presented as a set list of categories that describe how your company intends to use that data. Some common categories include personalization, advertising, and site performance.
0 commit comments