Applying Version Control to Campaign Audiences

Keep the approved campaign audience connected to the exact selection rules, exclusions and release used at launch.

Documents and work materials on a desk

Define the audience as a reproducible selection

Store the selection criteria, source system, query or filter version and snapshot time. Record exclusions and the relevant contact-permission rules applied by the authorized owner. A spreadsheet filename alone does not explain why a person belongs in the audience.

Keep personal data in the approved system with appropriate access. A review record can link to the controlled audience rather than duplicate the entire list. Identify who owns the selection and who may approve a release.

Compare changes before replacing an approved version

When the audience changes, compare additions, removals and the reason for each rule change. Reconcile the total count and investigate unexpected differences. A larger list is not automatically a better audience, especially if exclusions have stopped applying.

Distinguish a scheduled refresh using approved rules from a change to the rules themselves. Route material changes for review before activation. Retain the prior version and approval record so the team can reconstruct what changed.

Example: a launch date moves by one week

Illustrative case: an event invitation was approved on Monday, but the send moves to the following week. The team refreshes contact eligibility and applies the current suppression list. The audience owner checks the difference against the approved selection rather than reusing a stale export.

The release record identifies the final snapshot, approved channel and send date. If a new segment is added, it receives a separate review. A timing change should not silently expand the campaign’s audience.

Reconcile the released audience with the campaign

Before launch, confirm that the activation tool contains the intended version and exclusions. After launch, retain the release reference and delivery summary in the campaign record. Investigate discrepancies between the approved count and the actual activation.

If the wrong version is found, pause further activation where possible and involve the campaign and privacy owners. Record their decision and corrective action. Preserve the evidence needed to understand the incident without distributing unnecessary personal data.

Sources

  1. FTC CAN-SPAM Compliance, www.ftc.gov. Public guidance reviewed on 2026-10-12; applied only within its stated scope.

Related GTM guides

Frequently asked questions

What should an audience version record contain?

Record the selection rules, source snapshot, exclusions, release date and authorized approval. Link to the controlled audience rather than copying personal data into a widely shared record.

Does a refreshed list need another review?

Check the difference from the approved version. A refresh under unchanged approved rules differs from adding a segment or changing exclusions; material rule changes need the responsible owner’s review before activation.

How do you confirm the intended audience was used?

Match the activation tool’s release to the approved version, then reconcile the delivery summary. Investigate unexpected differences and preserve the release record.