Skip to content

Commit d32d8d5

Browse files
committed
fix broken image [netlify-build]
1 parent 82d5fe9 commit d32d8d5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/privacy/consent-management/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ When an end user visits your web or mobile app, they set **consent preferences**
1010

1111
Segment integrates with your commercial third-party or bespoke consent management platform (CMP) that captures an end user's consent preferences and enforces those preferences by only routing events to the categories consented to by an end user.
1212

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

1515
After a user sets their consent preferences on your web or mobile app, Segment requires you to add the [consent object](/docs/privacy/consent-in-segment-connections/#consent-object) to all events. If you are using OneTrust, Segment provides a wrapper for your web and mobile libraries that can add the consent object to your events. If you are using another CMP, you are required to add the consent object to your events by either creating your own wrapper or using another mechanism. For more information, see the [Configure Consent Management documentation](/docs/privacy/configure-consent-management/#step-2-integrating-your-cmp-with-segment).
1616

0 commit comments

Comments
 (0)