Skip to content

Commit b50e2c2

Browse files
committed
add unify page to related, add to protocols page
1 parent ae1e0a3 commit b50e2c2

File tree

5 files changed

+12
-3
lines changed

5 files changed

+12
-3
lines changed

src/privacy/consent-management/configure-consent-management.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Configure Consent Management
33
related:
44
- "/privacy/consent-management/"
55
- "/privacy/consent-management/consent-in-segment-connections/"
6+
- "/privacy/consent-management/consent-in-unify/"
67
redirect_from: "/privacy/configure-consent-management"
78
---
89

src/privacy/consent-management/consent-in-segment-connections.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Consent in Segment Connections
33
related:
44
- "/privacy/consent-management/"
55
- "/privacy/consent-management/configure-consent-management/"
6+
- "/privacy/consent-management/consent-in-unify/"
67
redirect_from: "/privacy/consent-in-segment-connections"
78
---
89

src/privacy/consent-management/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Consent Management Overview
33
related:
44
- "/privacy/consent-management/configure-consent-management/"
55
- "/privacy/consent-management/consent-in-segment-connections/"
6+
- "/privacy/consent-management/consent-in-unify/"
67
---
78

89
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.

src/protocols/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ To consolidate the views in the Schema tab, Segment automatically converts `page
3030

3131
### How can I see who made changes to my Tracking Plan?
3232

33-
Each Tracking Plan includes a Changelog, which shows which changes were made by which users. To view it, open a Tracking Plan, click the **...** button (also known as the dot-dot-dot, or ellipses menu) next to the Edit Tracking Plan button, and click **View Changelog**.
33+
Each Tracking Plan includes a Changelog, which shows which changes were made by which users. To view it, open a Tracking Plan, click the **...** button (also known as the dot-dot-dot, or ellipses menu) next to the Edit Tracking Plan button, and click **View Changelog**. In the Changelog, Consent Management users also see when the Segment Consent Preference Updated event was added to their workspace.
3434

3535
### How many Sources can I connect to a Tracking Plan?
3636

src/protocols/tracking-plan/create.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,13 +18,19 @@ The Segment Tracking Plan feature allows you to validate your expected events ag
1818
1919
Tracking Plans are stored in workspaces and can be connected to one or more Sources.
2020

21+
> info "Segment Consent Preference Updated Event"
22+
> After setting up a consent category, users of Consent Management see a Segment Consent Preference Updated Event added to all existing Tracking Plans.
23+
2124
## Create a Tracking Plan
2225

2326
To create a new Tracking Plan:
2427
1. Contact your Segment account team to enable the Protocols features in your workspace.
2528
2. Once enabled, click **Protocols** in the left bar navigation.
2629
3. Click **New Tracking Plan**.
27-
4. Add events, properties, traits and filters in the Tracking Plan editor. <br> You'll see an option to import events and traits to your Tracking Plan that your source received in the last 24 hours, 7 days or 30 days. This option is great if you want to get started with your current events.
30+
4. Add events, properties, traits and filters in the Tracking Plan editor. <br> You'll see an option to import events and traits to your Tracking Plan that your source received in the last 24 hours, 7 days or 30 days. This option is great if you want to get started with your current events.
31+
32+
> info "Consent Management users see the Segment Consent Preference Updated event on new Tracking Plans"
33+
> If you are a Consent Management user, Segment automatically adds the [Segment Consent Preference Updated event](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) to all new Tracking Plans.
2834
2935
## Copy a Tracking Plan
3036

@@ -62,7 +68,7 @@ To create a new Tracking Plan by uploading a CSV file:
6268
After uploading your CSV file, you are redirected to the Upload & Download History page while the upload is in progress. If the CSV upload fails, you'll be able to either view the error directly in the Reports column on the Upload & Download History page or download the `error_report.csv` file that corresponds to the Tracking Plan you uploaded.
6369

6470
> success ""
65-
> Tracking Plans created by an uploaded file are reflected in the [Audit Trail](docs/segment-app/iam/audit-trail/) and [Tracking Plan changelog](/docs/protocols/faq/#how-can-i-see-who-made-changes-to-my-tracking-plan).
71+
> Tracking Plans created by an uploaded file are reflected in the [Audit Trail](docs/segment-app/iam/audit-trail/) and [Tracking Plan changelog](/docs/protocols/faq/#how-can-i-see-who-made-changes-to-my-tracking-plan). If you are a Consent Management user, Segment automatically adds the [Segment Consent Preference Updated event](/docs/privacy/consent-management/consent-in-unify/#segment-consent-preference-updated-event) to all new Tracking Plans.
6672
6773
### Update an existing Tracking Plan
6874

0 commit comments

Comments
 (0)