Iterable for EdTech

Why Iterable Is a Strong Fit for EdTech Lifecycle Marketing

EdTech has a lifecycle problem that most generic CRM tools can't solve. Your users don't just churn — they disengage in predictable patterns: after the first hard lesson, after the free trial expires, after summer break, after a job change. Iterable's cross-channel orchestration gives you the infrastructure to catch those moments and respond with precision.

This guide covers exactly how to configure Iterable for an EdTech product — from the events worth tracking on day one to the automations that drive course completions and paid conversions.

---

The Events You Need to Track First

Most EdTech teams instrument too little early and too much too late. Start with the events that signal learning momentum — and the events that signal its absence.

Core Engagement Events

These are the non-negotiables to pass into Iterable via your CDP or direct API:

• `lesson_started` — with properties: `course_id`, `lesson_id`, `lesson_number`, `content_type`
• `lesson_completed` — with `time_on_lesson`, `pass_fail` (for assessments), `streak_day`
• `course_enrolled` — with `enrollment_source` (organic, email, push)
• `course_completed` — with `total_time_spent`, `certificate_earned`
• `quiz_attempted` and `quiz_failed` — track failure separately; it's one of your strongest re-engagement triggers
• `streak_broken` — if your product uses streaks, this single event drives some of the highest-ROI automations in EdTech
• `skill_path_started` — for platforms with structured learning paths

Conversion and Monetization Events

• `trial_started` — with `plan_type` and `trial_length`
• `paywall_hit` — captures intent to upgrade before it happens
• `subscription_started`, `subscription_cancelled`, `subscription_paused`
• `certificate_purchased` or `upgrade_to_unlock` for content-gated products

The Event Most Teams Miss

Track `last_active_date` as a user profile field, updated on every session. Iterable's segmentation works best when recency is baked into the user record, not calculated on the fly from event history.

---

Segments That Actually Drive Decisions

Iterable's segmentation is where your event data becomes actionable. Build these segments before you build any automation.

Engagement Tier Segments

Define three tiers based on lesson completions in the last 14 days:

1. Power Learners — 5+ lessons completed in 14 days
2. Casual Learners — 1–4 lessons completed in 14 days
3. At-Risk Learners — 0 lessons completed, active account, last session 8–30 days ago

Treat Power Learners as your referral and upsell pool. Treat At-Risk Learners as your re-engagement priority.

Lifecycle Stage Segments

• New Enrollees — enrolled in any course within the last 7 days
• Trial Users — on a free trial with 3 or fewer days remaining
• Churned Free Users — no login in 30+ days, never converted
• Lapsed Paid Users — cancelled subscription, previously completed at least one course

Behavioral Cohorts Worth Building

• Users who hit a paywall in the last 48 hours — your hottest conversion audience
• Users who completed a course but haven't enrolled in the next one — the post-completion drop is real and underserved
• Users who failed a quiz 2+ times on the same lesson — frustration is a churn signal, and a support opportunity

---

The Automations That Move the Needle

Iterable's Journey builder is where these segments become revenue. These are the workflows EdTech teams should build first.

1. The Onboarding Journey (Days 0–7)

This is your most important automation. Most EdTech churn happens in the first week.

Trigger: `course_enrolled`

Structure it around milestones, not time:

• Send the first message when the user completes lesson 1 — not on day 1
• Send the second message when they complete lesson 3 or hit 48 hours of inactivity (whichever comes first)
• Fork the journey at day 5: users who have completed 3+ lessons go to an upsell branch, users with 0–2 completions go to a re-engagement branch

Push notifications and email should work together here. Use email for progress summaries. Use push for in-the-moment nudges when a streak is at risk.

2. The Streak Recovery Automation

Trigger: `streak_broken`

This is a 24-hour window. After that, recovery rates drop sharply.

• Hour 1: Push notification with the specific streak number ("Your 12-day streak ended yesterday")
• Hour 6: SMS for users who have opted in — SMS outperforms email significantly in time-sensitive re-engagement
• Hour 20: Email with a soft re-entry offer (bonus content, not necessarily a discount)

3. Trial Conversion Journey

Trigger: `trial_started` — exit trigger: `subscription_started`

• Day 1: Welcome + what's available in the full product
• Day 4: Social proof message — completion rates, certifications earned by paid users
• Day 6 (48 hours before expiry): Direct conversion ask with your strongest value statement
• Day 7 (expiry): Last-chance message — this is where a time-limited offer performs best if your model supports it

4. Post-Completion Re-Enrollment

Trigger: `course_completed` + no `course_enrolled` event in 72 hours

Most platforms ignore the user the moment they finish. That's a mistake. A completed learner is your warmest audience for cross-sell and path continuation. Send a single, specific recommendation — not a catalog. "Based on completing Python Basics, here's what Power Learners take next" outperforms a generic "browse more courses" message every time.

---

EdTech-Specific Challenges in Iterable

Handling Seasonal Disengagement

EdTech usage drops in summer and around major holidays. If you suppress re-engagement automations based on standard inactivity thresholds, you'll fire too aggressively on users who are simply on a break. Build a seasonal suppression segment — users whose historical data shows annual low-activity periods — and pause aggressive outreach for those users between June 15 and August 31.

B2C vs. B2B2C Complexity

If you sell direct to consumers and through institutions, your Iterable setup needs to account for both. Use custom user fields like `account_type: individual | institutional` and build separate journey branches. Institutional users often can't receive certain promotional messages due to procurement rules — and sending them a discount offer undermines your enterprise relationship.

Mobile-Heavy Learners

Many EdTech users engage exclusively on mobile. If push notification opt-in rates are low, your email-only journeys will underperform. Build a push opt-in prompt journey triggered after the second lesson completion — that's the moment users have enough context to say yes to notifications.

---

Frequently Asked Questions

What's the best way to connect my EdTech product data to Iterable?

The most reliable approach is routing your event data through a CDP like Segment or RudderStack before it hits Iterable. This gives you a clean, validated event schema and makes it easier to update your tracking without redeploying Iterable-specific code. If you're early-stage and building direct API integrations, invest time in your event naming conventions upfront — renaming events after automations are live is painful.

How do I avoid over-messaging learners who are already engaged?

Build a frequency cap segment in Iterable that filters out users who have received more than 3 messages in a 7-day window, and apply it as a suppression list across all non-transactional journeys. Engaged Power Learners don't need re-engagement emails — sending them anyway trains your audience to ignore you.

Should I use Iterable for in-app messaging in my EdTech product?

Iterable's in-app messaging channel works well for triggered contextual messages — quiz encouragement, milestone celebrations, upgrade prompts. It's less suited for persistent UI elements like tooltips or feature walkthroughs. For those, pair Iterable with a dedicated in-app guidance tool and use Iterable to handle the campaign logic that sits outside the product session.

How do I measure whether my lifecycle automations are actually improving learning outcomes?

Set up conversion goals in Iterable tied to `lesson_completed` and `course_completed` events, not just email opens. Completion rate by cohort — users who received an automation versus those who didn't — is your north star metric. Open rates tell you if your subject lines work. Completion rates tell you if your lifecycle program works.