Create a Campaign in Customer.io

Overview

Creating a campaign in Customer.io is how you turn shopper behavior (browse, add to cart, checkout started, purchased) into automated revenue flows that run every day. Think of campaigns as your always-on programs for first purchase conversion, cart recovery, post-purchase upsell, and reactivation, not one-off blasts.

If you want these programs to be measurable and easy to scale across seasons and product launches, Propel helps teams design the data, segmentation, and creative system behind Customer.io so campaigns drive incremental revenue, not just more sends. If you want help mapping the highest-leverage flows, book a strategy call.

How It Works

Creating a campaign in Customer.io starts with the keyword: create a campaign in Customer.io, which means defining who enters, when they enter, and what should happen next.

At a practical level, a campaign has four parts:

• Entry trigger: the event or segment that starts the journey (for D2C, usually events like Product Viewed, Added to Cart, Checkout Started, Purchased).
• Filters and frequency: rules that narrow entry (only high-intent shoppers) and prevent over-messaging (cap sends, avoid re-entering too often).
• Message sequence: email, SMS, push, or in-app steps with delays and branches (for example, “if purchased, exit” vs “if not purchased, send reminder”).
• Goals and conversion criteria: the action that defines success (Purchased, Order Completed, Subscription Created) so you can measure lift and stop messaging once the job is done.

Most D2C teams get the biggest gains when they treat campaigns as a system. Your triggers and goals should match your ecommerce event taxonomy, and your frequency rules should match how often shoppers realistically buy. If you are building this inside Customer.io, align your campaign goals to the same purchase event used in reporting, otherwise performance gets messy fast.

Step-by-Step Setup

To create a campaign in Customer.io that actually drives revenue, set it up in the same order you would debug it later: entry, eligibility, messaging, measurement.

1. Choose the campaign type and name it like a revenue program. Example: “Cart Abandonment, 2-step, high intent” or “Post-purchase cross-sell, 14 days”. Add tags for lifecycle stage (Prospect, First-time buyer, Repeat buyer).
2. Pick the entry trigger. Use an event trigger when possible. For cart recovery, trigger on Added to Cart or Checkout Started. For reactivation, trigger on a segment like “No purchase in 90 days” plus an event like “Email clicked” if you want a higher-intent re-entry.
3. Add filters to protect margin and relevance. Common D2C filters include: cart value over a threshold, exclude discounted orders, exclude customers who purchased in the last X days, exclude people already in a similar journey.
4. Set frequency and re-entry rules. Decide how often someone can re-enter (for example, once per 3 days for cart abandonment). Add message limits so a shopper who browses repeatedly does not get spammed.
5. Build the message sequence with clear exit logic. Add a delay, then send email or SMS. Add a condition: “Has Purchased since entering?” If yes, exit. If no, continue. Keep the decision points close to the purchase moment.
6. Define the goal and conversion criteria. Set the campaign goal to your purchase event (Order Completed). Add a time window that matches your buying cycle (cart recovery might be 24 to 72 hours, replenishment might be 14 to 45 days).
7. QA with real profiles. Check a few known customers and confirm: entry trigger fires, filters behave, and purchase exits the journey. Then run a small ramp before full volume.

When Should You Use This Feature

Create a campaign in Customer.io when you need a repeatable automation that turns shopper intent into revenue, with clear controls around who enters and when they stop receiving messages.

• Abandoned cart recovery: Trigger on Checkout Started, filter for cart value, send a 2 to 3 touch sequence, exit on purchase.
• Product discovery journeys: Trigger on Category Viewed or Product Viewed twice in 7 days, branch by category affinity, send education plus social proof, then a soft offer.
• First-to-second purchase: Trigger on Purchased (first order), wait until the product is likely delivered, then recommend complementary items based on the first SKU.
• Reactivation: Trigger when a customer hits 60 to 120 days without purchase, filter out recent returns or support issues, then run a winback series with escalating incentives.

Realistic scenario: a skincare brand sees high add-to-cart volume but low checkout completion on mobile. They create a campaign triggered by Checkout Started, filter for cart value over $50, send an SMS at 30 minutes, an email at 4 hours with ingredients and reviews, then a final SMS at 20 hours. The goal is Purchase, and anyone who buys exits immediately.

Operational Considerations

Create a campaign in Customer.io with the operational reality in mind, because the flow is only as good as the data and guardrails behind it.

• Event taxonomy consistency: Standardize events like Product Viewed, Added to Cart, Checkout Started, Purchased, and include key properties (SKU, category, price, quantity, cart value, discount code). Campaign logic depends on these fields.
• Identity and cross-device: Cart and browse behavior often starts anonymous and finishes identified. Make sure your identity stitching is reliable, or your cart recovery will miss high-intent shoppers.
• Segment overlap: Cart recovery, browse abandonment, and winback can collide. Use exclusions and message limits across campaigns to avoid stacking discounts and harming margin.
• Creative modularity: Build reusable blocks for product recommendations, reviews, and shipping promises. It speeds iteration and keeps brand consistency across flows.
• Measurement discipline: Tie goals to the same purchase event used by your analytics and ecommerce platform. Also decide whether you are optimizing for conversion rate, revenue per recipient, or contribution margin.

Implementation Checklist

Create a campaign in Customer.io using this checklist so you do not ship a flow that looks good but fails under real traffic.

• Entry trigger is event-based and includes required properties (cart value, SKU, category).
• Filters exclude recent purchasers, refunded orders (if relevant), and people already in similar journeys.
• Frequency and re-entry rules prevent rapid repeat entry from heavy browsers.
• Exit conditions remove people immediately after purchase.
• Goal is set to the correct purchase event with a realistic conversion window.
• Message limits are set at workspace or campaign level to prevent channel fatigue.
• UTM and attribution parameters are consistent across email and SMS.
• QA completed with at least 5 real profiles across devices and lifecycle stages.

Expert Implementation Tips

Create a campaign in Customer.io the way high-performing D2C teams do, by tightening intent signals and protecting margin.

• Start with “high intent” triggers, then expand. In retention programs we’ve implemented for D2C brands, Checkout Started outperforms Added to Cart for early wins because the shopper is closer to purchase. Once that is stable, add an Added to Cart version with stricter filters.
• Use dynamic branching to keep offers rare. In retention programs we’ve implemented for D2C brands, the best cart flows only introduce a discount on the final step and only for shoppers who meet conditions (new customer, high AOV potential, no prior discount usage). That keeps conversion strong without training customers to wait for promos.
• Align delays to your traffic pattern. If most purchases happen within 2 hours, your first reminder should land inside that window. Then use a longer gap before the last touch to avoid feeling aggressive.
• Make goals do the work. A clean goal and exit setup reduces unnecessary sends, improves deliverability, and keeps reporting honest.

Common Mistakes to Avoid

Create a campaign in Customer.io without these mistakes, because they quietly drain revenue and trust.

• Triggering on weak signals: a single page view often creates noise. Use repeated views, time on site, or add-to-cart thresholds.
• No purchase exit: customers keep getting “complete your order” messages after buying, which increases unsubscribes and support tickets.
• Overlapping discounts: multiple campaigns sending offers to the same person in the same week, leading to margin loss and promo dependency.
• Goals that do not match your real purchase event: reporting looks broken, and optimizations go in the wrong direction.
• Ignoring re-entry logic: a shopper can enter the same campaign repeatedly in a short session, especially on browse and cart triggers.

Summary

Create a campaign when you need an always-on automation tied to shopper behavior, with clear eligibility rules and a purchase goal.

Done well in Customer.io, campaigns become your highest-leverage revenue engine for cart recovery, repeat purchase, and reactivation.

Implement with Propel

Propel helps D2C teams build and optimize Customer.io campaigns that are grounded in clean data, tight segmentation, and measurable goals. book a strategy call.