Data retention data-retention

Standard log tables in Campaign have pre-set retention periods on them limiting their data storage duration, to avoid overloading your system.

Data retention configuration is set by Adobe technical administrators during implementation and values may vary for each implementation, based on customer requirements.

Reach out to the Adobe consultants or technical administrators to learn more about retention periods which apply to your environment, or to set custom retention periods.

Note that using standard workflow functionality, it is possible to set up retention periods for any custom table.

Below are the default retention periods for standard tables. Whenever possible, and depending on your data usage, Adobe suggests you to move to the recommended retention periods to improve performances of your Campaign instance.

  • Consolidated tracking: 6 months (recommended: 1 month)
  • Delivery logs: 6 months (recommended: 1 month)
  • Tracking logs: 6 months (recommended: 1 month)
  • Events: 1 month
  • Statistics of event processing: 6 months (recommended: 1 month)
  • Archived events: 6 months (recommended: 1 month)
  • Temporary entities: 7 days
  • Ignored pipeline events: 1 month
  • Delivery alerts: 1 month
  • Export audit: 6 months (recommended: 1 month)

Retention period for deliveries deliveries

By default, the retention period for deliveries is unlimited.

However, if there is a high volume of deliveries on your instance, you can update the NmsCleanup_DeliveryPurgeDelay option available from the Administration > Application settings menu.

Each time the Database cleanup workflow is run, the deliveries meeting the conditions set for this option will be deleted.

This action can help speeding up processes such as the Copy headers from delivery templates workflow.

Learn more on technical workflows in this section.

The default value for the NmsCleanup_DeliveryPurgeDelay option is -1. In this case, no delivery is deleted.

For example, if you set it to 180, any non-template deliveries that have not been updated in the last 180 days will be deleted when the Database cleanup workflow is run.

  • Marketing or transactional delivery templates will not be deleted.

  • For recurring deliveries, child deliveries with aggregation period set as month or year will not be deleted.

When updating the NmsCleanup_DeliveryPurgeDelay option, it is recommended to proceed gradually with multiple iterations. For example, you can start by setting the value to 300 days, then 180 days, then 120 days, and so on - making sure iterations are at least 2 days apart. Otherwise, the Database cleanup workflow may take much longer because of a large number of deliveries to delete.