Profile Sync Schema Persists in Warehouse After Engage Space Deletion – Twilio Support

Issue

After deleting an Engage space, users may notice that the associated profile sync schema and tables (e.g., "profile_sync_unify_personas_v2") remain in their connected warehouse, and may continue to see data present even though no active warehouse connection is visible in the Segment Console.

Product

Twilio Segment

Environment

Segment Console

Cause

When an Engage space with Profile Sync enabled is deleted, the schema and tables created in the connected warehouse are not automatically removed. This can result in legacy data persisting in the warehouse, even after the Engage space and its profile sync configuration have been deleted.

Resolution

If you plan to enable Profile Sync again for a new Engage space, use a different schema name to avoid overwriting or appending to existing data in the warehouse.
To remove legacy data, manually drop the schema and tables from your warehouse if they are no longer needed.
Always verify which warehouse is connected to your Engage space in the Segment Console before enabling Profile Sync.

Additional Information

Enabling Profile Sync with the same schema name as a previously deleted Engage space may result in data being appended to or overwriting the existing schema. To prevent data loss or confusion, always use unique schema names for new Profile Sync configurations.