Data Hygiene API
The Data Lifecycle UI is built on top of the Data Hygiene API, whose endpoints are available for you to use directly if you prefer to automate your data lifecycle activities. See the Data Hygiene API guide for more information.
Timelines and transparency
Record delete and dataset expiration requests each have their own processing timelines and provide transparency updates at key points in their respective workflows.
The following takes place when a dataset expiration request is created:
Stage | Time after scheduled expiration | Description |
---|---|---|
Request is submitted | 0 hours | A data steward or privacy analyst submits a request for a dataset to expire at a given time. The request is visible in the Data Lifecycle UI after it has been submitted, and remains in a pending status until the scheduled expiration time, after which the request will execute. |
Dataset is flagged for deletion | 0-2 hours | Once the request is executed, the dataset is flagged for deletion. If using Amazon Web Services (AWS) data storage, this process takes up to two hours. During this time, operations like batch and streaming segmentation, preview or estimate, export, and access disregard this dataset. |
Dataset is dropped | 3 hours | One hour after the dataset is flagged for deletion, it is fully removed from the system. At this point, the dataset is dropped from the dataset inventory page in the UI. However, the data within the data lake is only soft deleted at this stage and will remain so until the hard deletion process is completed. |
Profile count updated | 30 hours | Depending on the contents of the dataset being deleted, some profiles may be removed from the system if all of their component attributes are tied to that dataset. 30 hours after the dataset is deleted, any resulting changes in overall profile counts are reflected in dashboard widgets and other reports. |
Audiences updated | 48 hours | Once all affected profiles are updated, all related audiences are updated to reflect their new size. Depending on the dataset that was removed and the attributes that you are segmenting on, the size of each audience could increase or decrease as a result of the deletion. |
Journeys and destinations updated | 50 hours | Journeys, campaigns, and destinations are updated according to changes in related segments. |
Hard deletion complete | 15 days | All data related to the dataset is hard deleted from the data lake. The status of the data lifecycle job that deleted the dataset is updated to reflect this. |
Next steps
This document provided an overview of Platform’s Data Lifecycle capabilities. To get started making data hygiene requests in the UI, refer to the UI guide. To learn how to create Data Lifecycle jobs programmatically, refer to the Data Hygiene API guide
Experience Platform
Data Collaboration in Today’s Customer Experience Landscape
Reaching audiences where they are is harder than ever, with fewer signals, limited performance insights, and an ever-growing focus on...
Tue, Mar 18, 3:30 PM PDT (10:30 PM UTC)
Elevate and Empower Teams with Agentic AI for Exceptional Experiences
Elevate and empower your CX teams with AI that transforms creativity, personalization, and productivity. Discover how Adobe is...
Tue, Mar 18, 1:00 PM PDT (8:00 PM UTC)
Connect with Experience League at Summit!
Get front-row access to top sessions, hands-on activities, and networking—wherever you are!
Learn more