Campaign operations · Practical guide
Campaign archive and retention: preserve the evidence before removing a campaign
Do not treat campaign deletion as a recoverable archive. Decide what must stop and what evidence must remain before using a removal action.
Reviewed · Examples are illustrative
Who this helps: Operators reviewing campaign retirement, rendering, threading and responsibility changes.
Define the decision
Zintara's current campaign deletion implementation issues a database delete for the campaign. It is not presented here as a soft-delete archive with a restore workflow. A retention decision also involves related conversations, suppression and reporting records, so inspect the actual dependencies rather than assuming everything is either preserved or erased.
Work through the procedure
- Identify the reason for retirement: stopping sends, reducing clutter or removing records under an approved policy.
- Review active enrollments, unresolved send attempts and outstanding replies before changing the campaign.
- Preserve necessary approved evidence in the team's appropriate record system and verify any export actually contains the required fields.
- Use the intended supported action only after understanding its scope and record the decision.
Worked example
The following is a synthetic example for this procedure, not a customer result or performance benchmark.
Retirement review
Goal: stop an old campaign while retaining its decision history
Open issue: one reply still needs an owner
Evidence needed: approved copy, audience definition and reporting cutoff
Action: resolve the reply and stop sending through supported controls
Do not assume Delete creates a restorable archive.Read the result
The review separates operational retirement from data removal. A paused or completed state may meet the immediate goal without resolving the organization's longer-term retention requirements. Conversely, preserving a screenshot alone may not retain the evidence needed to investigate a later suppression or reporting question.
Check before moving on
- Verify the effect on related records before deletion.
- Keep opt-out handling intact under the applicable policy.
- Do not promise restoration without a tested recovery path.
Limits and next action
This is an operational retention checklist, not a legal retention schedule. The deletion statement was checked against current code. Zintara does not promise a native recoverable campaign archive or universal export through this guide.
Source: Zintara product context; procedures and examples are editorial guidance
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Campaign preflight checklist: approve the first real send →
- Cold email campaign not sending: check eligibility before retrying →
- Hand off campaign ownership with settings, unresolved work and reply responsibility →