> For the complete documentation index, see [llms.txt](https://docs.taligate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taligate.com/alerts-and-filters.md). # Alerts and filters When a wallet you track makes a trade, Taligate sends you an alert. Each alert names the trader (their Polymarket public name, or the nickname you gave the wallet), the market and outcome, the entry price, the current position value, and the PnL. For a closed position, the PnL comes from Polymarket's own settlement data rather than the last saved snapshot, so the number is accurate even if you weren't watching. ## Four event types Taligate watches for four kinds of position changes: * **New** - the wallet entered a market it had no position in. * **Closed** - the wallet fully exited a position. * **Increased** - the wallet added shares to an existing position. * **Decreased** - the wallet trimmed an existing position. A price moving on its own, with no trade, never triggers an alert. The bot diffs the actual share counts between each poll, so you only hear about real activity. ## Filters Most users don't want an alert for every tiny $2 position or a 0.1-share tweak. Filters let you set a floor. A change has to clear all active filters before an alert fires. There are four thresholds: | Threshold | What it checks | | ------------------------ | ------------------------------------------------------------- | | Min position value (USD) | The position must be worth at least this much | | Min size change (%) | The change in position size must be at least this percentage | | Min absolute shares | The change must involve at least this many shares | | Min PnL (USD) | For closed positions, the realized PnL must reach this amount | Setting any threshold to **0** turns it off for that threshold. For example, if you set min position value to $500 and min size change to 10%, an alert fires only when both conditions are met. If you set min PnL to 0, closed-position alerts aren't filtered by PnL at all. ### Account defaults and per-wallet overrides Your thresholds work on two levels. **Account defaults** live in `/settings`. They apply to every wallet you track unless you override them on a specific wallet. So if you set your default min position value to $500, all your wallets use $500 unless told otherwise. **Per-wallet overrides** live on each wallet's Alerts card (tap "Alerts" in `/list`). Each value shows as either "inherited" (using your account default) or "custom" (you've set something specific for this wallet). A Reset button clears the custom values and reverts to the account default. This matters when you want tighter filters on a low-conviction wallet you're following casually, or no filters at all on a whale you want to see everything from. ### Event-type toggles Beyond thresholds, you can toggle entire event types on or off. If you don't care about small trims, you can disable Decreased alerts globally. The four toggles (New, Closed, Increased, Decreased) live in `/settings` and apply across every wallet you track. Per wallet, you can still mute a wallet completely with the Mute button or tune its thresholds, but the event-type switches themselves are account-wide. ## Consensus alerts Consensus is for when you track many wallets and want to know when a crowd of them converges on the same trade. Set a number N in `/settings`, and when N or more of your tracked wallets hold the same market outcome, you get a single consensus alert instead of a stream of separate ones. Consensus is off by default (N = 0). Set it to something like 3 or 5 depending on how many wallets you track. Once triggered, the bot doesn't repeat the consensus alert for the same outcome unless the condition resets. ## The /settings screen `/settings` is your account-level control panel for all of the above. It shows: * The four event-type toggles (New / Closed / Increased / Decreased) * The four default thresholds (min value, min size change %, min absolute shares, min PnL) * The consensus number (N) Each row explains what it controls. Changes here apply immediately to every wallet using inherited values. Per-wallet Alerts cards override the defaults for that wallet only. A practical starting point: set min position value to $500 and min size change to 10%. That cuts out noise while keeping you informed about anything meaningful. Adjust from there based on the wallets you follow. --- # 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://docs.taligate.com/alerts-and-filters.md?ask=&goal= ``` `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.