# Delete All Real-time Profile Data

Use **Delete All Real-time Profiles** to delete all real-time profile data for a Parent Segment's real-time configuration and start again from an empty state. Use it during a proof of concept or early implementation, when test data or misconfigured attributes have filled your profiles. In this page, this action is called a *reset*. A reset can't be undone, and earlier profile data can't be restored. Your source tables and real-time configuration aren't changed.

Beta
Delete All Real-time Profile Data is in beta. To get beta access, contact your account representative.

## Common Uses

- Deleting test data from a proof of concept (POC) or an early implementation
- Starting over after attributes were misconfigured
- Recovering from a broken profile state


## Before You Start

- **Permission:** You need the **MasterSegmentConfig** permission with **edit** access. To assign it, see [Policy Based Data Workbench Permissions](/products/control-panel/security/policies/policy-based-data-workbench-permissions).
- **No rollback:** A reset can't be undone. Earlier profile data can't be restored.
- **ID stitching:** If you load ID stitching data with a workflow, you must run that workflow again after the reset. See [After the reset](#after-the-reset).


## What a Reset Changes

After you confirm the reset, deletion runs in the background. The following data for the Parent Segment is deleted:

- Real-time profile attributes
- Batch attributes
- Internal profile data, including the real-time ID graph (identity links between profiles)


| Item | Effect of a reset |
|  --- | --- |
| Real-time profile count | Reset to 0. Counting starts again from the reset. |
| Journey state | Profiles that existed before the reset do not keep their journey state. |
| Real-time configuration (event tables, key events, attributes, ID stitching settings) | Unchanged |
| Parent Segment and Reactor instance | Unchanged |
| Your source tables | Unchanged |
| Log tables (ID changes, profile deletions, activation logs) | Kept. Earlier entries remain in the logs. Reset activity appears in customer-facing logs with a `data_version` field that identifies the data set each record belongs to. |


## Reset the Profiles

1. In **Data Workbench**, select **Parent Segments**, then select your Parent Segment. Select **Real-time Configuration**, and then select the **Administration** tab.
2. Under **Profile Settings**, click **Delete All Real-time Profiles**.
3. In the **Delete all Profiles data** dialog, type `DELETE` exactly as shown. The **Delete** button stays disabled until you do. If it stays disabled, check the spelling and capitalization of what you typed.
4. Click **Delete**.


A notification appears with the message "Profile data deletion has been initiated."

![Administration tab of a Parent Segment's real-time configuration showing the banner "Configuration is in progress.", the Profile Settings section with the Delete All Real-time Profiles button, and the notification "Profile data deletion has been initiated."](/assets/real-time-administration-delete-profiles.5ad35f8966eb1905e8abd789d03cedf310c6bc70618b6a730b8d2594f340bd11.5b2238d2.webp)

When the banner at the top of the **Administration** tab shows **Configuration launched successfully**, the reset configuration has been applied. Deletion runs in the background, and profiles are rebuilt as new data arrives. See [After the Reset](#after-the-reset) for the ID graph and batch attribute recovery steps.

If the banner shows **Oops! Something went wrong.**, the reset didn't complete. Click **Delete All Real-time Profiles** again. Retrying is safe, but there's no automatic retry, so you must run the reset again yourself. See [Check the Status](#check-the-status).

## Check the Status

The status banner at the top of the **Administration** tab shows the configuration status. It does not show the progress of background data deletion.

| Banner message | Meaning |
|  --- | --- |
| Configuration is in progress. | The reset is being applied. |
| Configuration launched successfully | The reset configuration has been applied. Deletion runs in the background. |
| Oops! Something went wrong. Please try again or contact your administrator for assistance. | The reset didn't complete. |


## After the Reset

- **Deletion runs in the background.** It starts after you confirm the reset.
- **Reload the ID graph manually.** The ID graph is not restored automatically. Re-run the workflow you use to upload ID stitching data. If you do not already have an upload workflow, you must create one.
- **Batch attributes are repopulated automatically.** They are repopulated by the next automatic batch run on the normal schedule. Batch processing also runs when the Parent Segment runs or the configuration changes.
- **Profiles are rebuilt as new data arrives.** Profiles that existed before the reset do not keep their journey state.
- **Customer-facing logs identify the data version.** Reset activity appears in the customer-facing logs. The `data_version` column identifies which data set each record belongs to. For example, `cdp_audience_<audience_id>_rt.activations` includes this column.
- **You can reset again.** Each reset starts a new data set and doesn't reuse earlier ones.


## Permissions and Safeguards

- Only users with MasterSegmentConfig edit permission see the **Administration** tab. The server checks the same permission on every request.
- You must type `DELETE` to confirm.
- Each reset is recorded in the audit log.


## Known Limitations

- **No rollback.** Earlier profile data can't be restored.
- **No automatic retry.** If a reset fails, run it again yourself.
- **No separate failure status.** A failed reset shows the general warning banner.