En esta página: configure y programe operaciones del ciclo vital de datos para que pueda mantener los registros precisos, utilizados según lo previsto y eliminados de acuerdo con las directivas de su organización.
A medida que los datos se incorporan continuamente en Adobe Experience Platform, resulta crucial garantizar que los datos se utilicen según lo previsto, que se actualicen cuando sea necesario y que se eliminen según las políticas organizativas.
Estas tareas se pueden realizar utilizando el menú Ciclo de vida de los datos, que le permite configurar y programar operaciones de ciclo de vida de datos, asegurándose de que los registros se mantengan correctamente.
Recomendaciones data-hygiene-recommendations
Al realizar operaciones de higiene de los datos (como eliminar identidades o conjuntos de datos), tenga en cuenta que los eventos de envío históricos asociados a identidades eliminadas ya no aparecen en los informes estándar ni en las consultas de lago de datos. Esto puede generar discrepancias entre el número de correos electrónicos notificados como Entregados y el número de correos electrónicos Recibidos en las bandejas de entrada de los destinatarios, especialmente para los recorridos más antiguos.
Antes de ejecutar eliminaciones a gran escala, valide y exporte los datos de envío o de creación de informes necesarios. Si es necesario realizar una reconciliación después de la higiene de los datos, coordínese con el servicio de asistencia de Adobe para acceder a los registros archivados o utilizar consultas del conjunto de datos de evento de comentarios sobre mensajes para los datos recientes.
Más información data-hygiene-learn-more
Para obtener más información sobre Privacy Service y cómo crear y administrar solicitudes de ciclo de vida de datos, consulte la siguiente documentación de Adobe Experience Platform:
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains how to configure and schedule data lifecycle operations in Journey Optimizer so you can keep your records accurate, used as intended, and deleted in line with your organizational policies.
Intents:
- Understand what data lifecycle operations accomplish
- Configure and schedule operations using the Data Lifecycle menu
- Understand the reporting impact of deleting identities or datasets
- Prepare for large-scale deletions by validating and exporting required data
- Know the availability requirements for data lifecycle capabilities
Glossary:
- Data lifecycle operations: operations configured and scheduled from the Data Lifecycle menu to keep records accurate, used as intended, and deleted per organizational policies (product-specific)
- Data hygiene operations: operations such as deleting identities or datasets (product-specific)
- Data Lifecycle: the menu used to configure and schedule data lifecycle operations (product-specific)
- Message Feedback Event Dataset: dataset that can be queried to access recent data if reconciliation is needed after data hygiene (product-specific)
Guardrails:
- Data lifecycle capabilities are currently only available for organizations that have purchased the Healthcare Shield and Privacy and Security Shield add-on offerings (availability constraint)
- After deleting identities, historical delivery events associated with deleted identities will no longer appear in standard reporting or datalake queries
- Deletions can result in discrepancies between the number of emails reported as Delivered and the number of emails Received in recipient inboxes, especially for older journeys
- Before executing large-scale deletions, validate and export any required delivery or reporting data (recommended)
Terminology:
- Canonical name: Data lifecycle operations — variants: data hygiene operations
- Do not confuse: “Delivered” (emails reported as delivered in standard reporting) ≠ “Received” (emails received in recipient inboxes)
FAQ:
- Q: Who can use data lifecycle capabilities? — Organizations that have purchased the Healthcare Shield and Privacy and Security Shield add-on offerings.
- Q: What happens to reporting after deleting identities? — Historical delivery events associated with deleted identities no longer appear in standard reporting or datalake queries.
- Q: What should you do before large-scale deletions? — Validate and export any required delivery or reporting data.
- Q: How can you reconcile data after data hygiene? — Coordinate with Adobe support to access archived logs, or use Message Feedback Event Dataset queries for recent data.