Research attention

ATTN shows the tickers participating Gloom users research, with a board, history, sector and country totals, and evidence. Open a ticker in DES, FA, G or NEWS to investigate. Gloom Trending in DES and the home pane uses the same released data.

Attention Counts is a separate, optional setting. It starts off, including for users who already enabled Usage Counts. Collection and publication are also disabled on the server until the privacy review and an explicit operational activation. There is no historical activity import. Until enough people choose to contribute, the board shows a collecting or disabled state.

What a count means

One verified account researching one recognized listing during one UTC hour contributes one researcher-hour. Opening it repeatedly, in several functions or on several devices does not increase that hourly contribution. The eligible actions are deliberate description, chart, quote and option-chain opens and watchlist additions. Restored panes, background quote polling and bots do not count. Only known, unambiguous listings are accepted; the identifier includes its exchange. This works for international listings supported by the stored instrument catalog, without a US-only ticker rule.

A ticker-hour must have at least 20 distinct contributors to be released. Counts are rounded down to multiples of five and published at least one hour after the hour ends. They are an observed subset of Gloom users, not population estimates, a count of unique people over a day, or a measure of buying and selling. The setting may use a stricter threshold or a longer delay.

Windows and comparisons

• Now is the latest eligible completed UTC hour.
• Today covers the UTC day through that hour.
• Week covers the trailing 168 completed hours.

Day, week, sector and country results add only released ticker-hours. A missing hour can be suppressed, unobserved or unavailable; it never means zero. Sector and country refer to the instrument, never to its contributors. Shares are shares of released research units and change with the published coverage.

Abnormal attention compares the latest eligible hour with the ticker’s same-UTC-hour published history over 28 days. It needs at least 14 comparable released hours; a constant rounded baseline has no defined z-score. The z-score stays unavailable until enough comparable periods exist, and suppressed hours are excluded rather than imputed. Price changes, relative volume and news provide separately timestamped context. They do not establish a causal relationship to research activity. Unavailable market context remains blank.

Evidence and access

Every released observation carries its time window, units, methodology version and privacy policy parameters. Counts are first-party observations, not extracted quotations or model estimates. Publication is immutable: an hour is finalized once, including suppressed buckets. There are no user, device or session identifiers in the aggregate tables and no filters for contributor cohorts or arbitrary time windows.

Free includes the first three published rows per section and the latest point. Pro adds the complete board and up to 29 days of hourly history. Published hourly storage is retained for 35 days; a permanent hour-finalization record prevents expired hours from being republished. Symbol requests follow the same global preview selection; the screener's Research attention and Abnormal attention fields require Pro.

REST: GET /cloud/attention?window=now, GET /cloud/attention?window=today, GET /cloud/attention?window=week, and GET /cloud/attention/AAPL?window=today. Responses carry status, release time, coverage, privacy parameters and entitlement. The MCP market.attention tool returns the same research with provenance and requires Pro.

Privacy choices

Turn Attention Counts on or off in Settings. Browser Do Not Track and Global Privacy Control override it. The app batches only in memory, clears unsent counts on opt-out or sign-out, and never persists a ticker activity log. Disabling the setting cannot recall requests already sent. The Privacy Policy explains temporary contribution deduplication, retention and consent withdrawal.