To make direct mail marketing measurable, choose the audience and mailing model first, assign the drop a stable campaign ID, then define the response you will track before printing. A neighborhood restaurant opening might use USPS Every Door Direct Mail (EDDM) and a route-specific offer code. A B2B renewal campaign might mail eligible companies through a documented provider integration and direct recipients to a HubSpot-tracked landing page.
Measurement can connect a mailing to later digital activity, but a mailed piece, a tracked visit, a conversion, and incremental campaign impact are different observations. A tracking link helps classify traffic. It does not prove delivery or show that the mail caused a purchase.
This guide focuses on the operating decisions behind a measurable campaign: selecting the targeting unit, defining event data, validating provider handoffs, and reporting results without overstating attribution.
What makes a direct-mail campaign measurable?
Direct mail marketing is the distribution of a physical communication or item to an audience. The audience may be defined by postal route, household, named person, company, or CRM eligibility rules. “Measurable” means the campaign has a defined identity, observable response events, and a documented reporting method.
Start with the decision the campaign needs to support. Use geographic targeting when the goal is local reach. Use named-recipient mail when eligibility depends on a person, account, lifecycle stage, or business event. Before production, settle the response event and reporting window. A QR scan, landing-page visit, form completion, and purchase are not interchangeable definitions of response.
For digital visits, HubSpot’s tracking URL documentation explains how campaign parameters classify traffic. The destination page needs HubSpot tracking code for HubSpot to record visits. The tracking URL helps report campaign traffic. It is not evidence that a piece was delivered or that mail caused a conversion.
Choose the mailing model: neighborhood reach or named recipients
USPS EDDM is a route-based option. Businesses select geographic areas rather than mailing to named individuals, and pieces are addressed to “Postal Customer.” USPS documents route selection and EDDM Retail conditions on its Every Door Direct Mail page. Confirm current route, quantity, size, preparation, and daily volume rules before production.
A CRM-connected campaign uses records and eligibility criteria to decide who should receive a piece. That can suit account-stage outreach or a renewal reminder, but the provider and CRM must support the required objects and event handling. Provider-specific capabilities vary by integration level, plan, and customer account.
| Model | Best-fit decision | Attribution approach |
|---|---|---|
| EDDM | Reach selected neighborhoods without naming recipients | Compare routes, offer codes, phone numbers, or destination variants |
| Named mail | Target eligible contacts or companies from CRM data | Associate a campaign or mailpiece ID with provider events and conversions |
A restaurant opening could select nearby EDDM routes and use a route-specific offer code. A B2B renewal campaign could select eligible companies in the CRM, assign a campaign ID to the drop, and use a landing page tailored to the offer. Route-level results cannot be interpreted as named-recipient engagement.
Design the response path before printing
For a digital response path, configure the campaign identity and destination before approving artwork:
- Create a stable
campaign_idfor the campaign drop and creative variant. - Choose one primary call to action and a landing page that matches the printed offer.
- Create a campaign tracking URL, then generate the QR code or print the short URL. Keep parameters through any redirects.
- Test the final destination on mobile and desktop. Submit the form or complete the intended action, then confirm that the visit and conversion appear in the selected analytics or CRM reporting.
For USPS Informed Delivery, the digital campaign is an additional operational setup, not simply a QR code in the artwork. USPS guidance describes eligible mailpiece and barcode requirements, campaign content, active dates, and an HTTPS destination related to the physical piece. Confirm current requirements with USPS or the mailing provider before committing the mailing. The USPS Informed Delivery campaign guide describes the process.
Keep USPS campaign exposure, physical-mail tracking, QR scans, landing-page visits, and conversions as separate event types. A campaign URL can identify traffic from a configured destination, but it cannot establish that a particular person received the physical mail.
A QR scan establishes a tracked interaction under your configured rules. It does not establish who received the physical piece or whether the mail caused the action. Report each event at the level your data can support.
Set up CRM and provider handoffs without losing event history
HubSpot documents tracking URLs, but sending a physical mailing requires a mail provider or a separate mailing process. Postalytics is listed in the HubSpot Marketplace and documents HubSpot integration options. Its supported objects, workflow features, and synchronized events vary by integration level, provider plan, and the customer’s HubSpot account. Review the current Postalytics integration overview and setup documentation before designing a workflow. Provider-specific fields are not standard HubSpot properties.
Define the data grain before connecting systems. One campaign record represents one drop or campaign version. One recipient or mailpiece record represents one intended piece. One event record represents one provider or response observation. A dated aggregate report is a separate record, not another event.
- Campaign: store the campaign ID, audience definition, creative version, planned quantity, send date, and approved budget.
- Recipient or mailpiece: store the CRM record ID and, where available, a stable provider or mailpiece ID associated with the campaign.
- Event: preserve each provider event with its event type, timestamp, and provider event ID when available. Do not overwrite a print or send event with a later delivery or pURL event. Maintain current status separately if needed.
- Conversion: store each qualifying conversion observation separately from provider delivery or response events, including the conversion timestamp and attribution rule.
- Aggregate: store reporting period, channel, attribution rule, and aggregation version with each summary.
If a custom data store processes concurrent events, enforce uniqueness with a database constraint and use a transactional upsert. A lookup followed by an insert can still create duplicates when two workers act at the same time. If no stable provider event ID exists, agree on a composite key only after confirming the provider’s event semantics. Do not assume that similar-looking events are duplicates.
Example operating patterns
The following patterns are proposed operating designs. They combine documented vendor capabilities with implementation controls that the campaign owner must configure and validate.
| Trigger | AI job | Validation | Action and fallback |
|---|---|---|---|
| CRM segment identifies eligible B2B renewal contacts | Optional classification of non-sensitive notes into an approved theme list | Check address fields, suppression, campaign eligibility, creative version, duplicate-send key, budget, and provider plan | Send through the selected provider. Quarantine incomplete or unmatched records for campaign operations review. |
| Planned route or audience variant needs a digital response path | None required. Use deterministic campaign parameters | Test HTTPS destination, HubSpot tracking code, redirects, QR behavior, form event, and visitor deduplication | Release artwork only after the destination and conversion event pass testing. Route broken links to web operations. |
| EDDM campaign needs neighborhood-level reporting | None required for route selection or mailpiece eligibility | Confirm current route, piece count, size, preparation rules, and route-specific offer code | Analyze responses by route or offer code. Do not attempt named-recipient attribution. |
For help defining CRM records and workflow readiness, see CRM systems consulting or HubSpot systems consulting.
Measure response, conversion, and incremental impact separately
Write a metric contract before launch. For every metric, state its numerator, denominator, time window, source, and deduplication rule. A practical starting set is pieces mailed, delivery-status events when available, unique tracked visitors, completed conversions, campaign cost, and attributed revenue.
- Response rate: define the chosen response event divided by the stated denominator. Unique tracked visitors divided by pieces mailed is one possible definition, not a universal standard.
- Conversion rate: completed conversions divided by the stated population, such as unique tracked visitors. Record the attribution window and how repeat conversions are handled.
- Cost per conversion: campaign cost divided by conversions counted under the agreed rule. Include more than postage in campaign cost.
- Attributed revenue: revenue assigned under a documented reporting rule. Attribution describes the rule used to assign credit. It does not establish causation.
Report QR scans separately from deduplicated visitors and form completions. If the denominator is pieces mailed, label it that way. Do not call the result a delivery-based rate unless actual delivery events support that denominator. USPS Informed Visibility offers commercial-mail tracking and reporting options, subject to access and provisioning. Availability of tracking data does not mean every piece has a directly attributable conversion.
To estimate incremental impact, use a control group when the campaign and audience allow it. Randomly assign eligible recipients to mail and no-mail groups, keep other conditions as comparable as practical, then compare conversion or revenue outcomes against cost. Record the sample, exclusions, reporting window, and attribution rule. This is a proposed measurement design, not a guarantee that differences are caused by mail.
Use automation and AI only where they have a bounded job
Use deterministic rules for address completeness, suppression, account status, eligibility dates, approved recipient segments, budget limits, and campaign dates. Those decisions have explicit inputs and should not be delegated to a language model.
AI may propose a message theme from non-sensitive account notes, but a person should review the proposal and a validator should enforce the send rules. The model should not infer address validity, override suppression, invent recipient facts, or authorize sending.
A proposed output contract might look like this. These are illustrative fields, not a HubSpot or Postalytics standard schema:
{
"campaign_id": "dm_renewal_q3_v1",
"record_id": "illustrative CRM record ID",
"proposed_theme": "renewal_planning",
"source_record_id": "illustrative note ID",
"review_status": "pending"
}Validate required fields, allowed theme values, source provenance, suppression status, campaign eligibility, duplicate-send rules, and approved creative version before sending anything to a provider. If the source note is unclear, the record is unmatched, or eligibility conflicts, route it to the campaign owner for review. Save the proposal and review decision separately so the final send decision is auditable.
Budget and launch checks
Build the estimate from data or list preparation, creative and design, printing, personalization, postage, provider charges, and measurement setup. The USPS Delivers postage calculator can help estimate postage. It is not a complete campaign budget. Provider prices depend on plan, format, postage class, quantity, and current terms. Check the live Postalytics pricing page if it is the selected provider, and authorize the full campaign cost rather than approving a postage estimate alone.
- Audience or routes are approved, and suppression rules have been applied where the mailing model supports them.
- Addresses or mailpiece eligibility have been checked for the chosen mailing model.
- Proof, offer, primary call to action, and destination page are approved.
- Campaign ID, destination URL, response event, attribution window, and deduplication rule are assigned and tested.
- Full campaign cost, including provider and operational charges, is within the authorized budget.
- A named owner is responsible for invalid addresses, unmatched records, provider rejections, and other exceptions.
Frequently asked questions
Can HubSpot alone send physical mail?
HubSpot documents tracking URLs, not a native physical-mail sending service. A mailing requires a provider or mailing process. The HubSpot Marketplace listing and Postalytics documentation describe a provider integration, but capabilities depend on the provider plan and HubSpot account. Verify current objects, events, and workflow support before promising a connection.
Does USPS Informed Delivery identify who opened or clicked?
USPS documents campaign content and reporting options, but those observations should not be treated as guaranteed person-level identity or proof of conversion. Keep digital campaign reporting distinct from physical-mail tracking and your own landing-page conversion data.
What counts as a direct-mail response?
The campaign owner defines it before launch. It could be a unique tracked visit, a completed form, a redeemed code, a qualified call, or a purchase. State the time window, denominator, source system, and whether repeat activity is deduplicated.
Does postal marketing require consent?
Requirements depend on jurisdiction, address source, profiling, sector, and campaign content. Postal marketing may be governed differently from electronic messaging, but lawful basis, transparency, opt-out, profiling, address sourcing, and sector-specific rules still require review. Check applicable requirements with qualified legal counsel rather than assuming one rule applies to every mailing.
A measurable campaign begins with a clear targeting unit and response definition, then preserves the events that connect the mailing to later activity. That gives the team a useful report without confusing tracked engagement with proof of delivery or causation.