Operations & troubleshooting
Data retention and clearing
Choose a retention scope and distinguish deleting entities from clearing statistics.
Define the policy
Choose what history your operation needs for reporting, reconciliation and troubleshooting. Coordinate retention with your privacy obligations and storage capacity. Deleting detailed data can limit future investigations even if a summary remains.
Review the available controls
Inspect Clear actions and the automatic-clearing settings actually provided by your installation. Read the selected entity, time range and data type before confirming. Deleting a campaign, clearing its statistics and deleting hosted files are separate operations.
Prepare a change
- Identify the exact scope and oldest required data.
- Export records required for reconciliation.
- Confirm a recoverable backup when the data must remain restorable.
- Check shared campaign or offer dependencies.
- Review the tool's confirmation and execute only the intended scope.
Validate afterward
Inspect representative recent and retained records, then check disk usage. Database storage may not shrink immediately after logical deletion. Do not manually remove database volume files to force space reclamation.
Automatic clearing
Start with a deliberately chosen policy and review its effect before expanding it. A previous permission to clear test data is not a general permission to remove later production data. Keep a record of the policy, time and affected scope.