How-to guide
How to measure activation in a Slack community
Four metrics, how to compute each one from Slack exports or manual counts without a paid analytics tool, and the benchmarks operators use to know when they have a week-one activation problem. If you can only track one number, track the intro-post rate.
TL;DR
Week-one activation in a paid Slack community is measured with four metrics: (1) intro-post rate (members who posted in #intros within 7 days), (2) day-3 reply rate (conditional activation among non-starters), (3) day-7 message count (messages per member in the first week), (4) day-30 retention (members who posted in days 22–30 and were still subscribed). All four can be computed from Slack’s workspace export and a Stripe subscription report. No paid tool required at SMB scale.
Why “activation” is the right metric
Most paid Slack community operators track cancellations, but cancellations lag the real problem by 30–90 days. A member who never activates in week one is almost certain to cancel before month three — but the cancellation doesn’t show up in Stripe until they hit the renewal. By then the window to intervene has closed.
Activation metrics are leading indicators: they tell you at day 7 which members are on a churn trajectory, while you still have time to do something about it. The week-one drop-off diagnosis post covers the causal chain from non-activation to cancellation in detail. This page focuses on how to compute the metrics, not why they matter.
The four metrics
1. Intro-post rate Track weekly
The single most useful activation metric for most paid Slack communities.
How to measure: Pull Slack’s channel export for #intros (Workspace Settings → Import/Export → Export → select date range as JSON). For each file in the export, extract user_profile.name and ts (Unix timestamp). Match against your member join dates (from Launchpass or Stripe → Customer created date). Count posts where (post timestamp − join timestamp) ≤ 604800 seconds (7 days).
Manual alternative: Each Monday, open #intros, scroll to the members who joined 7+ days ago, and count how many posted. Takes 10 minutes for a 20-member weekly cohort.
| Benchmark | What it signals |
|---|---|
| ≥ 60% Healthy | Day-0 DM is landing well; activation system is working. |
| 40–59% Watch | Day-0 DM sent but may lack a single clear ask; some members are finding #intros but not posting. |
| < 40% Problem | Day-0 DM may not be sending, or is sending too late, or asks for too many things at once. Fix the message first. |
2. Day-3 reply rate Track weekly
Measures how many non-starters respond to a second prompt. Only meaningful if you send a day-3 follow-up.
How to measure: Subset your cohort to members who did not appear in the Slack export for days 0–2. Of those, count how many posted anywhere in days 3–4 (another Slack export, count messages from those user IDs). If you send a day-3 DM manually, count the replies; if via a bot, pull from bot logs.
Note: If you don’t currently send a day-3 message, this metric is zero by construction — which is actually useful information. The gap between your intro-post rate and 100% represents members who are reachable on day 3 but are not currently being reached.
| Benchmark | What it signals |
|---|---|
| ≥ 30% Healthy | Day-3 nudge is well-targeted and timely. |
| 15–29% Watch | Nudge is firing but message may be too generic; try keying it to the goal track the member stated in day-0. |
| < 15% Problem | Message may not be conditional (firing for members who already posted, which tanks conversion) or timing is off. |
3. Day-7 message count Track monthly
A continuous measure that captures activity beyond #intros.
How to measure: Export the full workspace (all channels) for the relevant week. Filter by user IDs in the cohort. Count messages with timestamp in the 7-day window. Divide by cohort size.
This metric is slower to move than intro-post rate and has more confounders (a slow week in the community lowers message counts for everyone). Use it as a monthly aggregate rather than a weekly signal.
| Benchmark | What it signals |
|---|---|
| ≥ 3.0 messages / member Healthy | Members are exploring beyond #intros; good topic diversity in the onboarding flow. |
| 1.5–2.9 Watch | Members are posting but concentrating in one channel (usually just #intros). Consider day-3 nudge directing to a more relevant channel for their goal track. |
| < 1.5 Problem | Low intro-post rate is likely pulling this down; fix intro-post rate first. |
4. Day-30 retention Track monthly
The downstream outcome metric — tells you whether week-one activation converted to month-one engagement.
How to measure: Export the workspace for days 22–30. Filter by cohort user IDs. Mark each user as “active” if they appear in the export. Cross-reference against Stripe (or your membership platform): filter out members who cancelled before day 30. Calculate: (active and subscribed) ÷ (total subscribed at day 30).
The “subscribed at day 30” denominator is important. If you use total cohort size, you conflate activation with retention and with voluntary cancellation before the metric window. Segment out the cancellations first.
| Benchmark | What it signals |
|---|---|
| ≥ 65% Healthy | Onboarding is converting to ongoing participation; churn risk is concentrated in the non-activated sub-group, not spreading to the activated group. |
| 45–64% Watch | Some activated members are going quiet by week 3–4. May indicate a content cadence drop in weeks 2–3 or lack of a peer connection moment (Donut pairing, structured introduction). |
| < 45% Problem | Month-one renewals are at risk. Investigate whether day-30 non-posting correlates with non-introduction in week one (it almost always does). |
The minimal tracking spreadsheet
If you have under 100 new members per month, you can track all four metrics in a spreadsheet with four columns:
- Member ID (Slack user ID)
- Join date (from Stripe or Launchpass)
- First post date (from Slack export)
- Day-30 subscribed (Y/N from Stripe)
Compute intro-post rate (first post date ≤ join date + 7 days), and day-30 retention (active AND subscribed). Day-3 reply rate and day-7 message count require slightly more joins but can be added to the same sheet as additional columns.
What Foothold automates
Foothold’s weekly digest is the automation-layer version of this spreadsheet. Every Monday morning, the operator receives an email: how many members joined, how many posted in #intros in week one (intro-post rate), how many replied to the day-3 nudge, and a list of members who hit day 7 without posting — the names worth a personal follow-up. No spreadsheet, no Slack exports, no manual join. The weekly digest is included in all Foothold plans.
For more on the full diagnostic: diagnose week-one drop-off in your Slack community walks through a structured analysis process for operators who want to understand exactly where their funnel is leaking.