Steam Monitor — Track Game Discounts, Price Changes & Review Movements

Snapshot scrapers tell you what Steam looks like right now. This Actor tells you what changed since your last run: a game you track just went on sale, a price changed in your region, a review score moved, a new title entered the top sellers — as structured change events with field-level before/after diffs.

Built on Steam's public store JSON endpoints. No login, no browser, no proxies — fast and stable.

What it does

• Watch store lists — specials (discounts feed), top_sellers, new_releases, coming_soon. Every run diffs the list against the previous run: new_game (e.g. a fresh discount appeared), removed_game (sale ended), game_changed (discount percent moved).
• Watch specific games — pass Steam app IDs. Tracks regional price, discount, review score & verdict (e.g. "Very Positive"), review count, positive ratio, and release status. A game_changed event with discountPercent: null → 60 is your wishlist alert.
• Regional pricing — set any country code (us, de, pl, ua, ...) and monitor prices in that region.

Who uses this

• Deal hunters & communities — price-drop and new-discount feeds for Discord bots, deal sites, newsletters.
• Game developers & publishers — competitor pricing moves, review score trends, top-seller entries in your genre.
• Market analysts — top-seller churn and discount depth over time, straight into Sheets or a webhook.

Output example

{
  "type": "game_changed",
  "source": "watch",
  "appId": 1091500,
  "name": "Cyberpunk 2077",
  "url": "https://store.steampowered.com/app/1091500/",
  "changes": [
    { "field": "discountPercent", "before": null, "after": 70 },
    { "field": "finalPriceCents", "before": 5999, "after": 1799 }
  ],
  "detectedAt": "2026-08-04T10:00:00.000Z"
}

Input

Field	Description
lists	Store lists watched as sets: specials, top_sellers, new_releases, coming_soon
appIds	Steam app IDs tracked with field-level diffs
countryCode	Region for pricing
monitorId	State namespace shared between runs

Reliability

Public JSON endpoints only — the same ones the Steam store frontend uses. Strict schema validation on every item; the run fails loudly rather than storing garbage. Noisy counters (review totals) are banded so you only see meaningful movement. First run stores a baseline; change events start from run two.

Scheduling

Run every few hours via an Apify Schedule and pipe events to Slack, Discord (webhook), email, or Google Sheets through Apify integrations. Quiet runs cost almost nothing.