Deactivate Profile

Updated in 2026.14

Description

This Node deactivates a specific Contact Profile. By default, after the Contact Profile is deactivated, its data is kept and no new data is collected. You can configure this Node to delete all stored Contact Profile data or mask its personal data with the Mask and Keep Analytics feature. With this feature, you can keep only analytics data without any personal traceability. This approach is useful for tracking your AI Agents’ performance while complying with data protection standards, such as the General Data Protection Regulation (GDPR).

If you delete the Contact Profile with this Node, all the Contact Profile data is deleted and is no longer available.

Restrictions

The Mask and Keep Analytics feature is available only for Cognigy.AI 2026.14.0 and later versions.

Parameters

Parameter	Type	Description
Delete Data	Boolean	Deactivates the Contact Profile and deletes stored data, including all analytics data and transcripts, from the system. This parameter is deactivated by default. The Contact Profile isn’t deleted, and you can reactivate the Contact Profile using the Activate Profile Node or the Data collection inactive toggle.
Analytics data	List	This parameter appears when you activate Delete Data. Sets what data is deleted: Delete analytics records — deletes the Contact Profile data, including analytics and personal data. This option is selected by default. After the data is deleted, you can’t recover it. Keep analytics records, mask personal data — applies mask and keep analytics. With this option, data from the Contact Profile is processed as follows: Clears only free-text fields, such as input text and transcripts. Replaces contact identifiers, such as contact and user ID, with hashes. Keeps analytics data, such as session counts and Intents. 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.

Overview

AI Agents

Human Escalation

Platform Features

For Developers

Administration and Installation

Description

Restrictions

Parameters

Scope of Masking

Use Case

More Information

​Description

​Restrictions

​Parameters

​Scope of Masking

​Use Case

​More Information

Description

Restrictions

Parameters

Scope of Masking

Use Case

More Information