--- title: "Contact Removal Options" slug: "remove-contacts-from-groups-and-systems" updated: 2025-10-02T12:20:27Z published: 2025-10-02T12:20:27Z --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.mapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Contact Removal Options ## Overview Mapp Engage provides several ways to stop contacting users. Each option affects group membership, user data, and reporting differently. This page explains the available methods and when to use them. ### Options at a glance | Action | Impact on Data | Statistics Impact | Confirmation Sent | Reversible | Scope | | --- | --- | --- | --- | --- | --- | | **Unsubscribe** | Deletes group-specific data only | Counted in unsubscribe stats | Optional | Yes | One group | | **Remove** | Deletes group membership and data | Not counted as unsubscribe | No | Yes | One group | | **Delete** | Permanently deletes all profile and message data | Statistics retained, no new data | No | No | Entire system | --- ## Unsubscribing from a Group When a contact unsubscribes from a group, they stop receiving messages from that group, and their group-specific data is deleted. The action is recorded in the group’s unsubscribe statistics, and you can choose to send a confirmation message. Other group memberships are not affected. **Methods** - **Unsubscribe link**: Add a system variable or CMS template paragraph to every email. See [Add an Unsubscribe Link to an Email](/v1/docs/add-an-unsubscribe-link-to-an-email). - **List-Unsubscribe header**: Add an unsubscribe option to supported email clients in group sendout options. See [List-Unsubscribe Headers](/v1/docs/list-unsubscribe-headers). - **Keyword filters**: Automatically unsubscribe contacts when they reply with terms like “unsubscribe” or “do not contact.” See [Unsubscribe Contact Based on Keywords in Reply](/v1/docs/unsubscribe-contact-based-on-keywords-in-reply). - **Event-based Whiteboard**: Use the job [Add to / Remove from Group](/v1/docs/add-to-remove-from-group) in the Whiteboard automation to unsubscribe a contact from a group. - **Unsubscribe landing page**: Provide a custom page connected to one or more groups or the entire system. The landing page can be connected to one or more groups or used to manage unsubscribes for the whole system. Contact your account manager if you would like to develop a landing page for unsubscribes. - **API**: Use the `user` domain with the `unsubscribe` method. See the [API Documentation](https://docs.mapp.com/apidocs/membershipunsubscribe). **When to use:** Unsubscribing is best when a contact no longer wishes to receive messages from a particular group, but you still want to keep their profile and other memberships. --- ## Removing from a Group When a contact is removed from a group, their membership and related data are deleted, but the action is not recorded as an unsubscribe. The contact does not receive a confirmation, and any other group memberships remain unchanged. **Methods** - **File import**: Import a file with *Remove* mode to delete group-specific information (for example, member attributes). See [Remove Group Members with File Import](/v1/docs/remove-group-members-with-file-import). - **Event-based Whiteboard**: Use the job [Add to / Remove from Group](/v1/docs/add-to-remove-from-group) in the Whiteboard automation to remove a contact from a group. - **Manual removal**: Remove contacts in the *Group Members* window. See [Group Members: Overview](/v1/docs/group-members-tab). - **API**: Use the `membership` domain with the `delete` method to remove group membership. See the [API Documentation](https://docs.mapp.com/apidocs/membershipdelete). **When to use:** Removing is more appropriate when you are cleaning up membership lists without generating unsubscribe statistics. --- ## Deleting from the System When a contact is deleted from the system, all of their address data, profile data, and message history are permanently erased. The action cannot be reversed. Historical statistics remain available, but no new data is collected for the deleted contact. **Methods** - **Event-based Whiteboard**: Example: event [Email Response Received](/v1/docs/email-response-received) in combination with the**job [Delete Contact](/v1/docs/jobs-delete-contact). - **Manual deletion**: Delete contacts in the *All Contacts* window. See [Creating and Managing Contact Profiles in Mapp Engage](/v1/docs/creating-and-managing-contact-profiles-in-mapp-engage). - **API**: Use the `user` domain with the `delete` method. See the [API Documentation](https://docs.mapp.com/apidocs/userdelete). **When to use:** Deleting should be reserved for situations where a contact’s data must be completely erased from the system, such as for compliance reasons.