> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tightknit.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Navigating Studio Analytics
> How to use Tightknit Studio to track engagement, analyze member behavior, and turn insights into action.
## 1. Open Tightknit Studio
* Navigate to your Tightknit Home dashboard
* In the top right corner, click the green button that says **Tightknit Studio**
* The button will redirect you to a new window
* Log in using the **same email and account** that is connected to your Slack workspace
## 2. Get oriented: Studio sections
The Studio interface is organized into the following sections:
* **Overview:** High-level analytics and charts about your community's performance and engagement
* **Members:** Search, filter, and understand who is in your community and how they participate
* **Discussions:** Explore Slack discussions and threads across your activated channels
* **Activities:** A chronological activity feed showing what is happening in your community
* **Site:** Traffic and performance for your community site (if enabled)
Use this mental model:
* **Overview** = "How healthy is the community overall?"
* **Members** = "Who is here and how are they behaving?"
* **Discussions & Activities** = "What conversations and actions are driving engagement?"
* **Site** = "How is my community site contributing to reach and engagement?"
### 2.1 Members
Use **Members** to search, filter, and manage your community members.
You can:
* Find members by **name** or **email**
* Filter by **role** (Admin, Member, Bot, Non-bot)
* Sort by **name**, **role**, **join date**, or **last active**
Click a member's name to:
* View more details about their activity
* Access their profiles on the web and in Slack
Use this view when you want to:
* Identify rising champions or lurkers
* Check whether specific cohorts (for example, new signups from a campaign) are activating
* Prepare for outreach, office hours, or champion programs
### 2.2 Discussions
Use **Discussions** to view and monitor Slack messages from your activated channels.
You can:
* Search messages by **content** or **author**
* Filter by specific **channels**
* Sort by **newest** or **oldest** messages
Click a message to:
* View the full discussion thread
* See participant details and insights
Use this view when you want to:
* Understand which topics consistently drive replies
* Review how product launches, announcements, or events landed
* Pull examples for customer stories or community-led content
### 2.3 Activities
Use **Activities** to track all community interactions in a chronological feed.
You can:
* Search activities by **content** or **participant**
* Filter by **activity type** (for example, messages, joins, reactions)
* Sort by **newest** or **oldest**
Click any activity to:
* Open the related discussion
* See who was involved and how they interacted
Use this view when you want to:
* Get a quick sense of "what happened lately"
* Monitor whether new experiments (prompts, events, programs) are creating visible activity
* Spot patterns in when your community tends to be most active
### 2.4 Site
If you use a community site, the **Site** section helps you monitor its traffic and performance.
You can see:
* Visitor counts and pageviews
* Bounce rates and time on site
* Geographic data and device types
* Traffic sources and top-performing pages
Use this view when you want to:
* Understand which channels or pages are driving the most site traffic
* See whether SEO or content experiments are working
* Connect on-site behavior back to Slack discussions and programs
## 3. Set your time range
Once you are oriented, set your **date range** in Studio:
* **Last 7 days**
* **Last 30 days**
* A **custom range** that matches a launch, event, or campaign
## 4. Review core engagement metrics (Overview)
Start in **Overview** to understand community health at a glance.
Look at **message activity**:
* **Total messages** sent in the time range
* **Replies and comments**, which show how much conversation is happening versus broadcast messages
Then review **member activity**:
* Compare **active members** to total members for that period
* Check **new members added** in the time range
* Look at patterns over time (for example, are active members trending up, flat, or down?)
Use this view to answer:
* "Is the community more or less active than last week or last month?"
* "Are we getting more people talking, or just more people joining?"
## 5. Drill into specific channels or groups
Next, zoom in on where engagement is actually happening.
* Use filters to focus on a specific **channel** or **group** (for example, main community channel vs. a cohort channel or program space)
* For each important channel, look at:
* **Message volume** over the selected period
* Number of **unique participants** posting or replying
* **Trends over time**: is engagement rising, flat, or dropping?
Use this to:
* Identify channels that are **high-leverage** and should be protected or amplified
* Spot channels that might be **duplicative** or confusing for members
* Make decisions about where to run prompts, events, or experiments
## 6. Spot patterns and seasonality
Zoom out to look across weeks or months.
Scan the **activity graph** to identify:
* Regular cycles (for example, more activity mid-week)
* Expected dips (for example, major holidays, common vacation periods)
* Flag any **unexpected drops or spikes**:
* Sudden drop → may indicate content fatigue, timing issues, or a confusing channel structure
* Sudden spike → may highlight an event, announcement, or experiment that landed especially well
Use this to:
* Normalize expectations around holiday dips
* Document what tends to work (for example, recurring events, formats, or themes)
* Build a simple "community calendar" anchored to what you see in the data
## 7. Turn insights into actions
Use what you see in Studio to drive concrete experiments.
For channels with **low or declining engagement**, consider:
* Scheduling a **prompt**, **AMA**, office hours, or a **live event** in that space
* Doing **targeted outreach** to key members to restart conversation
* Clarifying the **channel purpose** in the description and pinned messages
* Simplifying or **archiving low-value channels** so activity is less fragmented
## 8. Re-check after you run experiments
Treat Studio as your experiment scorecard.
1. Define a clear **experiment**: for example, a 4-week event series, new weekly prompts, or a focused cohort channel
2. Let it run for **1–2 weeks** (or a full program cycle)
3. Return to Tightknit Studio and:
* Compare **engagement before vs. after** the experiment window
* Look in **Overview** for big shifts and in **Discussions/Activities** for specific threads and behaviors
* Decide whether to **keep**, **tweak**, or **drop** that tactic
## Troubleshooting
Start by focusing on **one priority channel** and one metric (for example, messages per week). Launch a simple weekly prompt or AMA in that channel and measure only that change for 1–2 weeks.
Check whether the **channel purpose is still clear** in the description and pinned messages. Try consolidating related channels so conversations have fewer places to fragment.
Cross-reference the spike dates with **events, announcements, or product changes** you shipped that week. Look at the specific channel(s) that spiked to see which posts or threads drove the lift.
Filter for the period after new member cohorts joined and check how many posted within their first 7–14 days. Pair this with onboarding experiments (welcome posts, intro prompts, first-win activities) and track whether activation improves.
Pick a small set of **north-star metrics** to watch weekly (for example, active members, replies per active member, and messages in your main channel). Review deeper charts only when those core metrics change meaningfully.
Users may be added to their organization's Studio workspace in one of the following ways:
* The user that first installs the Tightknit app into the Slack workspace is automatically added to the Studio workspace, as long as they are an admin and meet the requirements above
* When admin users visit the Tightknit app home in Slack, they are automatically added to the Studio workspace
* In Studio > Workspace > Admin, the organization admin may manually invite users to join the workspace via email
**Make Studio part of a weekly ritual**
Schedule a short, recurring review of Tightknit Studio (for example, 15 minutes every Monday). Look at the same small set of metrics, note one win and one concern, and choose **one experiment** for the week.
This rhythm keeps analytics lightweight but actionable, and ensures your community strategy is guided by real behavior instead of guesses.
## Related topics
- [Guides](/guides/index.md)
- [Studio](/studio/overview.md)
- [Studio Settings](/studio/settings.md)
- [Access the Studio](/studio/access.md)
- [Activate a Channel for Tightknit](/channels-and-feeds/activate-channel.md)