Conversation Mapping
How ThreadTrak captures and organizes Twitter conversations into a structured view.
What is Conversation Mapping?
When you view a tweet on X, replies are displayed in a flat, algorithm-sorted list. Conversation Mapping is ThreadTrak's process of reading these replies and organizing them into a structured tree that shows the true conversation flow.
This enables Tree View, Priority View, and all the filtering and action features that make ThreadTrak powerful.
How It Works
1. Opens on Tweet Detail Pages
ThreadTrak activates when you open a tweet's detail page (the permalink where you can see all replies). It immediately starts reading the visible replies.
2. Reads Replies as You Scroll
X loads replies progressively as you scroll down the page. ThreadTrak watches for new replies and automatically adds them to your conversation tree. The more you scroll, the more complete your tree becomes.
3. Captures Reply Context
For each reply, ThreadTrak extracts the author info, reply text, engagement metrics, and who the reply is responding to. This data populates the cards you see in Tree View.
4. Preserves the Tree
Once captured, replies stay in your tree even if X removes them from the visible page (due to lazy loading). Your conversation state is preserved until you navigate away.
The "Map Thread" Button
In the toolbar, you'll see a Map Thread button. This forces ThreadTrak to rescan all currently visible replies on the X page.
When to use Map Thread: If you've scrolled through a long thread and want to ensure ThreadTrak has captured everything visible, click Map Thread to trigger a full rescan.
What Gets Captured
For each reply that ThreadTrak maps, the following data is extracted:
| Data | What It's Used For |
|---|---|
| Author handle & name | Displayed on reply cards, used for starring/flagging users |
| Profile image | Avatar shown on reply cards |
| Reply text | Main content of the card, used for keyword filtering |
| Engagement metrics | Replies, retweets, likes, views (Pro feature) |
| Parent reply | Who this reply is responding to (↳ @handle indicator) |
| Verified status | Shows verification badge on card |
| Media presence | Shows media badge if reply contains images/videos |
Important Notes
Replies Must Be Loaded
ThreadTrak can only capture replies that X has loaded into the page. Deep threads require scrolling to trigger X's pagination. If you don't scroll, ThreadTrak only sees the first batch of replies.
Data is Session-Based
Mapped conversation data is held in memory during your session. When you navigate to a different page or close the tab, the tree resets. Your bookmarks, notes, and starred users are saved permanently.
No API Access Required
ThreadTrak doesn't need your Twitter login or API keys to map conversations. It reads what's already visible on the page. This means no rate limits and no extra permissions beyond what Chrome extensions normally need.