Skip to content

Commit 2507c2d

Browse files
committed
Update consent-management.md
1 parent 2288317 commit 2507c2d

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

src/privacy/consent-management.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Segment works with your third-party consent management platform (CMP) or bespoke
1414

1515
![Diagram outlining information flowing from an end user to Segment destinations](/docs/privacy/images/consent-overview.png)
1616

17-
After a user sets their consent preferences, Segment captures them with the [Analytics.js Consent Tools wrapper](https://github.com/segmentio/analytics-next/tree/master/packages/consent/consent-tools){:target="_blank"} and updates the [consent object](#consent-object). The events are then sent downstream to any streaming destinations in categories that a user consented to share data with.
17+
After a user sets their consent preferences, Segment captures them with a wrapper for your mobile and web libraries and updates the [consent object](#consent-object). The events are then sent downstream to any streaming destinations in categories that an end user consented to share data with.
1818

1919
> info ""
2020
> Segment collects consent for both registered users and anonymous users.
@@ -27,7 +27,6 @@ Segment requires every event from all of your sources to include the end-user co
2727
{
2828
"context": {
2929
"consent": {
30-
"version": 1,
3130
"consentPreferences": {
3231
"Advertising": true,
3332
"Analytics": false,
@@ -65,7 +64,6 @@ For example, if a user agreed to share their information with you for all catego
6564
"timestamp": "2023-01-01T00:00:00.000Z",
6665
"context": {
6766
"consent": {
68-
"version": 1,
6967
"consentPreferences" : {
7068
"Advertising": true,
7169
"Analytics": false,

0 commit comments

Comments
 (0)