Two Campaign Closeouts Swapped Suppression and Archive Manifests: Reopen Both Closures
A crossed suppression or archive manifest makes a campaign closure untrustworthy. Reopen both records, reconcile each population, and block downstream reuse until negative-swap tests pass.
Research this article with AI
Follow Well Met on Google
A closeout is not complete because an archive file exists. It is complete when the archive and suppression set, plus the reporting cutoff and unresolved conversation ownership, all belong to the same campaign.
If Campaign A carries Campaign B's manifests and Campaign B carries Campaign A's, treat both closures as open. The immediate risk is operational: a later launch may screen against the wrong do-not-contact population. It may also inherit the wrong open threads or cite the wrong final numbers.
Freeze reuse of both manifest pairs first. Preserve the files and closure records as evidence, then create corrected versions instead of overwriting the crossed record.
- Pause any launch or import that references either disputed manifest, including suppression-screening work.
- Record the two campaign IDs and the detected swap, plus the person who found it and the timestamp.
- Keep the original files readable but mark them superseded after the corrected closure is approved.
Which records belong to each campaign closeout?
Build one reconciliation row per campaign. Start with the campaign ID and the intended cutoff. Then attach only records whose event time and campaign reference fit that closure.
Final disposition means the last known state of every contact included before the cutoff. Open-thread owner means the named person or queue responsible for any conversation that still needs a response. Do not turn an unassigned thread into a closed outcome.
Use separate fields for accepted links and observed links. An accepted link is a link the closure was allowed to use. An observed link is a link found in exports or messages, including downstream records. An observed link does not prove that it belonged in the campaign.
| Field | Campaign A closure | Campaign B closure |
|---|---|---|
| Campaign ID and cutoff | Record the intended campaign ID and final inclusion cutoff | Record the intended campaign ID and final inclusion cutoff |
| Final dispositions | Population and disposition export tied to Campaign A | Population and disposition export tied to Campaign B |
| Open-thread owners | Unresolved conversation IDs and current owner | Unresolved conversation IDs and current owner |
| Suppression manifest | Source export and hash, plus creation time and approved use | Source export and hash, plus creation time and approved use |
| Archive manifest | Export location and hash, plus contents and retention state | Export location and hash, plus contents and retention state |
| Links and reuse | Accepted and observed links, plus downstream references | Accepted and observed links, plus downstream references |
How should you rebuild the suppression manifests?
Create a fresh suppression candidate from the corrected campaign population, not from either crossed manifest. Keep the source query or export reference and the cutoff, plus the record count if your system stores one and a content hash.
A suppression manifest needs a purpose and scope. State whether it covers objections or opt-outs; bounced contacts or active customer exclusions; unresolved conversations; or another defined population. Do not merge categories just because they share a file.
The UK Information Commissioner's Office says organizations should keep a do-not-contact list for people or businesses that object or unsubscribe, and screen new marketing lists against it. Its guidance also says electronic-mail rules can apply to direct messages via social media. Apply the relevant legal and policy review for the campaign's jurisdiction and channel.
- Generate each campaign's candidate suppression set from its own source records.
- Compare every entry against the campaign ID and cutoff, together with the reason code.
- Hash the approved export and store the hash beside the corrected closure.
- Keep a separate exception list for records that need a human decision.
What should the archive export prove?
An archive export should make a later review possible without relying on memory. Include the campaign ID and cutoff; disposition population and open-thread ownership; suppression-manifest and archive-manifest hashes; accepted and observed links; reporting cutoff; and correction status.
Amazon S3 Inventory documentation describes inventory files as lists of objects and metadata, and says a manifest lists the inventory files stored in the destination bucket. That model is useful here: a manifest is an index with traceable metadata, not a claim that the indexed records were approved for another campaign.
If your archive uses versioned storage, retain the original crossed artifacts as evidence and point the corrected closure to new versions or new immutable objects according to your storage controls. Amazon S3 Object Lock documentation explains that retention and legal holds operate on individual object versions.
Which later launches relied on the crossed manifests?
Search downstream launch records, imports, screening jobs, reporting views, and handoff notes for both manifest hashes, file locations, campaign IDs, and any accepted or observed links. Start from the moment each crossed manifest was created and continue until the freeze began.
Classify each downstream use by effect: blocked before send, screened but not sent, sent after the wrong screen, reporting-only, or unknown. Unknown is a review state, not a clean result.
If a downstream action involved email, keep the channel separate from LinkedIn activity. Google's Gmail sender guidance applies to messages sent to personal Gmail accounts and includes sender requirements, along with authentication and unsubscribe requirements for the scope it describes. Do not present those requirements as LinkedIn measurements or LinkedIn rules.
- Find references to both manifest hashes and both campaign IDs.
- Identify the operator, job, launch, or report that used each reference.
- Record whether contacts were screened or actually contacted, or appeared only in reporting.
- Escalate any confirmed contact that should have been suppressed under the corrected campaign record.
How do negative-swap tests prove the correction?
A corrected closure needs a test that fails when Campaign A is paired with Campaign B's manifests, and the reverse. This catches the exact class of error that triggered the reopening.
Run the tests before releasing either corrected manifest for reuse. The expected result is simple: each campaign accepts its own campaign ID and cutoff; disposition population and thread-owner list; suppression and archive hashes; and approved links. It rejects the other campaign's values.
NIST's Guide to Computer Security Log Management describes the need for effective log-management processes across an organization. Keep the swap finding and evidence references, plus test output and approvals, along with correction timestamps, in the closeout record so another operator can recertify the closure.
- Positive test: Campaign A accepts Campaign A's full closure record.
- Negative-swap test: Campaign A rejects Campaign B's suppression and archive hashes.
- Positive test: Campaign B accepts Campaign B's full closure record.
- Negative-swap test: Campaign B rejects Campaign A's suppression and archive hashes.
- Release test: no downstream launch still points to a crossed manifest.
The ICO says organizations should keep a do-not-contact list for objections or unsubscribes and screen new marketing lists against it. Its guidance says electronic-mail rules can include direct messages via social media.
Information Commissioner's Office (accessed), 2026-10-23Google's sender guidelines describe requirements and guidance for messages sent to personal Gmail accounts, including authentication and unsubscribe requirements for the scope described.
Google (accessed), 2026-10-23Amazon S3 Inventory documentation describes inventory files as lists of objects and metadata, with manifest files listing inventory files in the destination bucket.
Amazon Web Services (accessed), 2026-10-23NIST SP 800-92 provides guidance on developing, implementing, and maintaining effective log-management practices.
National Institute of Standards and Technology, 2006-09-13Frequently asked questions
Should we overwrite the crossed manifests?
No. Preserve the crossed files and closure records as evidence, then create corrected manifests and mark the old pair superseded. Overwriting removes the trail needed to review downstream reuse.
What belongs in the final disposition population?
Include the contacts within that campaign's agreed cutoff and their last known campaign-relevant state. Keep unresolved conversations separate and name the current owner rather than calling them closed.
How do we know whether a later launch used the wrong manifest?
Search downstream records for both manifest hashes, file locations, campaign IDs, and linked export references, including launch records, import jobs, screening jobs, reports, and handoff notes. Mark uncertain findings as unknown until an operator resolves them.
Do email suppression rules apply directly to LinkedIn?
Do not assume that they do. The ICO guidance cited here says electronic-mail marketing rules can include direct messages via social media, but legal obligations depend on the applicable jurisdiction and facts. Google's Gmail guidance applies to email sent to personal Gmail accounts, not LinkedIn activity.
What is a negative-swap test?
It is a test that confirms Campaign A rejects Campaign B's suppression and archive manifests, and Campaign B rejects Campaign A's. It tests the failure mode that caused the closeout error.