KPI Tree

Slack logoSlack Integration

Slack is where your team lives. Make it where they act on metrics too.

Slack serves two roles in a KPI Tree deployment. First, it is a delivery channel: metric alerts, statistical summaries, and action requests arrive in the channels where work already happens - so stakeholders act on metric movements without switching tools. Second, it is a data source: Slack engagement data in your warehouse reveals communication health metrics that connect to team productivity, response time, and cross-functional alignment. KPI Tree uses both sides. Alerts reach the right people in the right channels. Engagement metrics feed into causal trees that show how communication patterns drive organisational performance.

Alerts in minutes, engagement metrics in under an hour

The Slack integration has two dimensions: push notifications that work out of the box, and engagement metrics that come from your warehouse.

1

Connect your Slack data

Three ways to get started, depending on your stack.

MCP
MCP

Pull metrics from Slack directly through the Model Context Protocol.

SnowflakeBigQueryDatabricks
Warehouse

Connect your existing warehouse where Slack data already lands.

Fivetrandbt
Professional Services

Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.

2

Connect Slack engagement data

Slack ships an official MCP server in general availability, and KPI Tree consumes it directly via OAuth 2.1, pulling search results, channel history, thread activity, message volume, and canvas events without any warehouse setup. Enterprise Grid customers who already export Slack Analytics to Snowflake, BigQuery, or Databricks can also point KPI Tree at the warehouse and read those tables in place. Teams without a warehouse engage our professional services team, which builds the pipeline and ships dbt models for communication health.

3

Build trees that span communication and business outcomes

Arrange Slack engagement metrics alongside productivity and collaboration KPIs in causal trees. Does faster Slack thread response time correlate with faster project delivery? Does cross-channel activity drive better alignment scores? The tree makes these relationships visible and owned.

Alerts where work happens. Engagement metrics where strategy lives.

KPI Tree integrates with Slack as both a notification channel and a data source - delivering metric context to teams and measuring communication health in causal trees.

Metric alerts delivered to the right Slack channel

When a metric moves outside statistical norms, the alert goes to the Slack channel where the owning team works - not a generic #alerts graveyard. Alerts include the metric value, the statistical context (how unusual the movement is), the causal chain showing potential upstream causes, and a link to take action. Teams respond in their workflow, not in a separate tool.

Weekly metric summaries in-channel

Configurable weekly summaries deliver metric tree health to Slack channels on a schedule. Each summary highlights metrics that moved significantly, new outliers detected, and actions that are due or overdue. Leadership channels get the executive tree summary; team channels get their subtree. No one needs to log in to know where things stand.

Slack engagement as a leading indicator

Message volume, thread depth, response time, emoji reactions, and cross-channel activity - when tracked from your warehouse, these become leading indicators for team health and alignment. KPI Tree's correlation engine can reveal whether Slack engagement patterns predict project outcomes, escalation rates, or employee satisfaction.

Alerts that arrive with context, not just a number.

A metric alert that says "Revenue dropped 8%" is noise. An alert that says "Revenue dropped 8%, which is 2.3 standard deviations below the 12-week trend, correlated with a 15% decline in Activation Rate this week" is actionable. KPI Tree's Slack alerts include the metric value, statistical significance, correlated metric movements from the causal tree, and a direct link to the metric detail page. The owner sees the full picture in-channel and can respond immediately.

  • Alerts include metric value, statistical context, and causal chain
  • Correlated metric movements surfaced automatically from the tree
  • Direct links to metric detail pages for deeper investigation
  • Channel mapping ensures alerts reach the right team, not a generic feed
Root cause analysis loading

Weekly summaries that replace the Monday metrics meeting.

Every Monday morning, a configurable summary lands in each team's Slack channel: which metrics moved significantly, which are trending outside targets, which actions are due, and which completed actions had measurable impact. Leadership channels get the top-level tree summary. Team channels get their subtree. The information that used to require a 30-minute meeting is available asynchronously before anyone opens their laptop.

  • Configurable schedule and channel mapping per metric tree or subtree
  • Highlights significant movers, outliers, and overdue actions
  • Leadership channels get executive summary; team channels get their scope
  • Replaces synchronous review meetings with asynchronous metric delivery
Subscription delivery channels loading

Communication health metrics that predict team performance.

Slack data in your warehouse is an untapped signal for organisational health. Message volume by channel, thread response time, reaction frequency, and cross-team communication patterns - these are leading indicators for alignment, velocity, and escalation risk. KPI Tree tracks them as metrics in causal trees alongside the outcomes they predict. When a team goes quiet, the tree shows whether productivity metrics follow.

  • Message volume, thread depth, and response time as owned metrics
  • Dimension breakdowns by team, channel, and time period
  • Correlation engine links communication patterns to project outcomes
  • Leading indicator alerts surface team health changes before they compound
Engagement heatmap loading

Action requests that close the loop from alert to outcome.

When a metric alert fires in Slack, the owner can create an action directly from the notification. That action is tracked against the specific metric, assigned a deadline, and followed up automatically. After the action is completed, KPI Tree verifies whether the metric improved - closing the loop from detection to response to verified outcome. No action items lost in Slack threads.

  • Actions created directly from Slack metric alerts
  • Each action linked to the specific metric it targets
  • Automatic follow-up reminders for overdue actions
  • Impact verification compares metric trends before and after intervention
Task assignment and tracking loading

How KPI Tree uses Slack differently

Most tools dump alerts into Slack. KPI Tree uses Slack as a two-way integration - delivering contextual alerts and measuring the communication patterns that predict organisational health.

causal · q < 0.05lag 3dq < 0.01Revenue-15%Conversion-23%Traffic+2%AOV-4%Checkout-31%PricingPaidOrganicBasket sizeDiscountsPayment errorsPage speed

Every source resolves onto one causal tree.

Contextual alerts, not notification spam

KPI Tree alerts include statistical context, causal chain, and correlated movements - not just a number. Channel mapping ensures the right team sees the right metrics. The result is fewer, better notifications that people act on.

Slack data as a leading indicator

Most tools treat Slack as a one-way alert pipe. KPI Tree also reads Slack engagement data from your warehouse and tracks communication patterns as leading indicators for team health, alignment, and velocity.

Closed-loop actions from Slack notifications

Actions created from Slack alerts are tracked, followed up, and verified for impact - turning Slack notifications from fire-and-forget into a managed response system.

Metrics you can track. Ready to add to your metric trees.

51 Slack metrics, defined and ready to drop onto a tree.

Active Channel Ratio

Collaboration

Active Channel Ratio = Channels with Messages in Period / Total Channels × 100

Active Channel Ratio measures the percentage of Slack channels that have received at least one message within a defined period. It reveals workspace sprawl - the accumulation of dormant channels that clutter search, confuse new joiners, and dilute information discoverability.

View metric

Alert Acknowledgement Time

Collaboration

Acknowledgement Time = First Human Response Timestamp − Alert Posted Timestamp

Alert Acknowledgement Time measures the elapsed time from when an automated alert is posted to a Slack channel to when a team member acknowledges it via a reaction, thread reply, or dedicated acknowledgement action. It is a critical metric for incident response and on-call effectiveness.

View metric

Alert Fatigue Score

Collaboration

Alert Fatigue Score quantifies the degree to which automated alerts in Slack overwhelm recipients, measured through alert volume, acknowledgement rate, and the ratio of actionable to informational alerts. High fatigue scores indicate that noise is drowning out genuine signals.

View metric

Channel Engagement Rate

Collaboration

Channel Engagement Rate = Unique Posters in Period / Total Channel Members × 100

Channel Engagement Rate measures the level of participation within a Slack channel, calculated from the ratio of unique posters to channel members and the volume of messages, reactions, and thread replies. It distinguishes between channels that foster active discussion and those that are broadcast-only or dormant.

View metric

Channel Growth Rate

Collaboration

Channel Growth Rate = (Members End of Period − Members Start of Period) / Members Start of Period × 100

Channel Growth Rate measures the rate at which Slack channels gain or lose members over time. It reflects the evolving relevance and visibility of channels within the organisation. Rapidly growing channels may signal emerging interests or initiatives, while declining channels may need restructuring.

View metric

Cross-Team Collaboration Index

Collaboration

Cross-Team Collaboration Index quantifies the degree of interaction between members of different teams within Slack, measured through shared channel participation, cross-team thread replies, and multi-team channel engagement. It provides an objective indicator of whether organisational silos exist.

View metric

Direct Message to Channel Ratio

Collaboration

DM to Channel Ratio = Direct Messages / Channel Messages

Direct Message to Channel Ratio compares the volume of direct messages to public and private channel messages within a Slack workspace. A high DM ratio may indicate a culture of private communication that limits knowledge sharing, transparency, and asynchronous discoverability.

View metric

Emoji Reaction Rate

Collaboration

Emoji Reaction Rate = Messages with Reactions / Total Messages × 100

Emoji Reaction Rate measures the proportion of messages that receive at least one emoji reaction within a given period. Reactions serve as lightweight acknowledgements in Slack - a way to confirm a message was read, signal agreement, or express sentiment without generating a full reply.

View metric

File Sharing Frequency

Collaboration

File Sharing Frequency = Total Files Shared / Time Period

File Sharing Frequency measures the volume of files - documents, images, code snippets, and recordings - shared across Slack channels over time. It serves as a proxy for knowledge-sharing activity and can reveal whether teams are collaborating effectively or hoarding information.

View metric

Integration Usage Rate

Collaboration

Integration Usage Rate = Active Integrations / Total Installed Integrations × 100

Integration Usage Rate measures how actively installed Slack apps and integrations are used, tracking message volume from bots, user interactions with app commands, and workflow triggers per integration. It reveals which integrations deliver value and which are unused overhead.

View metric

Meeting to Message Ratio

Collaboration

Meeting to Message Ratio = Number of Meetings / Number of Messages

Meeting to Message Ratio compares the volume of synchronous meetings (huddles, video calls) to asynchronous messaging within Slack. It provides insight into whether teams are effectively leveraging asynchronous communication or defaulting to meetings that fragment focus time.

View metric

Message Response Time

Collaboration

Message Response Time = First Reply Timestamp − Original Message Timestamp

Message Response Time measures the elapsed time from when a message is posted in a Slack channel to when it receives its first reply, either as a thread response or an in-channel follow-up. It reflects the responsiveness of communication within the organisation.

View metric

Message Volume Trends

Collaboration

Message Volume = Total Messages Sent in Period

Message Volume Trends tracks the total number of messages sent across a Slack workspace over time, segmented by channel type, team, and time period. It reveals communication patterns, seasonal variations, and growth trends that inform workspace governance and capacity planning.

View metric

Notification Engagement Rate

Collaboration

Notification Engagement Rate = Notifications Acted On / Total Notifications × 100

Notification Engagement Rate measures the proportion of Slack notifications that result in user action - opening the app, reading a message, or responding. It reveals whether notifications are driving productive engagement or being ignored due to overload.

View metric

Peak Activity Hours

Collaboration

Peak Activity Hours identifies the times of day and days of the week when Slack message volume and user activity are highest. It reveals the organisation's natural communication rhythms and helps set expectations for response times across different time zones.

View metric

Platform Adoption Rate

Collaboration

Platform Adoption Rate = Active Users / Total Provisioned Users × 100

Platform Adoption Rate measures the percentage of organisation members who are actively using Slack - sending messages, reacting, or engaging with content - within a defined period. It distinguishes between accounts that exist and accounts that are genuinely adopted into daily workflows.

View metric

Search Usage Frequency

Collaboration

Search Usage Frequency = Total Search Queries / Active Users in Period

Search Usage Frequency measures how often users search within Slack and the success rate of those searches. It indicates whether the workspace serves as an effective knowledge repository and whether information architecture - channel naming, pinning, and threading - supports discoverability.

View metric

Thread Completion Rate

Collaboration

Thread Completion Rate = Threads with Resolution / Total Threads × 100

Thread Completion Rate measures the percentage of Slack threads that reach a clear conclusion - indicated by a final reply, reaction, or explicit resolution marker - versus threads that trail off without closure. Incomplete threads represent unresolved questions and lost context.

View metric

Thread Engagement Rate

Collaboration

Thread Engagement Rate = Messages with Thread Replies / Total Messages × 100

Thread Engagement Rate measures the proportion of messages that generate threaded discussions, as well as the depth (number of replies) and breadth (number of unique participants) of those threads. It indicates how effectively the organisation uses threads for focused, contextual conversations.

View metric

Time to Resolution via Slack

Collaboration

Time to Resolution = Resolution Timestamp − Issue Posted Timestamp

Time to Resolution via Slack measures the elapsed time from when an issue, question, or request is posted in a Slack channel to when it is resolved, as indicated by a follow-up message, reaction, or linked ticket closure. It quantifies Slack's effectiveness as a real-time problem-solving platform.

View metric

Top Contributor Analysis

Collaboration

Top Contributor Analysis identifies the most active Slack users by message volume, thread participation, reactions given, and cross-channel engagement. It surfaces knowledge brokers who connect different parts of the organisation and potential bottlenecks where too much communication flows through a single individual.

View metric

User Activity Score

Collaboration

User Activity Score is a composite metric that blends multiple engagement signals - messages sent, reactions given, threads participated in, files shared, and app interactions - into a single score per user. It provides a balanced view of Slack engagement that goes beyond raw message count.

View metric

Workspace Growth Rate

Collaboration

Workspace Growth Rate = (Current Period Value − Previous Period Value) / Previous Period Value × 100

Workspace Growth Rate measures the rate of expansion across key dimensions - users, channels, messages, and integrations - within a Slack workspace. It informs governance planning, cost forecasting, and scaling strategies to ensure the workspace remains manageable as it grows.

View metric

Workflow Automation Usage

Collaboration

Workflow Usage = Total Workflow Executions / Time Period

Workflow Automation Usage tracks the adoption and execution volume of Slack Workflow Builder automations and custom bot workflows. It measures how many workflows exist, how frequently they are triggered, their completion rates, and the time they save compared to manual processes.

View metric

Workspace Health Score

Collaboration

Workspace Health Score is a composite metric that evaluates the overall health of a Slack workspace by weighting factors such as platform adoption rate, active channel ratio, engagement depth, DM-to-channel ratio, and notification engagement. It provides a single number for tracking workspace quality over time.

View metric

Active User Rate

Collaboration

Active User Rate = Users with Engagement Actions in Period / Total Provisioned Users × 100

Active User Rate measures the proportion of provisioned Slack accounts that demonstrate meaningful engagement - sending messages, reacting, or participating in threads - within a defined period. Unlike simple login counts, it captures whether users are genuinely integrating Slack into their daily workflows.

View metric

Channel Activity Analysis

Collaboration

Channel Activity Analysis evaluates individual Slack channels across multiple dimensions - message volume, unique contributors, thread depth, and reaction frequency - to produce a comparative view of channel health. It enables workspace administrators to rank channels by value and identify those that need intervention or archival.

View metric

Channel Member Distribution

Collaboration

Channel Member Distribution maps how workspace members are spread across Slack channels, revealing concentration patterns such as channels with disproportionately large or small memberships. It highlights structural imbalances that affect communication flow and information reach.

View metric

Conversation Sentiment Analysis

Collaboration

Conversation Sentiment Analysis applies natural language processing to Slack messages to classify the overall tone - positive, neutral, or negative - of conversations at the channel, team, or workspace level. It provides an early-warning indicator of morale shifts and cultural friction.

View metric

Message Engagement Rate

Collaboration

Message Engagement Rate = Messages with Interactions / Total Messages × 100

Message Engagement Rate measures the proportion of messages that generate at least one meaningful interaction - a thread reply, emoji reaction, or link click - within a defined window. It distinguishes messages that spark conversation from those that disappear into the scroll.

View metric

Average Session Duration

Collaboration

Average Session Duration = Total Active Session Time Across Users / Total Number of Sessions

Average Session Duration measures the typical length of a continuous period of activity a member spends in Slack, derived from the gap between their first and last actions within a session before a period of inactivity ends it. In Slack terms a session is bounded by message events, reactions, channel views and other activity logged against a user. It tells you how long people are genuinely present and working in the workspace, not just whether they have it open.

View metric

Bookmark Usage Rate

Collaboration

Bookmark Usage Rate = Active Channels with At Least One Bookmark / Total Active Channels x 100

Bookmark Usage Rate measures the proportion of active Slack channels that have at least one bookmark pinned to the channel header. Bookmarks give members quick access to important links, documents and tools without scrolling through message history, so this rate shows how consistently channels are set up to surface their key resources.

View metric

Channel Activity Rate

Collaboration

Channel Activity Rate = Total Messages Posted in Period / Total Active Channels in Period

Channel Activity Rate measures the average volume of messages posted across your Slack channels within a defined period, expressed per channel. It draws on Slack message and channel data to show how much conversation a typical channel carries, rather than just whether a channel is active or not. A falling rate often signals that work is draining away from public channels into direct messages or threads.

View metric

Channel Lifecycle Analysis

Collaboration

Lifecycle Stage = classify(channel) by days since creation, days since last message, and message volume trend, where Dormant = no messages in the last N days and Archival Candidate = dormant beyond the retention threshold

Channel Lifecycle Analysis examines how each Slack channel progresses through distinct stages, from creation, to ramp-up, to steady activity, to decline, and finally to dormancy or archival. Using Slack channel creation timestamps, message history, and last-activity dates, it classifies every channel by its current lifecycle stage and measures how long channels spend in each one. It turns a flat channel list into a view of where a workspace is growing, where it is stagnating, and where clean-up is overdue.

View metric

Channel Participation Distribution

Collaboration

Channel Participation Distribution = Messages from Top Contributors / Total Channel Messages in Period x 100

Channel Participation Distribution measures how evenly messages within a Slack channel are spread across its members over a defined period. Drawing on Slack message events and per-member authorship, it distinguishes channels where many people contribute from those where one or two voices dominate. It is typically expressed as the share of messages produced by the most active contributors, or as the proportion of members who posted at all.

View metric

Communication Cohort Analysis

Collaboration

Cohort Activity Rate (period N) = Active Users from Cohort in Period N / Total Users in Cohort x 100

Communication Cohort Analysis groups Slack users by a shared starting point, such as the week or month they joined the workspace, then tracks the share of each cohort that stays active in later periods. Using Slack message and membership data, it shows whether new joiners keep posting, replying and reacting, or go quiet after their first few weeks. Each cohort becomes a retention curve that exposes how communication habits take hold across the workspace.

View metric

Communication Network Analysis

Collaboration

Connection Density = Active Communication Pairs / Total Possible Pairs, where Total Possible Pairs = Members x (Members - 1) / 2

Communication Network Analysis treats your Slack workspace as a graph, where people are nodes and the messages, mentions and replies between them are the edges that connect them. Applied to Slack message metadata, it surfaces who is central to information flow, which teams are well connected, and which members or channels sit on the edges with few links to the rest of the organisation. It turns raw message volume into a structural view of how communication actually moves.

View metric

Cross Channel Communication

Collaboration

Cross Channel Communication = Members Posting in 2 or More Channels in Period / Total Active Members in Period x 100

Cross Channel Communication measures how widely a person or team participates across different Slack channels rather than concentrating activity in a single channel. Using Slack message and membership data, it captures the share of active members who post in more than one channel over a defined period, alongside the average number of distinct channels each contributor touches. A higher value signals that information and conversation flow across team boundaries instead of staying trapped in isolated channels.

View metric

Daily Active Users

Collaboration

Daily Active Users = Count of Distinct Members with at Least One Active Event in Slack on a Given Day

Daily Active Users measures the number of distinct Slack members who perform an active action in your workspace on a given day, such as posting a message, reading channels, reacting, or opening a thread. In Slack it is drawn from member activity events rather than seat counts, so it reflects genuine usage rather than how many people have been provisioned. It is the clearest day-by-day signal of whether your team is actually living in Slack.

View metric

Message Length Distribution

Collaboration

Share of Band = Messages in Length Band / Total Messages in Period x 100

Message Length Distribution measures how the character or word counts of Slack messages spread across a defined range, grouping posts into bands such as very short, short, medium and long. In Slack data, it separates one word acknowledgements and emoji replies from substantive paragraphs that carry context or decisions. The distribution gives a shape, not a single number, so the team can see where the bulk of communication sits.

View metric

Message Sentiment Analysis

Collaboration

Net Sentiment Score = (Positive Messages - Negative Messages) / Total Scored Messages x 100

Message Sentiment Analysis scores the emotional tone of Slack messages, classifying each post as positive, neutral or negative and aggregating the results across channels, teams and time periods. Applied to Slack data, it turns the raw text of everyday conversation into a measurable signal of how a workspace feels. It is typically expressed as a net sentiment score or the share of messages falling into each tone band.

View metric

Message Volume

Collaboration

Message Volume = Channel Messages + Thread Replies + Direct Messages in Period

Message Volume counts the total number of messages posted in your Slack workspace within a defined period, drawn from channel posts, threaded replies, and direct messages. It can be measured across the whole workspace or broken down by channel, by user, or by message type. This metric is the raw measure of how much conversation a Slack workspace carries.

View metric

Onboarding Conversation Rate

Collaboration

Onboarding Conversation Rate = New Members Who Posted in Window / Total New Members in Period x 100

Onboarding Conversation Rate measures the share of new Slack members who post their first message or reply within a defined window after joining the workspace. It treats a genuine conversation, not just a join event, as the signal that a new member has activated. In Slack data this is derived from each member join timestamp compared against the timestamp of their first authored message across public channels.

View metric

Pin Engagement Rate

Collaboration

Pin Engagement Rate = Pinned Messages with Interactions in Period / Total Active Pinned Messages x 100

Pin Engagement Rate measures the proportion of pinned Slack messages that receive a reaction, reply, or click within a defined period, relative to all active pins across your channels. Slack pins are meant to surface the most important reference material in a channel, so this metric tests whether those pins are doing their job. A low rate suggests pins have gone stale or were never the right things to highlight.

View metric

Reaction Usage Patterns

Collaboration

Reaction Usage Rate = Messages with at least One Reaction / Total Messages in Period x 100; Reactions per Message = Total Reactions / Total Messages

Reaction Usage Patterns measures how emoji reactions are applied to messages in Slack, covering the volume of reactions, the share of messages that receive at least one, and the mix of emoji used. From Slack message and reaction event data, it shows whether teams lean on reactions for quick acknowledgement, approval or sentiment rather than writing full replies. It is a behavioural signal of how a workspace communicates, not just how much it posts.

View metric

Reminder Completion Rate

Collaboration

Reminder Completion Rate = Reminders Completed in Period / Total Reminders Due in Period x 100

Reminder Completion Rate measures the proportion of Slack reminders that reach a completed state within a defined period, rather than being snoozed repeatedly or left outstanding. It draws on the reminder events Slack records when a member sets, completes, or deletes a /remind, including those created from a message. As a behavioural signal it shows whether follow-up commitments captured in Slack actually get actioned.

View metric

Response Time Analysis

Collaboration

Median Response Time = Median of (First Reply Timestamp - Original Message Timestamp) across messages in period

Response Time Analysis measures the elapsed time between an initial Slack message and the first reply it receives, calculated from message and thread timestamps in your Slack data. It can be aggregated by channel, by team, or by request type so you can see where conversations stall. The metric typically reports a median and a percentile such as the 90th, because averages hide the long-tail messages that frustrate people most.

View metric

Silent User Identification

Collaboration

Silent User Identification = Members With No Messages, Reactions or Replies in Period / Total Active Members x 100

Silent User Identification measures the share of Slack workspace members who are active enough to read messages but who do not post, react, or reply within a defined period. It separates genuinely engaged contributors from lurkers and dormant accounts by combining message authorship data with presence and read activity. A high count of silent users often signals that conversations are concentrated among a small group while the wider membership stays passive.

View metric

User Adoption Rate

Collaboration

User Adoption Rate = Active Slack Users in Period / Total Provisioned Slack Accounts x 100

User Adoption Rate measures the proportion of provisioned Slack accounts that have actively engaged with the workspace, such as posting a message, reacting, or joining a channel, within a defined period. In a Slack context it separates the people who have an account from the people who genuinely work in Slack day to day. It is the headline indicator of how well a Slack deployment has landed across the organisation.

View metric

User Group Effectiveness

Collaboration

User Group Effectiveness = Members Who Engaged With Group Mentions / Total Active Members in Group x 100

User Group Effectiveness measures how reliably a Slack user group, the @-mentionable handles such as @engineering or @support, delivers attention to the people inside it. In Slack data terms, it compares the members of a user group against how many of those members actually respond to, react to, or read messages that mention the group within a defined window. A low score signals a group that is stale, oversized, or routing notifications to people who no longer act on them.

View metric

User Retention Rate

Collaboration

User Retention Rate = Active Users in Both Periods / Active Users in Prior Period x 100

User Retention Rate measures the percentage of Slack members who were active in one period and remained active in the next period. In Slack terms, an active user is someone who posts messages, reacts, or reads channels within the window, captured from member activity and message events. It separates a workspace that holds onto its people from one that gathers accounts but loses real usage.

View metric

Common questions

Do I need a warehouse connection to use the Slack integration?
No. The Slack push notification integration for alerts, weekly summaries, and action requests works immediately via OAuth with no warehouse connection. For engagement metrics (tracking Slack communication patterns), KPI Tree consumes Slack's official MCP server directly over OAuth 2.1. Enterprise Grid customers who already export Slack Analytics to a warehouse can also point KPI Tree at those tables in place, and teams without a warehouse engage our professional services team to build the pipeline.
What Slack channels can receive KPI Tree alerts?
Any public or private channel the KPI Tree Slack app is invited to. You can map specific metric trees or individual metrics to specific channels, so each team only sees the metrics relevant to them.
How are alerts different from a typical Slack bot notification?
KPI Tree alerts include statistical context (how unusual the movement is relative to the trend), correlated metric movements from the causal tree, and direct links to the metric detail page. They are designed to be actionable in-channel, not just informational.
Can I track Slack engagement metrics?
Yes, if your Slack data lands in a warehouse. Message volume, thread response time, channel activity, reaction frequency, and cross-team communication patterns can all be tracked as metrics with ownership, alerts, and causal relationships to team productivity KPIs.
What Slack plans are supported?
The push notification integration (alerts, summaries, actions) works with any Slack plan. The official Slack MCP server works across Slack's paid tiers and is how KPI Tree reads engagement metrics for most customers. The data warehouse route works with any plan too, since Enterprise Grid provides native data exports and our professional services team can set up pipelines for any Slack tier.
Can actions be created directly from Slack alerts?
Yes. When a metric alert fires in Slack, the owner can create an action directly from the notification. The action is tracked against the specific metric, assigned a deadline, and followed up automatically. Impact is verified after the action is completed.
How do weekly summaries work?
You configure a schedule (e.g. every Monday at 9am) and map channels to metric trees or subtrees. Each summary highlights metrics that moved significantly, new outliers, and actions that are due or overdue. Leadership channels get the top-level view; team channels get their scope.
Does KPI Tree read Slack message content?
The push notification integration only sends messages to Slack - it does not read message content. The engagement metrics side reads aggregate metadata (message counts, timestamps, channel IDs) from your warehouse, not message text or file contents.

Meet your team where they work. Make sure they act on what matters.

Connect Slack to KPI Tree for contextual metric alerts, weekly summaries, and closed-loop action tracking - delivered to the channels where work happens. Add warehouse-backed engagement metrics to measure the communication patterns that drive performance.

Experience That Matters

Built by a team that's been in your shoes

Our team brings deep experience from leading Data, Growth and People teams at some of the fastest growing scaleups in Europe through to IPO and beyond. We've faced the same challenges you're facing now.

Checkout.com
Planet
UK Government
Travelex
BT
Sainsbury's
Goldman Sachs
Dojo
Redpin
Farfetch
Just Eat for Business