Updated in 2026.13
Description
This Node is used to delete a specific Contact Profile.
You configure this Node to keep analytics records in masked form with the Mask and Keep analytics feature instead of deleting all related analytics data. This setting is useful for keeping analytics on your AI Agent interactions while avoiding any personal traceability. Use this Node to comply with data protection standards, such as the General Data Protection Regulation (GDPR), when users request to delete their data.
If you delete the Contact Profile with this Node, all the Contact Profile data is deleted and is no longer available.
Restrictions
- Mask and keep analytics is available only for Cognigy.AI 2026.13.0 and later versions.
Parameters
| Parameter | Type | Description |
|---|
| Mask and keep analytics data | Boolean | Applies mask and keep analytics. With this option, data from the Contact Profile is processed as follows:- Replaces contact identifiers, such as contact and user ID, with hashes.
- Keeps analytics data, such as session counts and Intents, instead of deleting them.
- Clears free-text fields, such as input text and transcripts.
This parameter is deactivated by default. Masking is processed asynchronously and may take up to 2 hours to take effect. Masked sessions are excluded from the Conversations and Message explorers. However, analytics data related to the masked session is still included in Insights reports and can be accessed through the OData endpoint. |
Scope of Masking
When the Mask and keep analytics data parameter is activated, the following fields are affected:
| Collection | Hashed fields | Cleared fields |
|---|
| Analytics | contactId | ip, inputText, userLanguageText, ratingComment, foundSlots, foundSlotDetails, custom1–custom10, inputData, slots, geoInfo, slotMatches |
| Sessions | userId | — |
| Conversations | contactId | inputText, previousInputText, ratingComment, inputData, previousInputData, inputAttachments, previousInputAttachments |
| Goals, Live Agent Escalations | contactId | — |
| Steps | userId | — |
| Voice Gateway Events | userId | recognizerTranscript, recognizerDigits |
Use Case
Consider placing this Node below an If Node to trigger it when the contact explicitly requests not to collect their data.
