Wishlist Notifier

Steamworks wishlist reporting guide

How often do Steam wishlist statistics update?

Steam wishlist statistics update daily, not in real time. The newest complete date in the Steamworks report is normally yesterday.

Short answer

Valve says the Steamworks wishlist report updates daily for the previous date. Its wishlist reporting API is refreshed at least once per day. You should not expect a new wishlist to appear immediately after someone adds your game.

What daily reporting means

When you open the wishlist report on March 2, the latest complete data is normally March 1. The current date is excluded because Steam is still collecting and processing it. This makes the report useful for day-by-day comparison, but not for live campaign monitoring.

The report portal and API describe the same activity with slightly different timing language:

  • The Steamworks Wishlist Reporting page says data is updated daily for the previous date.
  • The GetAppWishlistReporting API documentation says data is refreshed at least once per day.
  • The API date parameter is GMT-bounded.

Why today may be blank or incomplete

A missing current-day figure is expected. It does not show that additions stopped, and repeatedly refreshing Steamworks will not turn the report into a live counter. Wait for the next daily update before comparing the date with earlier results.

Time zones can also make the newest date look unusual near midnight. The API defines its requested date in GMT. The report’s downloadable CSV uses DateLocal for the Pacific Time date on which a wishlist purchase occurred. Check which field and interface you are using before aligning wishlist data with analytics from another system.

How often to check the report

Once per day is enough for normal tracking. Checking more often can tell you that an update has arrived, but it will not create fresher source data. For a weekly view, record each closed day and compare seven complete reporting dates rather than including an unfinished current date.

How often to query the API

Valve’s API guidance gives a simple pattern. On June 1, query May 31 and June 1. On June 2, query June 1 and June 2. Once an older date has closed, there is normally no reason to keep requesting it because wishlist data does not have the settlement delay associated with financial transactions.

This differs from some sales data, where older dates can change because payments settle later. For wishlist reporting, store completed dates and concentrate new requests on the latest dates.

When a daily figure looks wrong

First confirm that you are looking at the latest closed reporting date. Then check whether the selected App ID and partner account are correct. If the API returns no normal summary, confirm that the date is within the app’s available range and that the Financial API Group key is valid.

A zero is a reported value. A missing or unavailable date is not necessarily zero. Keep that difference intact when importing the data into a spreadsheet or database.