> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/tracker/notifications.md).

# Notifications

**Tracker notices things you didn't have to watch for — but you still decide what's worth acting on.**

Tracker notifications and alerts surface new wallet activity and Twitter/X signals so you don't have to refresh the panels manually. Notification behaviour depends on your account state, selected settings, and which item triggered the alert.

{% hint style="success" %}
**Alerts are inputs, not orders**

A notification means *something happened*. It doesn't mean you should trade. Always verify in Research or Trading first.
{% endhint %}

## Wallet Notifications

When a tracked wallet moves, the activity surfaces in the panel. Each row exposes:

* **Type** — buy, sell, transfer, swap, etc.
* **Token** — what was moved.
* **Amount** — size of the move.
* **Market cap** — context at the time.
* **Transaction reference** — link to the on-chain record.
* **Time** — when it happened.

If the activity looks important: **open the token in** [**Research**](/graphdex-docs/research/research-overview.md) **or** [**Trading**](/graphdex-docs/trading/trading-overview.md) and verify the current market state before acting. Wallet activity from 10 minutes ago can be stale by the time you see it.

## Twitter/X Alerts

The Twitter/X Tracker exposes an **Alerts tab** for tracked-account events. Alerts can include:

* **Tweets** — the post itself.
* **Sentiment information** — automated sentiment classification.
* **Confidence value** — how certain the sentiment / signal classifier is.
* **Empty states** — when no alerts are currently surfaced.

**Treat sentiment and confidence as starting signals**, not trading instructions. A "high-confidence positive" classification is a hypothesis to verify, not a green light.

## Managing Noise

A tracker that fires constantly is a tracker that gets ignored. Keep the signal-to-noise ratio high:

* **Settings** — adjust thresholds and routing.
* **Tracked lists** — trim handles and wallets you no longer read.
* **Search** — find specific items quickly instead of scrolling.
* **Delete controls** — remove the chronic offenders.
* **Boost controls** — surface the ones that matter most.

If a single wallet or account is creating too much noise, **remove it or lower its priority** — don't disable all alerts in response to one bad actor.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/m1zZKHwtJxpa0f4cJYJD"><strong>Wallet Tracker</strong></a></td><td>Source for wallet-side notifications.</td><td><a href="/files/AnuIRgx3Ju4HdXa1cEG3">/files/AnuIRgx3Ju4HdXa1cEG3</a></td></tr><tr><td><a href="/pages/2PlFU4Pt3OKOoBaNMfAK"><strong>Twitter/X Tracker</strong></a></td><td>Source for social-side alerts.</td><td><a href="/files/OVXlon60XqRGRA8pZwho">/files/OVXlon60XqRGRA8pZwho</a></td></tr><tr><td><a href="/pages/XJTcByJsbupiZnUUjdb4"><strong>Using Tracker with Research and Trading</strong></a></td><td>The verification step after an alert lands.</td><td><a href="/files/JBN29ujDJykAmMONwLxK">/files/JBN29ujDJykAmMONwLxK</a></td></tr></tbody></table>

{% hint style="info" %}
The fastest way to keep alerts useful is to prune the watchlists weekly — every handle and wallet that doesn't earn its slot should be removed.
{% endhint %}

## FAQs

<details>

<summary>How fast are notifications?</summary>

Near real-time, subject to indexing latency. Wallet activity surfaces seconds after the on-chain inclusion; tweets surface as the Twitter Tracker pulls them.

</details>

<details>

<summary>Why do I see alerts for activity that happened earlier?</summary>

Indexing or fetch lag — particularly during high-volume windows. The timestamp on the alert reflects when the activity happened on-chain, not when it surfaced.

</details>

<details>

<summary>Can I get notifications outside GraphDex?</summary>

Notification routing options depend on the current product version. Inside the terminal is the canonical channel; external delivery may or may not be exposed.

</details>

<details>

<summary>How do I silence a noisy tracked item?</summary>

Lower its boost, remove it from the list, or adjust the relevant Tracker setting. Disabling all alerts in response to one source is rarely the right answer.

</details>

<details>

<summary>What's the difference between a tweet alert and a sentiment alert?</summary>

A tweet alert surfaces the post itself; a sentiment alert layers automated classification on top (sentiment + confidence). Both reference the same underlying tweet — sentiment is a derived signal.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://graphdex-1.gitbook.io/graphdex-docs/tracker/notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.