Skip to content

Commit a300458

Browse files
committed
init consent GA
1 parent 90cd1b0 commit a300458

File tree

4 files changed

+2
-7
lines changed

4 files changed

+2
-7
lines changed

src/connections/delivery-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The pipeline view shows the following steps:
2424
- **Successfully received**: Events that Segment ingested from your source
2525
- **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules
2626
- **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) Tracking Plans
27-
- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. Beta users of [Consent Management](/docs/privacy/consent-management/) also see events discarded due to consent preferences.
27+
- **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. [Consent Management](/docs/privacy/consent-management/) users also see events discarded due to consent preferences.
2828
- **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements
2929
- **Successful delivery**: Events that were successfully delivered to the destination
3030

src/privacy/configure-consent-management.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,6 @@ related:
55
- "/privacy/consent-in-segment-connections/"
66
- "/privacy/consent-in-unify/"
77
---
8-
> info "Consent Management is in public beta"
9-
> This means that Consent Management features are in active development, and some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
108

119
After setting up your consent management platform (CMP), you can enforce the consent collected from your users by adding the [consent object](/docs/privacy/consent-in-segment-connections/#consent-object) to your events.
1210

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

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,6 @@ related:
55
- "/privacy/configure-consent-management/"
66
---
77

8-
> info "Consent Management is in public beta"
9-
> This means that Consent Management features are in active development, and some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
10-
118
Segment Connections users can add the [consent object](#consent-object) to their sources to stamp events with the end user consent preferences captured by your consent management platform (CMP) and send them downstream to destinations in categories that an end user consented to share data with. Events without the consent object continue to flow to destinations without consent enforcement.
129

1310
For more information about configuring consent categories, see the [Configure Consent Management](/docs/privacy/configure-consent-management/#step-1-create-consent-categories-in-the-segment-app) documentation.

src/segment-app/iam/audit-trail.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ The Audit Trail returns information about the following Segment product areas:
2121
- Warehouses
2222
- Destinations
2323
- Storage
24+
- Consent Management
2425
- Tracking Plans
2526
- Destination Filters
2627
- Transformations
@@ -33,7 +34,6 @@ The Audit Trail returns information about the following Segment product areas:
3334
- Journeys
3435
- Broadcasts
3536
- Workspace
36-
<!--- IG, 11/2023: Add consent to this list when this goes to public beta (q1 '24?)--->
3737

3838
To view a list of all events Segment surfaces in the Audit Trail, open the Audit Trail, click **Filters**, and select the **Events** dropdown.
3939

0 commit comments

Comments
 (0)