For the complete documentation index, see llms.txt. This page is also available as Markdown.

Enforce compliance on your audience

Attach processing activities to a segment so user choices are respected before anyone is included or activated.

Your goal

Make sure a segment only ever contains users whose choices permit the use you intend, and that the permission is enforced by the platform rather than by convention.

Expected outcome

A segment carrying one or more processing activities, with the platform checking user choices before including a user, and removing a user from the segment when their choice changes in a way that makes them incompatible with it. A feed on the segment then removes that user from the partner platform too, because they left the segment.

When this is useful

Before any activation. A processing activity represents what you expect to do with the data, paired with a legal basis. A user choice is the choice a user makes for one of your processing activities. Attaching processing activities to a segment sets a privacy wall on it: only users whose choices allow them can be in the segment. Read Manage consent & Processing activities to learn more. This page covers what those concepts mean on a segment, which is where the behaviour is specific and easy to get wrong.

Prerequisites

Your processing activities are defined, and user choices are captured for them. See Manage consent & Processing activities.

Attach processing activities to a segment

1

Open the segment edition page

On the segment edition page, find the Processing Activities section and click Add Processing Activity.

2

Select the processing activities

Select the processing activity, or activities, that justify the creation of this segment. If you select several, they are combined with AND: a user must have valid choices for all the selected processing activities to be in the segment. See Combining several choices.

3

Save

Click Save to apply the configuration. From this moment, the platform checks user choices before including end users in the segment.

What the platform then does

The check point depends on the segment type, and the difference is not cosmetic.

Segment type
How consent is enforced

Implicit conditions are added to the segment query, so it only scans users with compatible user choices. Enforcement happens at computation.

User choices are checked before the user is added to the segment.

The consequence for a Query segment: attaching a processing activity changes the query, so the segment has to be computed again before its population reflects the new rule.

Combining several choices

This is the asymmetry to remember, because the two cases pull in opposite directions.

On a segment: AND

If you add several choices to a segment, the user choices must be compatible with all the processing activities. You are using the AND condition between choices.

On a channel: OR

For a channel, choices from at least one processing activity must be valid for data to be ingested. You are using the OR condition between choices.

Segment types that cannot carry a processing activity

That does not mean consent stops mattering on them - Edge follows the same consent management requirements as the rest of the platform, and an unconsented user's tag does not fire at all. It means the segment-level mechanism is unavailable, so compliance for those audiences has to be handled upstream: at collection, in the channel's processing activities, or in the segment they derive from.

What happens when a choice changes later

Consent is not only checked on the way in. A live feed sends delete operations for users leaving the segment - and that includes users who updated their user choice in a way that makes it incompatible with being in the segment, where you chose to use a processing activity when defining it.

This is the practical reason to attach the processing activity to the segment rather than filtering the audience yourself before import: the deletion path back to the partner only exists if the platform knows the rule.

Verification

  • The segment's Processing Activities section lists the processing activities you expect.

  • For a Query segment, the user count after the next computation reflects the restriction.

  • On an activated segment, delete operations appear in the feed's stats as choices change. See Track a feed.

Last updated

Was this helpful?