Why active customers still churn (and what to measure instead)

Tracking logins without tracking outcomes is like measuring how often someone opens the fridge without asking if they ever ate dinner.

If you're running account management or customer success, you've probably built some version of a customer health model. You're tracking logins, feature usage, maybe NPS, support tickets. You've aggregated these signals into dashboards and scores. And you've probably noticed something frustrating: your data tells you customers are engaged, but it doesn't tell you if they're actually getting value.

A customer who logs in five times a week might be stuck, spinning their wheels on a setup process that's going nowhere. A customer who logs in once might have everything dialed in and be getting exactly what they need. The activity is there, but the signal is noise. You can't tell who's succeeding and who's just busy.

The activity trap

Most platforms treat all customer activity the same way. They count it and score it, but they don't distinguish between activity that matters and activity that just exists.

This creates a fundamental problem. Your CSMs end up chasing engagement metrics that look good on paper but don't actually correlate with success. High login counts become a proxy for health, even when those logins represent frustration rather than value. Low login counts trigger concern, even when they might indicate a customer who's found their groove and doesn't need to tinker.

The underlying assumption is that more activity equals more success. But activity and progress aren't the same thing. A customer can be very active and completely stuck. A customer can be minimally active and perfectly on track.

When you can't distinguish between these scenarios, you end up with a team that's reacting to metrics rather than responding to reality. You're measuring the fridge door, not the dinner.

Separating what matters from what exists

Trig approaches this differently by separating customer activity into two distinct categories: objectives and markers.

Objectives are milestones. They're the specific things you need customers to do to succeed. Each objective represents a checkpoint, something the customer either has or hasn't done. These are the actions that indicate real forward momentum.

Examples of objectives:

• Created first project
• Invited a team member
• Connected a payment gateway
• Generated first report
• Completed a full week of usage

Markers are signals of healthy behaviour along the way. They're patterns, ongoing behaviours that correlate with success over time.

Examples of markers:

• Logged in more than three times this week
• Session duration greater than ten minutes
• Returned within twenty-four hours
• Saved a report
• Explored a new feature

Both matter, but they answer different questions.

Objectives define the destination. They tell you whether a customer has reached the critical checkpoints that predict long-term success. When a customer completes an objective, Trig records when it happened, how long it took from stage entry, and how that compares to the average. This builds a picture of progress that's grounded in concrete achievements rather than abstract activity.

Markers indicate the quality of the journey. They tell you whether the customer is exhibiting the behaviours that healthy customers tend to exhibit. A customer might not have completed their next objective yet, but if their markers look strong, you have confidence they're moving in the right direction. Conversely, a customer might have technically completed an objective, but if their markers are weak, you might want to check in.

Building a picture of normal

One of the most valuable things this separation enables is the ability to understand what "normal" looks like for your customers.

As customers progress through their journey and complete objectives, Trig automatically calculates benchmarks:

• Average time to complete each objective — How long does the typical customer take?
• Completion rates — What percentage of customers complete each objective?
• Completion sequence — In what order do customers typically complete objectives?

With 50 or more customers through a stage, these averages become meaningful. With 200 or more, they become statistically significant. This baseline builds automatically as data accumulates. You don't have to guess what good looks like or rely on intuition about which customers are on track. The data tells you.

Once normal is established, every customer is measured against it. Customers completing objectives faster than average are often your strongest accounts, correlating with higher retention and expansion potential. Customers taking longer than average may be experiencing friction or disengagement, signalling an opportunity to intervene before problems compound.

This is fundamentally different from tracking raw activity. The question shifts from "how active is this customer?" to "how is this customer progressing relative to customers who succeeded?"

From counting activity to measuring progress

Consider what this looks like in practice.

A traditional activity-based approach might show you that Customer A has logged in 47 times this month and Customer B has logged in 12 times. Based on that data, Customer A looks healthier. But you have no idea what either customer actually accomplished during those sessions.

With objectives and markers, the picture becomes clearer:

Customer A: Logged in frequently but hasn't completed the integration objective that 80% of successful customers complete by week two. Now in week four. Session durations are short, suggesting they're bouncing off something.

Customer B: Logged in less frequently but has completed all onboarding objectives ahead of schedule. Markers show consistent weekly engagement with core features.

Customer B is on track. Customer A needs attention. The login count told you the opposite.

Knowing exactly where customers get stuck

Because objectives represent specific milestones, you can pinpoint exactly where customers fall behind. Trig tracks completion rates and timing for each objective, so you can see patterns across your customer base.

Maybe 90% of customers complete the "created first project" objective within the first week, but only 60% complete the "connected integration" objective. That gap tells you something important. The integration step is where customers struggle. You can focus your enablement resources there, improve your documentation, or build automated interventions specifically targeting customers who've stalled at that point.

This level of specificity is impossible when you're just tracking aggregate activity. You know something is wrong when engagement drops, but you don't know what. With objectives, you know exactly which milestone a customer hasn't hit, how far behind they are relative to the average, and where they stand compared to everyone else.

When a customer falls behind on any objective, Trig surfaces this through Signals, alerting your team with the specific context they need: which objective, how many customers are affected, how much revenue is at risk, and how far behind they are relative to the benchmark. The intervention can be precise because the diagnosis is precise.

Why markers still matter

Objectives alone don't tell the whole story. A customer could complete all their onboarding objectives but then go dark. A customer could be one objective away from completion but showing all the signs of healthy engagement.

Markers fill in these gaps. They're the ongoing behaviours that indicate whether a customer is building the habits that lead to long-term success. Returning within 24 hours. Exploring new features. Engaging consistently week over week.

Think of markers as leading indicators and objectives as lagging indicators. Markers tell you how the journey is going. Objectives tell you whether customers reached the destination. You need both to understand the full picture.

A customer with strong markers but incomplete objectives probably just needs a nudge. A customer with weak markers and complete objectives might have checked the boxes but isn't actually embedding your product into their workflow. The combination tells you what to do.

What this means for your team

When your team has clarity on objectives and markers, they stop chasing engagement metrics that don't correlate with success. The focus shifts to milestones that actually predict outcomes.

The CSM reviewing their book of business doesn't have to investigate each account to figure out what's happening. They can see immediately which customers have completed their objectives, which are behind, and which are showing healthy markers despite being early in their journey. Prioritization becomes obvious.

For customers who fall behind on objectives, Trig can intervene automatically with contextual outreach targeted at the specific gap. A customer who hasn't invited team members gets a different message than a customer who hasn't connected an integration. The intervention matches the problem because the system understands the specific problem.

This frees your team to focus on the accounts where human judgment matters: complex situations, strategic relationships, customers facing challenges that don't fit neatly into a predefined playbook. The routine interventions happen automatically. The high-value work gets human attention.

The fundamental shift

The old way of measuring customer health treats all activity as signal. It counts logins and feature usage and support tickets and tries to derive meaning from the aggregate. When the numbers look good, you assume things are fine. When they drop, you scramble to figure out why.

Trig treats activity as context and milestones as signal. Objectives tell you whether customers are achieving the things that matter. Markers tell you whether they're exhibiting healthy patterns along the way. Together, they answer the question that activity metrics never could: is this customer on track to succeed?

Your data stops telling you customers are engaged and starts telling you customers are progressing. That's the difference between measuring the fridge door and knowing whether anyone ate dinner.