What is a campaign ID in direct mail?

A practical guide to campaign IDs, batch IDs, source records, proof versions, mailstream tracking fields, response sources, and reviewable audit records.

What is a campaign ID in direct mail?

A campaign ID in direct mail is the internal identifier for a mailing effort. It connects the audience, creative, proof, batch, tracking, and review records that belong to the same campaign.

The ID can be simple, such as `winback-2026-06-23`, or generated by the system that owns the campaign. What matters is consistency. If the audience file, proof version, batch release, tracking fields, and response review all use different names, operators lose the thread that ties the mailing together.

When should the campaign ID be created?

Create the campaign ID before audience records are selected, proofs are approved, or batches are released. The ID should travel with each downstream record so later review can connect the original intent to the final send file.

Creating the ID late usually creates drift. A batch may be approved under one name, a proof may use another, and response exports may use a third. A durable ID gives the team one stable key across list import, design review, approval, batching, tracking, and measurement.

Operator rule: the campaign ID should be created before release, not reconstructed after someone asks for reporting.

Which records should include the campaign ID?

The campaign ID should appear on every record needed to explain what mailed, why it mailed, what version was approved, how it was grouped, and how later signals should be reviewed.

Record	Why it needs the campaign ID	Common companion fields
Source record	Shows which lead, customer, order, property, or event qualified for the campaign.	Source system, source record ID, event time, recipient key.
Audience version	Preserves the exact group that was eligible at a point in time.	Audience ID, selection rule, suppression run, count.
Creative proof	Connects approved copy and layout to the campaign that used it.	Template ID, proof version, approver, approval timestamp.
Mail batch	Connects a specific release of approved records back to the broader campaign.	Batch ID, approved count, held count, release timestamp.
Tracking record	Connects mailstream fields to the campaign and batch being reviewed.	Batch ID, barcode or tracking field, scan source, status timestamp.
Response review	Connects calls, forms, orders, or other response sources to the campaign window.	Response source, response time, match key, review window.

How is a campaign ID different from a mail batch ID?

A campaign ID identifies the broader mailing effort. A mail batch ID identifies one approved release of mail records. One campaign can have multiple batches, and every batch should still point back to the campaign ID.

ID type	Scope	Example use
Campaign ID	The mailing effort or program being measured.	Group all records for a June win-back mailing.
Batch ID	One approved release of mail records.	Separate Monday and Wednesday releases under the same campaign.
Source record ID	The original record that qualified for the mailing.	Trace a postcard back to a lead, order, customer, or property.
Recipient key	The person, address, household, or entity being mailed.	Deduplicate records and review suppression decisions.

For the batch-level workflow, see the mail batch guide. For upstream lineage and release evidence, see the direct mail audit trail guide.

How does the campaign ID connect to USPS tracking fields?

The campaign ID should sit beside USPS mailstream identifiers and tracking fields, not replace them. USPS Intelligent Mail barcode and Informed Visibility resources describe postal visibility systems, while the campaign ID tells the operator which mailing effort the record belongs to.

Keep the distinction clean. Postal identifiers help with mailstream visibility when the setup supports it. The campaign ID helps your system join that visibility back to the audience, proof, batch, and measurement records. One is not a substitute for the other.

How should campaign IDs support measurement?

Campaign IDs support measurement by giving every response review one stable join key. They should connect mailed records, response sources, match keys, holdout groups, and declared measurement windows without implying causality by themselves.

For measurement work, the ID should be stored with the audience snapshot, mail batch, response source, start rule, end rule, and any holdout assignment. A campaign ID can make reporting possible, but it cannot prove that a specific mailpiece caused a response. For that boundary, see the direct mail attribution guide.

What mistakes create campaign ID drift?

Campaign ID drift happens when operators rename campaigns, rebuild audiences, split batches, or export responses without preserving the original ID. The fix is to treat the campaign ID as immutable once records start moving downstream.

Drift pattern	What breaks	Control
Renaming mid-campaign	Proof, batch, and response records no longer line up.	Keep display labels editable, but keep the ID stable.
Reusing an old ID	New and old campaign records mix together.	Create a new ID for each distinct mailing effort.
Missing ID in exports	Responses must be matched by fuzzy names or dates.	Include campaign ID in every export and downstream review file.
Batch-only reporting	Multi-batch campaigns look like unrelated mailings.	Store campaign ID and batch ID together.
Source-system overwrite	Corrected records lose the original campaign context.	Save source record ID, campaign ID, and final mailed values.

What should a campaign ID not prove?

A campaign ID should not prove that a piece arrived, that a recipient saw it, that a response happened, or that revenue came from the mailing. It is a record-joining control, not outcome evidence.

Keep campaign IDs connected to measurement, but do not let the ID carry more meaning than it can support. The measurement record still needs source evidence, response timing, review windows, and a clear rule for which responses are in scope.

What should a Sendvo-style workflow keep visible?

A Sendvo-style workflow should keep campaign IDs visible beside audience rules, source records, proof versions, batch IDs, suppression results, tracking fields, response sources, and measurement windows before the campaign is reviewed.

Sendvo is in beta, so product language should stay capability-framed. The operational pattern is stable: when teams connect audience data, postcard design, triggered sends, and USPS tracking, campaign IDs help preserve the connection between what qualified, what was approved, what moved forward, and what gets reviewed later.

FAQ

What is a campaign ID in direct mail?

A campaign ID in direct mail is an internal identifier that connects one mailing effort across audience records, creative versions, proof approvals, batch files, tracking fields, response sources, and review records. It helps operators join records later without treating tracking or response data as outcome proof by itself.

Is a campaign ID the same as a mail batch ID?

No. A campaign ID identifies the broader mailing effort. A mail batch ID identifies a specific approved release of mail records. One campaign can have multiple batches, and each batch should still point back to the campaign ID for reporting and review.

What should a direct mail campaign ID not prove?

A campaign ID should not prove that a piece arrived, that a recipient saw it, that a response happened, or that revenue came from the mailing. It is a join key for records; measurement still needs source data, declared windows, response evidence, and review logic.

What is a campaign ID in direct mail?

TL;DR