Introduction

iLearn isn’t a typical marketing automation client. The audience isn’t a list of prospects waiting to be nurtured — it’s an active community of teachers, students, school administrators, and parents who all need the right communication, at the right time, triggered by what’s actually happening inside the platform.

That’s a very different problem to solve. The success of every email, in-app notification, and follow-up depends on whether ActiveCampaign actually knows what each user has just done — a lesson completed, a class created, a renewal date approaching, a student inactive for ten days. Without that signal, marketing automation is just guesswork.

When Zilla came on, iLearn already had ActiveCampaign in place but it was working in a silo. The team was manually sending most lifecycle emails, the data flow between AC and the iLearn application was patchy, and the automations that did exist were firing on lists rather than on real user behavior.

The challenge

Three things had to be true for the system to be worth building:

1. ActiveCampaign needed real-time visibility into what was happening inside the iLearn app — sign-ups, logins, lessons completed, classes created, inactivity, renewals.
2. The lifecycle communications had to be specific to who the user was — a brand new teacher needs a very different message to a head of school three years in, even if they triggered the same event.
3. None of this could add operational load to iLearn’s small team. If the system needed a person to babysit it, it wouldn’t survive contact with a busy term.

The brief was effectively: build a marketing and lifecycle automation engine that runs the communication side of the business so the iLearn team can stay focused on the product, sales, and customer success — not the inbox.

The solution

Zilla designed and built the system in three layers.

1. A clean, two-way integration between ActiveCampaign and iLearn

We built the integration so that every meaningful event inside the iLearn application — a teacher signing up, a class being created, a lesson completed, a renewal approaching, an account going inactive — is mirrored into ActiveCampaign in near real time. Tags, custom fields, and lifecycle stage data flow from the app into AC, and engagement signals (opens, clicks, automation completions) flow back into the app where the iLearn team can see them on a user’s profile.

This was the foundation. Without it, none of the automations downstream would have worked.

2. A lifecycle automation framework, not a pile of campaigns

Rather than building one-off email sequences, Zilla mapped iLearn’s full user lifecycle and built automations against each stage:

• Onboarding — new teacher and new school flows that walk users through first-class setup, first-lesson creation, and parent invitations, with branching based on whether they’re moving or stuck.
• Activation — behavior-triggered nudges when a user signs up but hasn’t completed the steps that predict long-term retention.
• Engagement — ongoing best-practice emails, product updates and tips, segmented by role (teacher vs. admin vs. parent) and tenure.
• Re-engagement — automatic detection of inactive accounts with a structured win-back sequence, escalating to a human handoff for high-value schools.
• Renewal — automated renewal workflows starting [TBC: #] days out, with internal notifications for the iLearn team on accounts that need a personal touch.

Every flow is keyed off real signal from the iLearn application — not just “they’re on this list” but “they did this thing, this many days ago, and haven’t done that thing yet.”

3. Operational automations that took work off the team

The least glamorous layer was also the most valuable. Zilla built the internal-facing automations that turn ActiveCampaign into an operational tool, not just a marketing one:

• Automatic task creation and notifications to the iLearn team when an account hits a lifecycle moment that needs a human (large school onboarding, churn risk, renewal blocker)
• Automated handoffs between marketing, sales, and customer success based on user behavior
• Daily and weekly internal digests of the lifecycle metrics that actually matter

The result is a system that runs quietly in the background and only surfaces a human when a human is genuinely needed.

The results

The headline outcome is the one iLearn cares about most: they kept growing without growing the team. The lifecycle communication that would have required [TBC: estimated #] additional staff to manage manually is now handled by automation, with the existing team focused on product and customer success rather than on sending emails.

Specific outcomes:

• 100% of teacher and student lifecycle communications now fully automated
• 10 active automation flows running across the lifecycle
• 30% improvement in onboarding completion for new teachers
• 15% Boost in re-engagement of inactive accounts
• 100s of new schools onboarded with no additional headcount on the iLearn team

The system has become a quiet competitive advantage — the kind of operational infrastructure customers never see, but feel every time they get the right email at the right moment.

Want a system like this for your business?

If you’ve got strong product traction and a small team, and you’re feeling the pressure to hire just to keep up with the communications side of the business — that’s exactly the problem we solve.

Book a free ActiveCampaign health check →

We’ll review your setup, flag the issues most likely to bite you in the next six months, and leave you with a prioritized list of fixes — whether you end up working with us or not.