How do I compare wishlist growth week over week without reacting to noise?

Compare complete, equally sized weeks using the same definitions. Look at additions and deletions separately, then inspect the daily pattern and marketing activity behind the change. Use the comparison to choose an investigation or next action. A larger total is useful information, but it does not explain its own cause or establish a lasting trend.

Start with two complete weeks

Pick a consistent reporting week and timezone. Save both date ranges so another team member can reproduce the comparison.

Valve says wishlist reporting updates daily for the previous date. A missing current day is therefore not automatically a tracking failure. Check report availability before comparing a partial week with a full one. Valve: Wishlist Reporting.

If this week's report is incomplete, compare it with the same completed weekdays from last week and label it as a partial comparison. Keep that separate from your full-week review.

Show counts before percentages

Here is a fictional example for an unreleased game, with no purchase activity:

Measure	Previous week	Latest week	Change
Wishlist additions	140	175	+35 / +25%
Wishlist deletions	20	40	+20 / +100%
Additions minus deletions	120	135	+15 / +12.5%

The additions headline sounds stronger than the change after deletions. Both are useful, but they answer different questions. Neither explains why deletions increased.

Keep the counts visible because percentages can exaggerate small changes. Going from two additions to four is a 100% increase and only two extra additions. If the previous period is zero, show the absolute change instead of an undefined percentage.

For a released game, inspect purchase activity as well. Do not assume additions minus deletions alone describes every change in the outstanding wishlist balance; Steam's reporting distinguishes additions, purchases and deletions. Valve: Wishlist Reporting.

Open the week before calling it a trend

Those 35 additional wishlists might be spread across seven days, or concentrated on one day after a creator video. The total is identical; the follow-up decision is different.

If one day explains most of the change, inspect its events and source reports. If several comparable weeks show a sustained change, investigate what changed in the ongoing workflow or audience. This is descriptive review, not a statistical significance test.

Chris Zukowski's historical analysis compared promotional spike periods with quieter periods for three high-wishlist games. It is useful context for why the shape of growth matters, but the selected cases do not provide a universal weekly target. How To Market A Game: How much promotion should you be doing?.

Avoid silently removing spike days to make a smoother trend. If you compare ordinary periods separately, state which days you excluded and why. A festival or campaign is part of the commercial result even when it is not part of the recurring baseline.

End with one decision

Use this short review record:

What changed? Additions rose by 35; additions minus deletions rose by 15.
Where did it happen? Most of the increase occurred on the day of a video.
What else happened? A paid campaign overlapped that day.
What remains uncertain? The two activities cannot be separated from the weekly totals.
What happens next? Review their individual source reports; record the finding before the next campaign decision.

Assign that next action to a person and a date. The purpose of the weekly review is to improve the next decision, not to manufacture a verdict on every fluctuation.

How Coal helps

Coal's wishlist timeline exposes additions, deletions and marketing events for this review. Its balance measure uses additions minus deletions over the selected range. A saved review with an owner, conclusion and follow-up date is a workflow recommendation here, not a claim that Coal stores that full record today.