Skip to content

Commit 5c2a6a5

Browse files
committed
Add reconcile conflicts header, cmp and Segment conflict info [netlify-build]
1 parent e6580a0 commit 5c2a6a5

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

src/privacy/consent-management.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,10 @@ Segment assigns a `version` to your consent object. The `version` describes the
9393
A consent conflict flag and the categories consented to by a user are both pulled from the consent object and are visible as traits on a user's profile in Unify. --->
9494

9595

96+
## Reconcile consent conflicts
97+
98+
Segment resolves conflicts between your [consent object and your integration object](#reconcile-consent-object-and-integrations-object-conflicts) and between your CMP and the consent categories you configured in the Segment app.
99+
96100
### Reconcile consent object and integrations object conflicts
97101

98102
You can add both the integrations object and the consent object to your Segment payloads for greater control over how Segment routes data to your downstream destinations.
@@ -115,7 +119,13 @@ If an event includes both an integrations and consent object, Segment will look
115119
| `{ad: true,` <br>`analytics: true}`<br><br>_ad = facebook, google ads_ <br> _analytics = facebook, amplitude_ | `{facebook: true,`<br>`amplitude: false}` | Data delivered to all ad destinations, including Facebook, because analytics is true. <br> Metadata is sent from Facebook. <br> No data is sent to Amplitude because it is `false` in the integrations object. |
116120
| `{ad: false,` <br>`analytics: true}` <br><br>_ad = facebook, google ads_ <br> _analytics = facebook, amplitude_ | `{facebook: true,`<br>`amplitude: false}` | Data **NOT** delivered to ad destinations. Data delivered to Facebook for analytics only and not to Amplitude. |
117121

122+
### Reconcile CMP and Segment consent category conflicts
123+
124+
If you have a category configured in your consent management tool (for example, `advertising`) and there is no matching category in the Segment app, data will flow to unmapped destinations. If destinations are mapped to a different category in the Segment app, data will flow to those destinations.
125+
126+
If destination names do not match exactly (for example, your CMP has a `advertising` category and the Segment app has an `ad` category,) data will not be shared with destinations in the `ad` category.
118127

128+
If there is a category configured in Segment (`functional`) that is not mapped in your CMP, no data will be shared with the destinations mapped to the `functional` category.
119129

120130
## Consent observability
121131

0 commit comments

Comments
 (0)