Three weeks running, one member sits at the top of your FluentCommunity Leaderboard. Comments answered, reactions given, points climbing every Monday. It reads like your best advocate.
That number never once asks whether they’ve opened this week’s lesson.
Somewhere lower on the same board sits a member who hasn’t posted since they joined. No comments, no reactions, nothing a leaderboard can see. FluentCRM’s automation log, fed by FluentPlayer, tells a different story: every lesson, watched past 90%, the week it drops.
One of these members renews because the training is still delivering. The other cancels because a leaderboard rank was never why they signed up. The Leaderboard can’t tell you which is which. Here’s what can.
TL;DR
- FluentCommunity’s Leaderboard scores participation: comments, reactions, posts, it says about whether a member is still watching your lessons.
- FluentCRM’s Automation Funnels include two free triggers fed by FluentPlayer, Media Milestone Reached and Media Layer Interaction.
- A high Leaderboard rank and strong video-watch behavior are two different signals. Neither substitutes for the other.
- Spotting engagement is automated and free; spotting who’s gone quiet is a saved filter you check by hand, also free, or a Conditional automation if FluentCRM Pro is already part of your stack.
- Tagging members by video behavior tells you attention, not intent to renew.
- Video Analytics (Pro) turns this into a dashboard, Top Users, retention curves, completion trend, once checking tags by hand stops scaling.
Where This Fits
This post assumes you already know the shape of FluentPlayer’s Video Analytics for WordPress, watch time, retention, completion rate. What follows narrows that vocabulary to one job: telling power members and at-risk members apart inside a FluentCommunity membership.
What Video Engagement Can and Cannot Tell You About a Member
The Media Milestone Reached trigger, a FluentCRM automation fed by FluentPlayer, tells you one specific member crossed one specific point in one specific video. That’s it. FluentPlayer’s watch tracking is server-verified and doesn’t count skipping ahead, so a milestone tag reflects real playback, not a scrubbed position.
Still, it does not tell you why they stopped watching short of that point, whether the lesson lost them or a Tuesday got busy. It does not tell you whether they intend to renew, recommend you, or ever open the community again.
Media Layer Interaction tells you a member saw, completed, or skipped something inside the video: an overlay, a form, a CTA. Those are three separate, selectable events, not one blended signal, so a skip and a completion should never feed the same tag. Seeing a layer doesn’t mean reading it carefully, and completing one doesn’t mean the click was an agreement.
Neither trigger, alone or combined, produces a churn score. FluentPlayer doesn’t calculate renewal probability. What it gives you is a behavior log: who watched what, how far, and when. The interpretation is yours, and it should stay honest about what it can’t see: real life, competing priorities, a member who reads every email but never touches the player.
The Complete Workflow, Before Any Settings
- Publish each new lesson as a FluentPlayer video inside your FluentCommunity Course.
- The Media Milestone Reached trigger fires in FluentCRM the moment an identified member crosses your chosen watch threshold on that video.
- Media Layer Interaction fires separately if the member engages with anything you’ve layered into the video.
- A FluentCRM Automation Funnel applies a tag based on which trigger fired and for which lesson.
- Each cycle, you pull a saved filter: members carrying an older lesson’s milestone tag but not the newest one. That’s your quiet list, and building it is a manual check, not a trigger.
- You review that list alongside the FluentCommunity Leaderboard, both by hand. Neither one merges into the other, and that’s deliberate.
Sorting cold traffic instead of an existing membership? The same two triggers run a product launch waitlist in How to Use Video Lead Scoring for a Product Launch Waitlist, tiering strangers by watch depth instead of flagging members who’ve gone quiet.
What You Need Before You Build
- FluentPlayer active, with lesson videos embedded inside a FluentCommunity Course. The integration itself is free on both sides and connects automatically, no API key, no account to link.
- FluentCRM’s Event Tracking Module enabled: FluentCRM → Addons → Event Tracking Module → Settings → Enable Event Tracking Module. FluentPlayer’s own documentation flags this as the step people miss, and it’s off by default. Skip it and the contact-level activity this whole build depends on doesn’t show up anywhere.
- FluentCRM connected, with Automation Funnels enabled. The trigger picker for Media Milestone Reached and Media Layer Interaction is free, no Pro plan required.
- A defined publishing cadence, weekly, biweekly, whatever you actually run. Without a known cadence, you can’t tell a member who’s disengaged from a member who’s simply between lessons.
- FluentCRM’s Advanced Filter, to save the “has an older milestone tag, not the newest one” view you’ll check each cycle. This is a contacts-list filter, not an automation, so it’s free regardless of which FluentCRM plan you run.
- Nothing here to tag yet because nobody’s enrolled? Turn a Free Course Lesson Into a Complete Enrollment Funnel covers the stage before this one, turning a single lesson into your first wave of members.
- If FluentPlayer isn’t running on your site yet, install the free plugin from WordPress.org before building the funnel below. For every setting covered next, walked through end to end with its own screenshots, FluentCRM’s integration guide covers the same build.
Step-by-Step: Tagging Video Behavior With FluentPlayer’s Free Triggers
Turn on re-entry before you set anything else
By default, Media Milestone Reached runs once per contact. The first lesson to cross your threshold enters the member, and every lesson after is skipped for them. Check “Allow contacts to re-enter when another targeted media reaches this milestone” in the trigger’s WHO CAN ENTER section. Skip this, and a member who watches every new lesson looks identical to one who watched a single lesson and never came back, since only the first one ever tags them.
Pick your milestone from the real options, not an arbitrary percentage
The Watch Milestone control offers five fixed choices: Started, Reached 25%, Reached 50%, Reached 75%, or Completed. Choosing Completed opens a separate Completion Threshold (70, 80, 90, 95, or 100 percent), since outros get skipped often enough that 100 percent rarely fires. For most training content, Reached 75% or a Completed trigger with a 90 percent threshold gives you a real signal without over-crediting a viewer who clicked away early.
Scope the trigger to the lesson, not the whole library
Apply Media Milestone Reached per video rather than as a blanket rule across every lesson in the Course. A member who watches lesson one closely and skips lesson four isn’t disengaged; they might already know that material. Tagging per lesson keeps that distinction visible instead of averaging it away.
Name tags by lesson and week, not by member status
A tag like watched-lesson-4-milestone tells you exactly what happened. A tag like engaged-member tells you an opinion you formed later. Keep the tag descriptive of the behavior, not the conclusion.
Add Media Layer Interaction as a second, lighter signal
If a lesson has an embedded form or CTA, this trigger fires when a member interacts with it. It’s a shallower signal than a milestone tag, since someone can click a CTA out of curiosity without watching the surrounding content, so weight it accordingly rather than treating a click the same as a completed watch.
Pair every milestone tag with a Remove From Tag step targeting “quiet”
FluentCRM’s Automation Funnels treat Apply Tag and Remove From Tag as separate Primary Actions, both free. Whenever Media Milestone Reached fires, on any lesson, for any threshold, add a Remove From Tag step right after it, targeting the quiet tag. This half of the exclusivity logic is fully automated regardless of your plan: any sign of fresh engagement clears the stale label.
Build the quiet list as a saved filter, not an automation
In FluentCRM’s Contacts view, use Advanced Filter to find members carrying an older lesson’s milestone tag without the newest one, for example, watched-lesson-4-milestone present, watched-lesson-5-milestone absent. Review that list each cycle and bulk-apply the quiet tag by hand. No automation ever needs to detect an absence; you do, and this keeps the entire build free.
If FluentCRM Pro is already part of your stack, this one step can run itself
A Conditional block can check Fluent Player, Watched Media, with that specific lesson’s video selected, set to No, server-verified, skipping ahead doesn’t count. Wire it after a Wait step sized to your publishing cycle, and it applies the quiet tag automatically instead of you checking a filter. This is the only piece in this build that needs FluentCRM Pro; everything else runs on the free plan.
The Power Member vs. At-Risk Member Signal Table
| Tag | What it means | Follow-up job |
| watched-lesson-[n]-milestone | This member crossed your set threshold on this specific lesson | Confirms the content is landing. No outreach needed |
| interacted-lesson-[n]-layer | This member engaged with something inside the video. Weaker signal than a milestone tag | Worth a light touch if it’s the only signal you have on this member |
| quiet-[n]-weeks | This member has an older lesson’s milestone tag but not the newest one | Triggers a check-in message, not a hard sell |
Exclusivity
Removing the quiet tag is automated on any plan: a fresh milestone tag, on any lesson, always clears it. Applying the quiet tag is the part that differs, a saved filter you check by hand on the free plan, or a Conditional block if FluentCRM Pro is already in your stack. Either way, a member should never carry both a fresh milestone tag and a quiet tag at once; if your reporting shows both, the removal step isn’t wired correctly.
Namespacing
Running this same setup for a second course or a new cohort? Prefix every tag with that course’s name. springcourse-watched-lesson-4-milestone versus summercourse-watched-lesson-4-milestone keeps last season’s activity from bleeding into this season’s numbers.
What these tags are not
A tag describing watch behavior is not a loyalty score, and it is not a renewal prediction. It’s a record of what a specific member did, nothing more.
Do not use a milestone tag as a shortcut for finding your best referral sources
Watching every lesson to completion says a member values the content. It says nothing about whether they’d recommend you publicly. Treating your most-tagged members as your advocate list puts people who prefer to learn quietly in front of a referral ask they never wanted. If you want advocates, look for a public action, a comment, a review, a share, not a private watch history.
Seeing the Full Picture With Video Analytics (Pro)
Tag-checking by hand works at the size where you can hold your member list in your head. Past that, Video Analytics turns the same behavior into a dashboard instead of a funnel report.
Top Users surface your highest watch-time members without you reading tag history one contact at a time. Audience retention and completion-rate trends show whether engagement across the whole membership is climbing or sliding, a pattern no single tag exposes on its own.
New vs. returning viewers on a lesson shows whether last week’s quiet members came back for the next drop.
None of that changes what the data proves. Video Analytics reads the same triggers at scale; it doesn’t add a layer of intent the triggers didn’t already have.
Buy FluentPlayer Pro to Access Video Analytics→
What to Send Each Group
A member carrying fresh milestone tags doesn’t need anything from you. Sending a check-in to someone actively watching reads as noise, or worse, as a sales approach dressed as concern.
A member who gets tagged quiet, whether from your filter check or a Pro Conditional, gets a short, specific message. Reference the actual lesson they stopped on, not a generic “we miss you.” “Looks like lesson four’s still sitting unwatched, anything blocking you?” does more work than a discount code, since it treats the gap as a real question instead of a churn event to head off.
Reserve any offer or incentive for a member who’s been quiet across multiple lessons in a row, not the first missed one. One skipped lesson is a normal week. Two or three in sequence is the pattern worth acting on.
Test the Complete Chain Before You Trust It
Run three test contacts through the full setup before trusting it with real members. To check what actually happened rather than guessing from the outside, open FluentCRM → Contacts, click the test contact, and read the Event Tracking section in the Additional Information panel, it lists exactly what fired, on which video, and when.
Fully engaged
Watch every new lesson past your milestone threshold, in order, for three publishing cycles. Expected state: a fresh milestone tag each cycle, no quiet tag ever applied.
Partially engaged
Watch each lesson to 40 percent, below your threshold. Expected state: no milestone tag fires. Confirm this directly; a trigger that fires below your intended threshold will quietly inflate every number downstream.
Gone quiet
Watch the first two lessons past the threshold, then stop entirely for two publishing cycles. Expected state: this contact appears on your saved filter, older milestone tag, no newer one, once the second cycle passes. If you’re running the Pro Conditional version instead, the expected state is the quiet tag applying automatically at the same point. Either way, the earlier milestone tags should stay in the member’s history rather than disappearing.
Edge cases worth checking separately: An anonymous or logged-out viewer, FluentPlayer can only attribute activity to someone it can identify, a logged-in user or an existing contact, so an anonymous visitor has nothing to attach the event to, and separately, the trigger’s own “if the viewer is not in your CRM yet” setting decides whether an unrecognized-but-later-identifiable viewer gets skipped entirely or created as a pending contact; a contact sitting in a pending or unsubscribed state in FluentCRM, who may still trigger tags even though they shouldn’t receive the follow-up messages tied to them.
Rewatching an old lesson is not an edge case worth testing. FluentPlayer logs each milestone once per contact per media item, so a rewatch doesn’t re-fire the trigger or duplicate the tag.
Measure Whether This Actually Helps
Define the number you’re actually watching: re-engagement rate, the count of quiet-tagged members who pick up a new milestone tag within your outreach window, divided by the total number of members who received a check-in message that cycle.
One run of this doesn’t prove the check-in message works. It tells you whether anything obvious is broken, a tag misfiring, a threshold set wrong, before you draw a real conclusion. Change one thing between cycles, the message, the threshold, the gap length that defines quiet, so whatever moves the number is the thing you actually changed.
Close
The Leaderboard was never built to answer this question, and that’s fine; it’s doing its own job well. Video engagement is the piece it can’t see. Put the two side by side instead of asking one to stand in for the other, and a member who stops showing up in your feed but keeps opening every lesson stops looking like someone slipping away.
Start with FluentPlayer and FluentCommunity, both free, plus the free Automation Funnels trigger picker in FluentCRM. Nothing above needs a paid plan to work, including the quiet list, that’s a saved filter you check by hand. If FluentCRM Pro already sits in your stack, the same check can run itself; if it doesn’t, nothing here is waiting on it.
Once your list outgrows what a tag report can show you at a glance, Video Analytics (Pro) turns the same behaviour into a dashboard you check instead of a funnel you read line by line.
Frequently Asked Questions
What is a power user in an online community?
A power user is a member whose engagement sits well above the average member’s, measured by whatever behavior actually matters on your platform. In a FluentCommunity membership built on video training, that’s watch behavior more than post count, since post count alone can overstate participation from members who talk more than they watch.
How do you identify at-risk members in an online community?
Look for a change against a member’s own baseline, not a fixed rule. A member who watched every lesson for two months and then stopped for two publishing cycles has changed behavior in a way worth a check-in. A member who never posted and never will isn’t automatically at-risk; that might just be how they use the community.
Does watching more videos mean a member won’t cancel?
No. Watch behavior shows attention, not intent. A member can watch every lesson and still cancel for reasons that have nothing to do with the content: price, timing, a change in their own goals. Treat high engagement as a good sign, not a guarantee.
Can a community Leaderboard alone predict who’s about to leave?
Not on its own. A Leaderboard measures visible participation: posts, comments, reactions. A member can stop posting while still watching everything, or keep posting while having quietly stopped watching. Pairing the Leaderboard with a video-behavior signal catches both blind spots.