Add an ID Consent Category

The ID Consent category stores consent information about a single identifier — for example, consent captured against an email address rather than against the person. For what each category stores and how it behaves after ID resolution, see Categories for adding Catalogue fields. Once an ID Consent field exists, you can use it in destination mapping to control which identifier values are sent to a destination — see Filter ID on User Consent below. Perform the following steps to add an ID Consent category:

Enter a Catalogue Field. As you type, suggestions based on the existing Catalogue Fields appear. You can choose a suggested Catalogue Field or click +Add Catalogue Field to add a new field.

Map the Catalogue Field to its corresponding Source Field. Same as the above behaviour, you can choose a suggested Source Field or click +Add a new Source Field to add a new field.

Enter a description for easy identification.

Choose String as the Data Type.

Choose ID Consent as the Category.

Under advanced settings, a Group Name appears by default. Select the Group Name from the drop-down menu. Ensure to select the appropriate Group Name for which you are creating the ID Consent category.

Save the changes.

When you activate an audience or a journey, you can filter the identifier values that are sent to a destination by consent status. The filter is set in destination mapping: a filter icon appears for every identifier you are sending. This is deliberately different from a consent rule on the audience itself. An audience-level consent rule disqualifies people; this filter decides only which identifier values leave with the audience. Destination mapping is also the only place an ID Consent field can be used — it cannot be used in audience or journey filtering. See Consent Orchestration for the audience-level and channel-level consent rules.

Filter modes

A filter uses the same three consent states as audience rules — see Consent Information Operators:

Mode	Meaning
Consent Given	The user has provided consent.
Consent Not Given	The user has explicitly denied or not provided consent.
Information Not Present	No consent information is available.

Consent can be stored at two levels: against the person (a Consent category field) and against a single identifier (an ID Consent field). Which level you filter on changes how much of the identifier is sent:

You filter by	What is sent
User Consent	All values of that identifier are sent, provided the user-level consent qualifies. The decision is taken once, for the person.
ID Consent	Only the identifier values whose own consent qualifies are sent. The decision is taken per value.

For example, a profile holds three values for one identifier and the ID Consent field qualifies only two of them. Filtering on ID Consent sends those two values. Filtering on User Consent sends all three, provided the person’s own consent qualifies.

NoteThe filter icon appears when a consent attribute is present in your catalogue, along with the option to filter by User Consent or by ID Consent.

Add an ID Consent Category

Filter modes

Categories for adding Catalogue fields

Add an ID Category

Add a Consent Category

Consent Orchestration

Work with Operators