Week-one activation
How to measure week-one activation in your Slack community (without any special tooling)
You have read that week-one activation is the fastest lever for paid-community retention. You want to know where you stand. This post walks through how to calculate the number — using only Slack Analytics and your billing system — with a worked example and a decision tree for what to do once you have it.
What “activated” actually means — and the three definitions operators use
Before you can measure week-one activation, you need a single, crisp definition of what activated means for your community. Most operators never settle one. They have a vague sense that it means “engaged” or “using the community,” which makes the metric unmeasurable and therefore unused. There are three definitions in common use, ordered from loosest to strictest:
Definition 1 — Workspace entry. The member opened the Slack workspace at least once in the first seven days. Slack’s Analytics dashboard calls this “active.” This is the loosest definition and the least useful one for paid communities. A member who opened Slack once, saw 17 channels, felt overwhelmed, and never returned scores as “activated” under this definition. That is not activation; it is a visit.
Definition 2 — Posted at least once. The member sent at least one message in any public channel in the first seven days. This is the correct threshold for paid subscription communities, and the one used in the worked example below. A post is the first durable signal that a member has moved from observer to participant. The correlation between posting in week one and renewing at month two is strong enough that this single binary — posted or did not post — is more predictive of retention than any composite engagement score. What does not count: reactions, channel joins, reading threads, opening DMs. A reaction is an ambient signal; a post is a commitment.
Definition 3 — Posted and received a reply. The member posted at least once and had at least one other member reply to their post. This is the strictest definition and the right one for communities where connection, not content, is the primary value proposition. Communities with a professional networking focus — job boards, mastermind circles, peer advisory groups — often use this definition because a post with zero replies still leaves the member in isolation. For these communities, activation is a two-party event.
For the rest of this post, “activated” means Definition 2: posted at least once within seven days of joining. If your community is in the “connection” category, swap in Definition 3 and the formula still works.
Where to get the data
You need two exports: one from Slack and one from your billing system. No API access required, no custom code. Both exports are available to workspace admins through standard web interfaces.
Step 1 — Export the Slack Analytics member table. Go to your Slack workspace. In the left sidebar, click your workspace name at the top left → Settings & administration → Analytics. This opens the Analytics dashboard. Click the “Members” tab. At the top right of the table, click “Export CSV.” The file downloads immediately. It includes every member who has ever been in the workspace, with columns for: display name, email, join date, last active date (last message sent), and total messages sent.
Two important notes on this export. First, “last active date” in the Slack Analytics export means the date of the member’s last message sent — not the last date they opened the app. This distinction matters. A member who opens Slack daily but never posts will show a “last active date” of their join date if they never posted, which is exactly what you want for this measurement. Second, if your workspace is on the legacy Free plan and has more than 90 days of history, the export may truncate older join dates. If you are measuring a historical cohort older than three months and are on Free, your data will be incomplete. Upgrade to Pro, or restrict your measurement window to the most recent 90 days.
Step 2 — Export your billing system member list. In Stripe: Customers → Export → select “all customers” or filter by your subscription product. The export includes email and subscription start date. In Memberstack: Members → Export → CSV. In Gumroad: Analytics → Sales CSV. Whatever your billing system, the goal is a file with at least two columns: email and the date the member first paid.
Step 3 — Cross-reference in a spreadsheet. Open both CSVs in a spreadsheet tool (Google Sheets or Excel). Use VLOOKUP or XLOOKUP on the email column to merge the billing start date into the Slack Analytics rows. Filter the merged table to rows where the billing start date is within your measurement window — for example, the four-week period ending last Sunday. This gives you your measurement cohort: paying members who joined in the last four weeks.
Now add one calculated column: days_to_first_post. This is the Slack “last active date” minus the Slack join date, but only if the join date and first-post date are within seven days of each other. For members who have never posted, this value is blank. Members with a value between 0 and 7 are activated; everyone else is not.
The calculation — with a worked example
The formula is straightforward:
Week-one activation rate = (members who posted within 7 days of joining) ÷ (total members who joined in that period) × 100
Here is a worked example with a realistic community. Suppose you run a paid product-management community with 800 total members. In the four-week period from May 5 to June 1, 2026, 64 new members joined (roughly 16 per week). After cross-referencing the Slack export against your billing system, your spreadsheet shows:
- 64 members joined in the window
- 38 have a first-message date within 7 days of their join date
- 11 have a first-message date more than 7 days after their join date (they eventually posted, but not in week one)
- 15 have never posted (blank last-active date)
Week-one activation rate = 38 ÷ 64 × 100 = 59.4%
That is one number. To track it over time, add a row to a simple spreadsheet each Monday:
| Cohort week | Joined | Activated in 7d | Rate |
|---|---|---|---|
| May 5–11 | 17 | 10 | 59% |
| May 12–18 | 14 | 9 | 64% |
| May 19–25 | 18 | 10 | 56% |
| May 26–Jun 1 | 15 | 9 | 60% |
The trailing four-week average for this community is 59.8% — squarely in the 40–60% band. The week-to-week variation (56–64%) is normal with cohorts of 14–18 members; a two-point move in either direction is noise, not signal. Wait for a three-week directional trend before treating a change as real. For communities with fewer than ten new members per week, use a rolling two-week cohort instead of weekly to reduce the noise.
The full breakdown of what engagement rate measures and how activation fits into it is worth reading alongside this post if you want to understand how week-one activation relates to the broader set of community health numbers. Activation is the fastest-moving lever; the others are longer-cycle.
What to do when you see the number
The rate is a diagnosis, not a goal. Here is what the four bands mean and what to do in each one.
Below 40% — activation is the bottleneck. More than six in ten new members are not posting in their first week. This is not a content problem or a pricing problem; it is an onboarding problem. At this rate, month-two retention is almost certainly below 60%, and the operator is losing subscribers who would have stayed if they had engaged. The fix is a structured day-0 outreach: a direct message sent to every new member within two hours of joining, with a single specific ask and a concrete payoff. If you are not sending any welcome DM today, that is the first and only change to make before measuring anything else. Give it four cohort-weeks before re-measuring.
40–60% — improve the day-0 DM. This is the median range for communities that have some onboarding in place but have not optimised it. The welcome DM exists, but it probably has multiple asks, a generic opener, or no urgency frame. The right intervention is a structural rewrite of the day-0 message: one ask, one payoff, one reason to act this week. Diagnosing where in week one the drop-off is happening will tell you whether the issue is in the message itself or in the timing of delivery. If members are opening the DM but not acting on it, the ask is wrong. If the DM has a low open rate (measurable only with a bot, not with manual DMs), the timing is wrong.
60–75% — optimise the day-3 nudge targeting. At this rate the day-0 DM is working: the majority of new members are posting. The remaining gap — the 25–40% who are not activating — is the harder segment to reach. These are members who opened the welcome DM and decided not to act, or members who did not see it. A conditional day-3 nudge — one that fires only to members who have not yet posted, and that offers a lower-effort entry point than the day-0 ask — is the right next step. The key word is conditional: a day-3 nudge that also goes to members who already activated is a bad signal and damages trust with the people you most want to keep.
Above 75% — shift focus to content cadence for months 2–6. You have solved week-one activation. The retention risk at this rate is not new-member drop-off; it is the gradual disengagement of members in months two through six who found the community valuable in the first weeks but stopped opening it as the initial novelty faded. The intervention here is content cadence: a predictable weekly signal that gives members a reason to return. The member retention framework covers the full cycle, including what good content cadence looks like at different community sizes.
How to improve the rate once you have a baseline
The lever set is small. There are exactly three things that move week-one activation rate:
The day-0 DM — what you send, when you send it, and from whose handle. A message sent within two hours of join converts at significantly higher rates than one sent at the end of the day. A message from the operator’s personal Slack handle converts higher than a bot message. A message with one ask converts higher than one with three. These three variables — timing, sender, and ask count — are the only structural levers in the day-0 DM. Everything else is copy, and copy matters far less than structure.
The day-3 nudge — a conditional follow-up sent only to non-activated members that reframes the ask. Not a reminder (“did you see my last message?”) but a new entry point. The day-3 nudge does not need to ask for the same thing as the day-0 DM. It can be lower-stakes: “What’s one thing you’re working on right now that you’d want a second pair of eyes on?” is easier to answer than “post a two-sentence intro in #intros.” The answer to that question can become the intro, but the member does not need to know that upfront.
The day-7 operator scorecard — knowing who to follow up with personally. At the end of every member’s first week, someone on the operator team should have a list of the names of members who have not yet posted, so they can decide who merits a personal outreach (a message from the operator, not a bot). The scorecard makes this possible without the operator manually checking each member’s profile. Three names per week is a manageable personal-follow-up load for a solo operator running a 500-member community.
The challenge is that the conditional check — “has this member posted yet?” — is difficult to implement manually at any meaningful scale. At 10 new members per week you can check by hand. At 30, it becomes a half-hour task that gets skipped when the operator is busy. At 80, it is not possible without tooling. For a baseline measurement of where you stand before you implement any of this, the Onboarding Health Check runs in two minutes and gives you a 0–50 score with the three fixes most likely to move your specific number.