Sending Direct Mail with Lob in Customer.io

Customer.io partner logo

Table of Contents

Summarize this documentation using AI

This banner was added using fs-inject

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Overview

Sending direct mail with Lob in Customer.io is a practical way to add an offline touchpoint when email and SMS are saturated, ignored, or suppressed, especially for high-intent moments like abandoned checkout or high-AOV replenishment. For D2C teams, it works best when you treat mail as a targeted escalation layer, not a blanket campaign.

If you want direct mail to behave like a performance channel (tight targeting, clean attribution, fast iteration), Propel can help you operationalize it inside Customer.io, align it with your email and SMS, and keep it profitable. If you want help pressure testing the use cases and build, book a strategy call.

How It Works

Sending direct mail with Lob in Customer.io works by using a workflow action that calls Lob to create and mail a piece (postcard or letter) based on the person and event data you pass in.

In practice, you set up a reusable webhook in Customer.io that hits Lob’s API. The workflow supplies the recipient address and the creative inputs (template ID, merge variables, or HTML), then Lob prints and mails it. You can also capture Lob’s response (like an ID) back into your data layer for tracking, suppression, or customer support visibility.

Think of it like this: your journey decides who qualifies and when, the webhook sends the order to Lob, and your reporting ties the mail drop to downstream conversion and repeat purchase.

Step-by-Step Setup

Sending direct mail with Lob in Customer.io is easiest when you start with data readiness, then build the webhook, then add journey logic that prevents waste.

  1. Confirm you have mailable address data in your customer profile. At minimum: first name, last name, address line 1, city, state, postal code, country. Decide where it lives (person attributes vs an “address” object) and standardize field names.
  2. Decide your first use case and trigger. Common starting points are “Checkout Started” with no purchase within X hours, or “Delivered” with no second order within X days for a replenishable product.
  3. Create a Lob account and generate an API key. Use a restricted key if possible and store it securely for your webhook configuration.
  4. Build your Lob template. Start with one postcard format. Keep the offer simple, include a short URL or QR code, and include a clear expiration window to create urgency and aid measurement.
  5. Configure a reusable webhook in Customer.io that calls Lob’s API. Set the endpoint to Lob’s “create” endpoint for the mail piece you’re sending. Add headers for authorization and content type.
  6. Map Customer.io fields into the Lob payload. Pass recipient address fields, template ID, and merge variables (like product name, cart value, discount code, or a personalized landing URL).
  7. Add the webhook action to your journey. Place it after your “wait” period and after a purchase check so you only mail people who still need the nudge.
  8. Write guardrails into the workflow. Add filters for country, address completeness, order value threshold, and customer status (for example, only mail first-time abandoners over $120).
  9. Optionally capture Lob’s response. Store the Lob mail piece ID on the person profile or in an event so support and analytics can reference it.
  10. QA with test recipients. Send to internal addresses first, validate merge fields, confirm print quality, and confirm the landing page experience matches the promise on the card.

When Should You Use This Feature

Sending direct mail with Lob in Customer.io tends to win when you use it selectively for high-value moments where an offline touchpoint changes behavior.

  • Abandoned checkout escalation for high-AOV carts: If email and SMS do not convert within 24 to 72 hours, a postcard can recover margin-rich orders without increasing paid media spend.
  • Winback for lapsed best customers: Target customers who used to buy every 30 to 45 days and have now gone dark for 90+ days. A physical mailer often cuts through inbox fatigue.
  • Post-purchase cross-sell for specific categories: For example, a skincare brand can mail a regimen card 10 days after delivery with a bounce-back offer for the complementary product.
  • Addressable audiences you cannot message digitally: Suppressed emails, unsubscribed SMS, or low deliverability segments still have postal reach if you have consent and policy coverage.

Realistic scenario: A premium coffee brand sees many first-time customers abandon at shipping. They run email and SMS for 48 hours, then mail a postcard only if cart value is over $60 and the customer is within the contiguous US. The postcard drives to a personalized landing page with the cart pre-loaded and a 10% code that expires in 7 days.

Operational Considerations

Sending direct mail with Lob in Customer.io becomes profitable or unprofitable based on data quality, tight segmentation, and how you orchestrate it with your other channels.

  • Address quality and formatting: Standardize country and state formats, and decide how you handle missing apartment numbers. In many D2C programs, a simple “address completeness” flag prevents the majority of failed sends.
  • Eligibility rules to protect margin: Set minimum cart value, minimum predicted LTV, or “VIP tier only” rules. Direct mail is not a volume play for most brands.
  • Frequency caps: Create a “last_direct_mail_sent_at” attribute and cap at 1 piece per 30 to 60 days per household unless you are running a very specific replenishment program.
  • Channel orchestration: Add a purchase check immediately before sending mail. Also suppress mail if the customer converted via email or SMS during the wait window.
  • Attribution: Use unique codes or short URLs per segment, not per person at first. Per-person codes can be powerful, but they add operational complexity and customer support edge cases.
  • International and compliance boundaries: If you ship globally, split by country and start with one region. Confirm your internal policy for marketing mail and required disclosures.

Implementation Checklist

Sending direct mail with Lob in Customer.io goes smoothly when you treat it like a channel launch, not a one-off workflow.

  • Postal address fields are standardized and reliably populated
  • Segment rules defined (AOV threshold, geo, customer status, suppression rules)
  • Lob templates created and reviewed (brand, offer, legal, QR or short URL)
  • Reusable webhook configured with secure authentication
  • Payload mapping validated for all required Lob fields
  • Journey includes wait window and a final “purchase happened?” check
  • Frequency cap attribute and logic implemented
  • Tracking plan defined (codes, URLs, events, and reporting cadence)
  • QA completed with internal test sends

Expert Implementation Tips

Sending direct mail with Lob in Customer.io performs best when you design it as an escalation layer with strict controls.

  • In retention programs we’ve implemented for D2C brands, direct mail works best when it is reserved for the top 10 to 20 percent of abandoners by cart value or predicted LTV. If you mail everyone, CAC quietly balloons.
  • Use timing that matches delivery reality. A postcard that arrives 10 days after an abandoned cart is usually dead on arrival. For cart recovery, prioritize faster formats and keep the wait window short so it lands while intent still exists.
  • Keep creative “operationally simple” for version one. One template, two offers max, and clean merge fields. Add complexity only after you have proof of lift.
  • Build a suppression rule for recent complaints or refund events. Mailing someone who just requested a return is an avoidable brand hit.

Common Mistakes to Avoid

Sending direct mail with Lob in Customer.io can look successful on paper while losing money if execution details are sloppy.

  • No final conversion check before mailing: People buy from email, then still get a postcard. That is pure waste and creates a disjointed experience.
  • Skipping frequency caps: Without a cap, VIPs can get hammered by multiple triggers (abandon, winback, post-purchase) in the same month.
  • Using direct mail for low-margin orders: If your margin cannot support print and postage, the program will never scale profitably.
  • Weak landing page experience: Sending to a generic homepage kills conversion. Use a dedicated page aligned to the mailer message, ideally with cart or product context.
  • Messy address data: Undeliverable mail is more than wasted spend. It also hides the real performance signal you need to optimize.

Summary

Use direct mail when you need a high-impact touchpoint for high-value customers and high-intent moments. When it’s orchestrated with email and SMS, it can lift first purchase conversion, repeat purchase, and winback without leaning harder on paid media inside Customer.io.

Implement with Propel

Propel helps D2C teams implement direct mail with Lob inside Customer.io, including segmentation, webhook setup, and measurement that ties back to revenue. To map the right use case and launch plan, book a strategy call.

Contact us

Get in touch

Our friendly team is always here to chat.

Here’s what we’ll dig into:

Where your lifecycle flows are underperforming and the revenue you’re missing

How AI-driven personalisation can move the needle on retention and LTV

Quick wins your team can action this quarter

Whether Propel AI is the right fit for your brand, stage, and stack