Braze for Meal Kit Subscriptions

Why Lifecycle Optimization Matters More for Meal Kits Than Most Subscriptions

Meal kit subscribers churn fast. Industry average churn runs between 70-80% annually, and most of that loss happens in the first 90 days. Your window to build a habit is narrow. The difference between a subscriber who stays 3 months and one who stays 18 months usually comes down to whether they cooked their first three boxes — not whether they loved the brand.

Braze gives you the infrastructure to close that gap. But the platform only works if you wire it correctly for how meal kit behavior actually unfolds: delivery cycles, skip patterns, recipe engagement, box customization, and the specific moment someone starts drifting.

This guide walks you through the exact setup — events, segments, canvases, and automations — built for meal kit operators specifically.

---

Events to Track in Braze

Your Braze setup lives or dies on the quality of your event tracking. These are the custom events that matter most for meal kits.

Subscription and Order Events

• `subscription_activated` — fires when a new subscriber completes their first checkout. Include properties: plan type, box size, dietary preference, promo code used.
• `box_customized` — fires when a subscriber selects or changes their weekly recipes. Track whether they customized or took the default.
• `box_skipped` — the most important churn signal in your stack. Track cumulative skips via a custom attribute alongside the event.
• `box_delivered` — confirmed delivery. Use this to trigger post-delivery engagement.
• `subscription_paused` and `subscription_cancelled` — track cancellation reason as an event property if your cancellation flow captures it.

Engagement Events

• `recipe_viewed` — tracks which recipe cards a subscriber opens in app or on web. Useful for personalization.
• `recipe_rated` — post-cook ratings signal satisfaction and inform future recommendations.
• `referral_shared` — tells you which subscribers are brand advocates before you think to ask.

Behavioral Attributes to Maintain

Beyond events, keep these custom attributes updated in Braze:

• `consecutive_skips` (integer)
• `lifetime_boxes_delivered` (integer)
• `days_since_last_customization` (integer, updated via connected content or nightly data sync)
• `preferred_protein` and `dietary_tags` (string/array)
• `acquisition_source` (string, set at signup, never overwritten)

---

Segments to Build

Good segmentation is what separates relevant messaging from noise. Build these segments as a foundation.

Lifecycle Stage Segments

1. New Subscribers (Days 0–14) — subscribed within 14 days AND `lifetime_boxes_delivered` is less than 2. This is your onboarding cohort.
2. Active Engaged — subscribed for 30+ days, zero skips in the last 4 weeks, has customized at least once.
3. Passive Subscribers — receiving boxes but never customizing, low recipe engagement. High default-box risk.
4. Skip-Risk — `consecutive_skips` is 1 or more. Urgency depends on where they are in their tenure.
5. Pause-State — paused but not cancelled. Separate from cancelled; winback strategy differs.
6. Lapsed/Cancelled — cancelled within 90 days. Your highest-conversion winback audience.

Value-Based Segments

• High-Value Loyalists — `lifetime_boxes_delivered` greater than 24 and no skips in last 8 weeks.
• Referral Candidates — high loyalty score, has rated at least 3 recipes 4 stars or above.

---

Canvases and Automations to Set Up

Canvas 1: New Subscriber Onboarding (Days 0–30)

This is your most important canvas. Structure it around three goals: first delivery, first customization, first recipe rating.

• Entry trigger: `subscription_activated`
• Day 0: Welcome message. Set expectations for first delivery date. Link directly to the customization flow — do not make them hunt for it.
• Day 2 (if not customized): Reminder push or SMS. "Your first box ships in X days. Here are this week's most popular recipes." Pull in dynamic content using Connected Content.
• Day 7 (post-delivery): Ask for a recipe rating. One tap, low friction. This interaction is more valuable than any discount you could offer — it creates investment.
• Day 14 (if `box_customized` is false): Educate on customization. Show them what they're missing with specific recipe examples.
• Day 30: If engaged (customized at least once, no skips), send a loyalty acknowledgment. If passive, trigger the passive subscriber nurture branch.

Canvas 2: Skip Prevention

Entry trigger: `box_skipped` fires

• Immediate (1–2 hours after skip): Acknowledge the skip, show next week's menu. Give them a reason to stay engaged with the upcoming options.
• Second skip (Action Path): If `consecutive_skips` reaches 2, escalate. Offer a box credit or a "try something different" prompt based on their `preferred_protein` attribute.
• Third skip: Route to a human-feeling message. Consider SMS for this touchpoint — it performs better than email when the relationship feels at risk.

Canvas 3: Pause-to-Reactivation

Subscribers who pause are telling you something. They're not done — they just need a reason and a moment.

• Entry trigger: `subscription_paused`
• Day 7: Light touchpoint. "We're saving your preferences." No pressure.
• Day 21: Show what's new — seasonal recipes, new proteins, menu updates since they paused.
• Day 45: Make a direct offer. A box credit or reduced price for their return box. Put a deadline on it — open-ended offers underperform.
• Day 60: Final message before exiting to lapsed segment.

Canvas 4: Winback (Post-Cancellation)

• Entry trigger: `subscription_cancelled`
• Day 3: Do not contact immediately. Let the decision breathe.
• Day 7: Soft return message. No discount yet — test messaging that focuses on what's new or what they achieved while a member.
• Day 21: Introduce an offer. First box free or heavily discounted tends to convert best in meal kit winback.
• Day 45: Final attempt. Make the offer clear, the CTA singular, and the message short.

---

Industry-Specific Challenges in Braze

Delivery timing variability. Your subscribers' delivery days differ. Build delivery-day-relative timing into your canvases using custom attributes, not calendar-fixed delays. A "how was your box?" message hitting someone two days before their delivery is a credibility problem.

High event volume. A mid-size meal kit operator with 50,000 active subscribers generates significant event volume. Monitor your Braze data point consumption carefully — tracking every recipe scroll is not worth the cost. Prioritize high-signal events.

Suppression logic. Braze's default frequency capping is not enough for this category. Build explicit suppression steps: do not send skip-prevention messages to subscribers who already reactivated their skip, do not send winback messages to anyone who is currently active.

Connected Content for personalization. Static recipe recommendations don't perform. Use Braze Connected Content to pull live menu data into your messages so recipe names, images, and availability are always current.

---

Frequently Asked Questions

What Braze channel should meal kit companies prioritize?

Email handles the volume. Push and SMS handle urgency. The highest-impact moments — second skip, post-cancellation day 7, delivery-day engagement — perform better with SMS or push because they're time-sensitive. Build your canvases to escalate channel intensity as the stakes increase.

How do we handle subscribers who skip frequently but never cancel?

Segment them separately as chronic skippers. These subscribers have lower lifetime value but they haven't left. Test message frequency reduction — over-messaging chronic skippers accelerates cancellation. A lighter cadence with higher-quality personalization often outperforms a high-frequency retention push.

Can Braze handle the weekly menu cycle that changes every week?

Yes, but you need to build the infrastructure. Use Connected Content to pull your weekly menu via API so that messages always reflect the current week's options. Hardcoded recipe names in message templates will break your trust the moment a menu updates and the message doesn't.

What's the single highest-ROI automation to build first?

Skip prevention. The `box_skipped` trigger into a two-step canvas that acknowledges the skip and shows next week's menu recovers a measurable percentage of would-be cancellations. It's fast to build, easy to measure, and directly tied to revenue retention. Build this before the onboarding canvas if you have to choose.