-
Notifications
You must be signed in to change notification settings - Fork 365
Consent in Reverse ETL "soft" GA #6459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
cmastr
reviewed
Jun 12, 2024
cmastr
reviewed
Jun 12, 2024
Before you can enforce consent stored in your warehouse, take the following steps: | ||
- **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. | ||
- **Know how your company uses each destination**. You need to know which destinations to map to each category. | ||
- **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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had to read this last bullet a few times before understanding it. I think it needs an action at the front before 'end-user'.
cmastr
reviewed
Jun 12, 2024
cmastr
reviewed
Jun 12, 2024
cmastr
reviewed
Jun 12, 2024
cmastr
reviewed
Jun 12, 2024
cmastr
approved these changes
Jun 12, 2024
Co-authored-by: Casie Oxford <coxford@twilio.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Added page for consent in retl
Merge timing
When eng is complete
Related issues (optional)