Objective
This article explains how to efficiently batch delete user profiles in Segment using the GDPR endpoint, including API limits, suppression best practices, and what to do if you need to process large volumes (e.g., 80,000+ users). If you need to remove sensitive event data from Engage or comply with privacy regulations like GDPR or CCPA, this guide will help you understand the process and avoid common pitfalls.
Product
Twilio Segment
Environment
Segment Console
User Account Permission/Role(s) Required
Workspace Owner or Admin permissions required to access the Privacy Portal and use the GDPR API.
Procedure
Export User Traits (Optional but Recommended):
Before deletion, export any user traits or data you may need to restore later.-
Batch Deletion Requests:
- Use the GDPR endpoint(Create Source Regulation) to submit deletion requests.
- You can delete up to 5,000 userIds per API call.
- For large batches (e.g., 80,000 users), split your requests into cohorts (e.g., 16 calls of 5,000 users each).
-
Suppression During Deletion:
- Use the SUPPRESS_WITH_DELETE regulationType option to prevent new events from being ingested for affected users during the deletion window.
- Any events sent during suppression will be permanently lost.
-
Unsuppress and Recreate Profiles:
- After deletion is confirmed (Segment’s SLA is up to 30 days), use the GDPR endpoint to unsuppress users by using the UNSUPPRESS regulationType.
- Recreate user profiles with an Identify call if needed.
-
Monitor API Limits:
- Segment enforces a monthly rolling limit of 110,000 user deletions per workspace.
- If you expect to exceed this, request a temporary limit increase via your Segment support contact.
Additional Information
- Deletion via the GDPR endpoint removes the entire user profile and all associated data from Engage and Unify; selective event or property deletion is not supported.
- For more details, see Segment’s Privacy and Data Deletion Documentation.