Why Wishlist Velocity Matters

Wishlist velocity is the rate at which a Steam game gains wishlists over a defined period. It can help a developer understand whether a festival, trailer, announcement or creator campaign produced meaningful interest. It is not an official Steam ranking score, and there is no universal weekly target that predicts success for every game.

What wishlist velocity actually measures

The simplest calculation is:

Wishlist velocity = new wishlist additions ÷ number of days measured

Steamworks also reports deletions, purchases and gifts associated with wishlists. For day-to-day marketing analysis, record both gross additions and net movement. A campaign that adds many wishlists but also creates unusual deletions later may have reached an audience that was not well matched to the game.

Always label the time period. “Thirty wishlists per day during Next Fest” and “thirty wishlists per day during a quiet month” describe different conditions. The rate becomes useful when it is compared with the same game’s baseline and campaign history.

Why the rate matters more than an isolated total

A total wishlist count is cumulative. It does not explain when interest arrived or what caused it. Velocity provides context:

A short spike can reveal that a trailer, demo or creator mention reached players.
A sustained increase can show that several channels are working together.
A fall towards the old baseline can reveal that an event’s effect was temporary.
Differences by territory or language can guide localisation and outreach.

These observations help with marketing decisions, but they are not proof of future sales. Wishlists can be old, duplicated across campaigns or created by players waiting for a deeper discount. Release timing, price, game quality, competition and the accuracy of the store-page promise all affect what happens later.

What Valve says about wishlists and visibility

Valve’s visibility documentation makes an important distinction: with limited exceptions such as Popular Upcoming, wishlists are not a direct factor in a game’s algorithmic visibility on Steam. Store-page traffic and conversion rate are also not direct visibility factors.

Wishlists remain valuable because Steam may notify those players when the game releases, leaves Early Access or receives a qualifying discount. A growing wishlist audience can therefore increase the number of interested players who hear about a launch, but developers should not describe wishlist velocity as a secret visibility formula.

Steam says player purchases and play matter strongly to visibility after release. Tags and supported languages also help the store match a game with suitable players. The practical goal is to build genuine demand and describe the game accurately, not to manufacture a particular graph shape.

How to measure wishlist velocity properly

Choose a baseline. Record at least a representative quiet period before the campaign.
Mark campaign dates. Note festivals, announcements, demos, creator coverage, paid adverts and major store-page changes.
Use consistent periods. Compare daily with daily or weekly with weekly; do not compare a festival day with a normal month without context.
Track the source. Use Steamworks UTM Analytics for external links so you can compare trusted visits and attributed actions.
Keep raw numbers. A large percentage increase from a tiny baseline can still mean only a handful of players.
Allow for reporting limits. Privacy choices and cross-device journeys mean attributed campaign data is not a complete count of everyone influenced.

Use a campaign annotation table

A simple record makes the data much easier to interpret:

date and campaign name;
channel and audience;
asset or message used;
store-page visits;
new wishlist additions and deletions;
demo players or other relevant actions;
outside events that may have affected traffic;
what the team learned.

For external campaigns, create consistent UTM names before publishing links. Steamworks can report visits and attributed wishlist actions for signed-in users within its documented attribution window. Use the report to compare sources, while recognising that some people will later search for the game in another browser or device and cannot be connected to the original click.

Avoid universal wishlist benchmarks

Claims such as “every indie game needs a fixed number of wishlists per week” ignore genre, price, market size, release date and campaign reach. A niche strategy game and a broad multiplayer title do not need identical audiences. A game with strong organic discovery cannot be compared directly with one receiving paid traffic.

Use three benchmarks instead:

Your baseline: the game’s normal rate without a major campaign.
Your previous campaigns: results from comparable announcements, festivals or creator outreach.
Your qualified audience: whether the people arriving understand the game and take relevant actions.

This approach produces decisions you can act on. If one creator sends fewer visits but more wishlist additions than a broad advert, that may be the better audience. If a festival produces a spike followed by strong demo feedback, investigate what worked. If traffic rises but wishlists do not, review the promise made by the external message and the first screen of the Steam page.

Questions wishlist velocity can answer

Did this campaign create more interest than our usual activity?
Which source brought the most qualified visitors?
Did the new trailer or announcement improve response from the intended audience?
How quickly did interest return to baseline after an event?
Which territory or language deserves more attention?

Questions it cannot answer alone

How many copies will the game sell?
Whether Steam will feature the game in a specific placement.
Whether players will enjoy or recommend the finished game.
Why a wishlist was added or later removed.
Whether one campaign caused every later purchase.

The useful takeaway

Wishlist velocity matters because it turns a cumulative total into a time-based signal. Use it to compare your own campaigns, spot changes in interest and decide where to spend the next week of marketing work. Do not turn it into a fabricated algorithm score or a guaranteed sales forecast.

Pair wishlist reporting with Steam traffic data, UTM Analytics, demo feedback and honest store-page testing. The result will be a clearer view of which activities are bringing the right players closer to your game.

Official sources

Josh

See Full Bio