From 2ffc8df8990d143cbe1efc079a1aa8cb9ad52780 Mon Sep 17 00:00:00 2001
From: Brandon Caudillo <52050659+bcaudillo@users.noreply.github.com>
Date: Tue, 16 Jul 2024 12:26:58 -0600
Subject: [PATCH] Fixed typo
---
.../consent-management/consent-in-segment-connections.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/privacy/consent-management/consent-in-segment-connections.md b/src/privacy/consent-management/consent-in-segment-connections.md
index f36ba748b7..b286cee36d 100644
--- a/src/privacy/consent-management/consent-in-segment-connections.md
+++ b/src/privacy/consent-management/consent-in-segment-connections.md
@@ -59,9 +59,9 @@ If an event includes both an integrations and consent object, Segment will look
| Consent Object | Integration Object | Result |
| --------------------------------------------------------------------------------------------------------------- | ------------------------------------------- | ------ |
| Not provided or empty consent object
`"context": {`
`}`
OR
`"context": {`
` "consent": {`
` }`
`}` | Not provided or empty object | Data flows to all destinations. |
-| Empty categoryPreference object
`"context": {`
` "consent": {`
` "categoryPreference": {`
` }`
` }`
`}`| Not provided or empty object | Data does **NOT** flow to any mapped destinations - consent is considered to be `false` for all categories.
Data flows to all destinations **NOT** mapped to a consent category. |
+| Empty categoryPreferences object
`"context": {`
` "consent": {`
` "categoryPreferences": {`
` }`
` }`
`}`| Not provided or empty object | Data does **NOT** flow to any mapped destinations - consent is considered to be `false` for all categories.
Data flows to all destinations **NOT** mapped to a consent category. |
| Not provided
`"context": {`
`}` | `{facebook: true,`
`amplitude: false}` | Data flows to the destinations that are `true` in the integrations object (Facebook). Any metadata provided in the integrations object also flows to your downstream destinations. |
-| Empty consent object
`"context": {`
` "consent": {`
` }`
`}`
OR
`"context": {`
` "consent": {`
` "categoryPreference": {`
` }`
` }`
`}`| `{facebook: true,`
`amplitude: false}` | Data does **NOT** flow to any mapped destinations - consent is considered to be `false` for all categories.
Data flows to all destinations **NOT** mapped to a consent category, destinations set to `true` in the integrations object, and destinations not included in the integrations object. |
+| Empty consent object
`"context": {`
` "consent": {`
` }`
`}`
OR
`"context": {`
` "consent": {`
` "categoryPreferences": {`
` }`
` }`
`}`| `{facebook: true,`
`amplitude: false}` | Data does **NOT** flow to any mapped destinations - consent is considered to be `false` for all categories.
Data flows to all destinations **NOT** mapped to a consent category, destinations set to `true` in the integrations object, and destinations not included in the integrations object. |
| `{ad: true,`
`analytics: false}`
_Segment has no category-to-destination mapping for ad and analytics_ | Provided, not provided, or empty object | Data flows to all destinations, as all destinations are unmapped. If the integrations object is present, data flow may be impacted. |
| `{ad: true,`
`analytics: false}`
_ad = facebook, google-ads_
| Not provided or empty object | Data flows to destinations that map to a consented purpose. In this case, data flows to all ad destinations (Facebook and Google Ads).
No data flows to analytics destinations. |
| `{ad: true,`
`analytics: false}`
_ad = facebook, google-ads_
_analytics = amplitude_ | `{facebook: true,`
`amplitude: false}` | Data flows to all ad destinations, even though Google Ads is not present in the integrations object.
Data does **NOT** flow to analytics destinations. |
@@ -78,4 +78,4 @@ If there is a category configured in Segment (`functional`) that is not mapped i
## Content observability
-Events discarded due to consent preferences appear in [Delivery Overview](/docs/connections/delivery-overview/) at the "Filtered at destination" step with the discard reason *Filtered by end user consent*.
\ No newline at end of file
+Events discarded due to consent preferences appear in [Delivery Overview](/docs/connections/delivery-overview/) at the "Filtered at destination" step with the discard reason *Filtered by end user consent*.