Walkthrough: Customizing interaction purge conditions


Walkthrough to extend the purging tool with custom filters of interaction data.

You can extend the purging tool with custom conditions to further filter interaction data extraction before purging. This option is useful to refine the selection of interaction data to purge for more specific use cases.

This walkthrough describes how to:

  • Implement the IInteractionCondition interface

  • Register the custom condition

To create a custom condition:

  • Implement the Sitecore.XConnect.DataTools.Abstractions.Conditions.IInteractionCondition interface with a unique ConditionId.


    The ConditionId is a string you set that uniquely identifies it in the system. You must pass the ConditionId in the Conditions POST parameter during task registration.

    For example:

    public interface IInteractionCondition
        bool IsAccepted(Interaction interaction);
        string ConditionId { get; }
    public class ChannelInteractionCondition : IInteractionCondition
        public static readonly Guid ChannelId = new Guid("DF9900DE-61DD-47BF-9628-058E78EF05C6");
        public string ConditionId { get; } = nameof(ChannelInteractionCondition);
        public bool IsAccepted(Interaction interaction)
            return interaction?.ChannelId == ChannelId;


The conditions are limited to filter by interaction data. You cannot create a condition based on the interaction facet data in Sitecore 10.2.

You must register the condition in the Cortex Processing Engine instance.

To register the condition:

  1. Open the configuration file /App_Data/Config/Sitecore/Processing/sc.XConnect.DataTools.Conditions.xml.

  2. Under the <Settings>/<Sitecore>/<Processing>/<Services> tag, register the new condition.

    For example:



You cannot get a list of all the registered conditions. After you extend processing with a custom condition, you must make a note of the ConditionId.