Broadcasts in Customer.io

Overview

Broadcasts in Customer.io are your one-to-many sends for moments that matter in a D2C calendar, like a product drop, a limited-time bundle, or a last-call sale. Unlike automated flows (cart recovery, post-purchase, winback), broadcasts are typically scheduled or sent on demand to a defined audience, then measured for immediate revenue impact.

A realistic use case is a skincare brand launching a new vitamin C serum and emailing “early access” to VIP customers, then widening the audience to past purchasers who browsed similar products in the last 30 days but have not bought in 90 days.

If you want broadcasts to feel less like “blasts” and more like revenue plays, Propel can help you tighten audience rules, offer logic, and measurement inside Customer.io, so you can move faster. If you want help pressure-testing your next send, book a strategy call.

How It Works

Broadcasts in Customer.io work by selecting a specific audience (usually a segment), choosing a message and channel (email, SMS, push), and sending immediately or scheduling for later.

In practice, you treat a broadcast like a controlled campaign: you define who qualifies, exclude people who should not get it (recent purchasers, recent unsubscribers, support issue customers), pick a send time strategy, then monitor performance and deliverability as it goes out. You can also reuse the same audience logic across multiple broadcasts so your promo calendar stays consistent.

For teams running weekly promos, the biggest unlock is operational consistency: stable segments, consistent exclusions, and a repeatable QA checklist before every send. That is where Customer.io broadcasts become a reliable revenue lever instead of a stressful scramble.

Step-by-Step Setup

Broadcasts in Customer.io are easiest to operationalize when you build the audience first, then build the message around what that audience actually needs to buy.

1. Create or confirm the segment you want to send to (for example, “Purchased 2+ times” or “Viewed product in last 14 days, no purchase in last 30 days”).
2. Define exclusions as separate segments you can reuse (recent purchasers, recent refunders, already bought the promoted SKU, suppressed or unengaged addresses).
3. Build the broadcast message using your preferred editor, and add personalization that matters (first name is optional, last purchased category, recommended products, discount eligibility).
4. Set the broadcast audience to your main segment, then apply exclusions to protect margin and customer experience.
5. Choose timing: send now for urgency (drop, restock), or schedule for a known high-performing window based on your brand’s purchase cycles.
6. Run pre-send QA: rendering, links, discount codes, UTM parameters, dynamic blocks, and suppression behavior.
7. Send a small internal test, then launch the broadcast.
8. Track performance: revenue, conversion rate, unsubscribe rate, spam complaints, and downstream impact (does it cannibalize full-price orders, does it pull forward repeat purchases).

When Should You Use This Feature

Broadcasts in Customer.io are best when you have a time-based reason to communicate and a clear commercial goal tied to a specific audience.

• Product drops and early access: Send to VIPs first (high LTV, high AOV), then expand to high-intent browsers who have not purchased recently.
• Back-in-stock and restocks at scale: When the restock is broad and you want a single coordinated push, not just item-level triggers.
• Promo calendar moments: Sitewide sale, bundle launch, free gift threshold, or shipping deadline reminders.
• Category discovery pushes: Launch a “new arrivals” edit to customers whose last purchase category matches the new assortment.
• Reactivation waves: A controlled winback broadcast to lapsed buyers, often paired with tighter exclusions to protect deliverability.

Operational Considerations

Broadcasts in Customer.io get messy when audience logic, data freshness, and promo operations are not aligned.

• Segmentation hygiene: Keep a small library of “core” segments (VIP, active buyers, lapsed buyers, high-intent browsers) and reuse them. Avoid rebuilding audiences from scratch every time.
• Data flow and timing: If Shopify events or warehouse syncs lag, your “recent purchaser” exclusion can miss people and cause immediate complaint risk. Build a buffer (for example, exclude purchases in last 2 to 24 hours depending on your sync speed).
• Offer eligibility logic: If a discount applies only to first-time buyers, do not send it to repeat purchasers. Create explicit eligibility segments to protect margin and trust.
• Channel coordination: If you also send SMS, decide whether SMS is a follow-up to non-clickers, a VIP-only channel, or a last-call reminder. Do not double-tap the same audience without a plan.
• Measurement beyond clicks: Track incremental revenue and downstream behavior. A broadcast that spikes revenue but increases refunds or unsubscribes can be a net negative.

Implementation Checklist

Broadcasts in Customer.io run smoother when every send follows the same pre-flight checklist.

• Audience segment defined and saved (not built ad hoc inside the send).
• Exclusion segments applied (recent purchasers, purchased promoted SKU, suppressed, customer service flags if available).
• UTM parameters consistent with your reporting model.
• Offer logic validated (codes active, thresholds correct, expiration correct).
• Dynamic content blocks tested for edge cases (no last purchase, no recommendations, out-of-stock).
• Deliverability checks (from name, subject line, spammy language, image-to-text balance).
• Send time confirmed (including time zone strategy if relevant).
• Post-send reporting plan (what “good” looks like for revenue, unsubscribes, complaints, and conversion).

Expert Implementation Tips

Broadcasts in Customer.io perform best when you treat them like segmented revenue moments, not calendar obligations.

• In retention programs we’ve implemented for D2C brands, the highest ROI change is usually exclusion discipline. Excluding purchasers of the promoted SKU and recent buyers often improves conversion rate and reduces unsubscribes, even if it lowers total sends.
• Build a “promo ladder” audience approach: VIP first, then high-intent non-buyers, then broader engaged list. You can run this as multiple broadcasts over 24 to 72 hours with different creative and urgency.
• Use purchase cycle timing to decide send day. For replenishable categories, align sends to expected refill windows (for example, 21 to 35 days post-purchase) and reserve broad promos for slower weeks.
• If you run frequent broadcasts, create a simple engagement gate (for example, clicked or purchased in last 90 to 180 days) to protect deliverability and keep your core list healthy.

Common Mistakes to Avoid

Broadcasts in Customer.io can quietly leak revenue when execution details are off.

• Sending promos to people who just purchased: This drives complaints and trains customers to wait for discounts.
• Overlapping broadcasts with automations: If a customer is in cart recovery or post-purchase cross-sell, decide which message wins and suppress the other.
• One-size-fits-all creative: A single message to first-time prospects and VIPs usually underperforms. At minimum, split by lifecycle stage.
• Measuring only opens and clicks: Revenue, contribution margin, refunds, and unsubscribe rate are the metrics that matter for broadcast decisions.
• Ignoring inventory reality: Promoting hero SKUs that are low stock creates a bad experience and pushes support load up.

Summary

Use broadcasts when you have a time-sensitive reason to reach a specific audience, like a drop, restock, or sale moment. Done well, broadcasts complement your automations and drive fast revenue without burning list health in Customer.io.

Implement with Propel

Propel helps teams set up scalable broadcast operations in Customer.io, including reusable segments, exclusions, and measurement that ties back to revenue. If you want a tighter, faster promo engine, book a strategy call.