12 Free Steam Wishlist Analytics Tools for Next Fest Week - 2026

If you searched steam wishlist analytics tools during Steam Next Fest week, you do not need another post-fest velocity essay or a paid dashboard pitch. You need a free fest-week toolkit: Steamworks Wishlist Action Summary CSV, UTM Analytics, local chart apps that never upload your file, a UTM link builder, and a dated receipt before anyone pastes “wishlists are exploding” into Discord.

This listicle is that toolkit. It is not the post-fest daily export / wishlist velocity tools listicle (D+14 after fest). It is not the hour-one demo funnel snapshot evening (one-evening CSV ritual). It is twelve free tools for measuring wishlist movement during Next Fest week — especially after Press Preview traffic and before/through the Oct 19–26 public window.

Why this matters now

Steam Next Fest: October 2026 runs October 19–26 after Press Preview opened October 8. The Upcoming Steam Events calendar stacks Cooking Fest and Scream V around the same month. Creators will spam links. Wishlists will move. Without a free measurement stack, your team will argue from screenshots.

Direct answer: Adopt a four-tool minimum this week — Steamworks Wishlist Action Summary CSV, Steamworks UTM Analytics, one local CSV chart app, and a UTM link builder — then expand to the full twelve before you claim “fest attribution.”

Who this list is for

Time: 25 minutes to pick the four-tool minimum; 60–90 minutes for a full fest-week smoke on a throwaway export.
Honest limit: Steamworks privacy rules hide low-volume UTM combinations. Tracked visits require signed-in Steam users. Third-party charts cannot invent data Steamworks never exported.

Non-repetition

Pair demo metadata checklists at 15 free Next Fest October demo metadata resources and the Steam guide hub. If Steam Input defaults blocked an upload, see demo upload rejected - missing Steam Input default config.

Selection criteria (how a tool earned a slot)

A tool is in only if all of these are true:

1. Free tier usable without a credit card for the fest-week job (or fully open source / native Steamworks).
2. Wishlist or UTM measurement is a primary job — not a random marketing SaaS with a wishlist checkbox.
3. Works with Steamworks exports or Steam store URLs without claiming to replace partner permissions.
4. Honest limits can be stated in one sentence (privacy thresholds, signed-in tracking, local-only CSV, etc.).
5. Useful during Next Fest week (pre-open tagging, live-week reads, or immediate post-open charts) — not only D+30 BI.

Four-tool minimum (do this before the other eight)

Latch the receipt at the end only when these four are live for your AppID.

Tool 1 - Steamworks Wishlist Action Summary CSV

Type: Native Steamworks export
URL: Steamworks → Financial / wishlist reports for your AppID (Wishlist Action Summary → view as CSV)
Fest-week job: Ground truth for daily Adds, Deletes, PurchasesAndActivations, Gifts.

How to use in fest week

1. Export the per-game daily breakdown — not the studio-wide summary.
2. Confirm headers include DateLocal,Adds,Deletes,PurchasesAndActivations,Gifts (column names may vary slightly; reject the wrong file).
3. Save as wishlist-action-YYYY-MM-DD.csv in your evidence folder.
4. Re-export daily at the same local hour during Oct 19–26.

Honest limit: Steamworks UI paths move; if you grab the wrong CSV (all games summary), your chart will lie. HowToMarketAGame documents the common “click the game name again” trap.

Pair with: Tools 3–4 for charting; Tool 2 for source attribution.

Tool 2 - Steamworks UTM Analytics

Type: Native Steamworks dashboard + CSV
URL: UTM Analytics (Steamworks Documentation)
Fest-week job: See which utm_source / utm_campaign combinations drove tracked visits and wishlist conversions.

How to use in fest week

1. Confirm your account has View Marketing Traffic Data permission.
2. Open Marketing & Visibility → UTM Analytics for the AppID.
3. Use Test a UTM Link before creator blasts.
4. Download CSV for the fest window; note visit counts refresh hourly and conversions finalize on a delay (Steamworks: conversions finalized 4 days after the visit).

Honest limit: Only Tracked Visits (signed-in Steam users in that browser/app path) get conversion attribution. Low-volume UTM combinations may be hidden for privacy. Demo downloads alone are not counted as base-game UTM conversions.

Pair with: Tool 6 (link builder); Tool 1 (volume vs source).

Tool 3 - IndiePilot free Wishlist CSV Chart

Type: Free browser chart (local file)
URL: https://indiepilot.dev/tools/wishlist-csv-checker/
Fest-week job: Drop your Wishlist Action Summary CSV and see daily adds/removals and running total without uploading the file to a server (per their FAQ: processed in-browser).

How to use in fest week

1. Export Tool 1 CSV.
2. Open the chart page; load the file locally.
3. Screenshot the Next Fest date band for Discord stand-up.
4. Optional: use area-select style workflows in similar tools to compare fest days — IndiePilot focuses on clean daily charts and missing-date detection.

Honest limit: Convenience layer only. Steamworks remains source of truth. Paid IndiePilot workspace/extension features are out of scope for this free listicle slot — this entry is the free CSV chart page.

Pair with: Tool 1; Tool 4.

Tool 4 - HowToMarketAGame Steam Wishlist Chart

Type: Free browser chart
URL: https://howtomarketagame.com/wishlists/
Fest-week job: Chart Wishlist Action Summary CSVs, compare two games, merge history, and area-select multi-day fest windows (including Next Fest) for totals and average daily rates.

How to use in fest week

1. Follow their Steamworks download steps carefully (per-game daily file).
2. Load CSV; Shift-drag to select the fest date range.
3. Use Avg Daily in the selection tooltip as a baseline vs pre-fest days.
4. Compare against a prior fest CSV if you have one.

Honest limit: Still depends on correct Steamworks export. Comparison mode is for learning — do not treat rival CSVs as your diligence packet unless you own them.

Pair with: Tool 1; Tool 3 as alternate chart UI.

Tool 5 - Steamworks Traffic / Marketing reports (native)

Type: Native Steamworks
URL: Steamworks Marketing & Visibility traffic reports for your AppID
Fest-week job: Cross-check page visits vs wishlist movement when UTM and wishlist CSVs disagree.

How to use in fest week

1. Open traffic breakdown for the fest dates.
2. Note Steamworks’ own warning: UTM Analytics totals and Traffic Breakdown totals will not always match (different tracking + cookie preferences).
3. Write one sentence in the receipt: “Visit discrepancy expected — using Wishlist CSV for volume, UTM for tagged campaigns.”

Honest limit: Do not spend fest open hour reconciling every visit delta. Latch the discrepancy note and move on.

Pair with: Tools 1–2; Steamworks UTM docs.

Tool 6 - Kedolo Steam UTM link builder

Type: Free browser builder
URL: https://kedolo.com/tools/steam-utm
Fest-week job: Paste your store URL; generate UTM-tagged links for Discord, streams, and press kits without hand-typos.

How to use in fest week

1. Paste https://store.steampowered.com/app/YOUR_APP_ID.
2. Set utm_campaign=nextfest_oct2026 (or similar).
3. Create distinct utm_source values per creator/platform.
4. Test each link in Steamworks Test a UTM Link.

Honest limit: Builder does not show results — Steamworks UTM Analytics does. Kedolo states links are built in-browser.

Pair with: Tool 2; Tool 12 creator sheet.

Tool 7 - Hand-built UTM links (notepad + Steamworks rules)

Type: Free / zero install
URL: Rules in UTM Analytics docs
Fest-week job: Fallback when you distrust builders; guarantee utm_source or utm_campaign is present.

Example shape

https://store.steampowered.com/app/YOUR_APP_ID?utm_source=discord&utm_campaign=nextfest_oct2026&utm_medium=social

Honest limit: Typos create orphan campaigns. Always Test a UTM Link.

Pair with: Tool 2; Tool 6.

Tool 8 - Steam Wishlist Pulse (open source)

Type: Open-source monitor
URL: https://github.com/hortopan/steam-wishlist-pulse
Fest-week job: Self-host wishlist polling with alerts (Telegram/Discord) so you are not refreshing Steamworks every hour.

How to use in fest week

1. Read the repo README for API/auth requirements before promising alerts.
2. Run only if someone on the team can own the host for Oct 19–26.
3. Keep Steamworks CSV as nightly truth even if Pulse alerts fire.

Honest limit: Ops cost is real (host + secrets). If nobody can babysit a binary, skip to Tools 3–4 and stay CSV-native.

Pair with: Tool 1; crash triage culture from festival crash triage.

Tool 9 - LibreOffice Calc or Google Sheets (free spreadsheet)

Type: Free spreadsheet
URL: https://www.libreoffice.org/ or Google Sheets
Fest-week job: Pivot Adds/Deletes by date; compute fest-day net wishlists; share a read-only tab with the lead.

How to use in fest week

1. Import Tool 1 CSV.
2. Add columns: net = Adds - Deletes (and note purchases/activations separately).
3. Highlight Oct 19–26 rows.
4. Chart net wishlists; paste PNG into Discord.

Honest limit: Spreadsheets do not fix bad exports. Name the file with UTC date.

Pair with: Tools 1, 3, 4.

Tool 10 - jq (or Miller) for CSV sanity

Type: Free CLI
URL: https://jqlang.github.io/jq/ (or https://miller.readthedocs.io/)
Fest-week job: Diff yesterday vs today exports; catch missing dates before stand-up.

How to use in fest week

1. Keep two CSVs: wishlist-action-prev.csv and wishlist-action-today.csv.
2. Count rows / max date; fail the morning ritual if the date gap is >1 day during live fest.
3. Optional: emit a tiny JSON summary into the receipt folder.

Honest limit: CLI is for developers. Beginners can use Tool 3 missing-date detection instead.

Pair with: Tool 1; hour-one funnel evening if you also track demo launches.

Tool 11 - Steamworks “Test a UTM Link” + store widget UTM

Type: Native Steamworks + docs
URL: UTM Analytics · Store widgets
Fest-week job: Validate links and, if you embed widgets on a landing page, append UTM parameters to the iframe URL.

How to use in fest week

1. Test every creator link before send.
2. If you use sale-page or widget embeds, confirm UTM passthrough behavior from the docs (sale-page passthrough noted since 2025).
3. Do not invent affiliate payout schemes on UTM — Steamworks cautions hard against abuse-prone reward programs.

Honest limit: Age gates still record the UTM click; conversions still need signed-in tracked visits.

Pair with: Tools 2, 6, 7.

Tool 12 - Fest-week creator UTM sheet (template)

Type: Free template (you own the sheet)
URL: n/a — create once, reuse
Fest-week job: One row per creator/platform with final URL, utm_source, owner, and “tested in Steamworks” checkbox.

Honest limit: A sheet is not analytics. It prevents untagged chaos so Tool 2 can work.

Pair with: Press kit / outreach tools; final-nine-days ops lock.

Criteria → tool map (scannable)

Baseline before open (Oct 10–18)

Do not wait until Oct 19 noon to discover your CSV path is wrong.

1. Export one Wishlist Action Summary CSV today and chart it (Tools 1 + 3 or 4).
2. Write the pre-fest 7-day average daily Adds into the receipt notes.
3. Build and test every creator UTM link (Tools 6/7 + 11).
4. Confirm View Marketing Traffic Data permission on a backup Steamworks user.
5. Decide who runs the 45-minute ritual each fest morning — name them in Discord.

Pass: You can produce yesterday’s net wishlists and top utm_source in under ten minutes without asking where the export lives.

Fest-week ritual (45 minutes)

Run this once per day during Oct 19–26. Compare each fest day to the pre-fest baseline so a “spike” is a number, not a vibe.

CapEx four-liner

1. Steamworks exports are source of truth; third-party charts are conveniences.
2. We will not buy a BI seat for fest week if the four-tool minimum answers the question.
3. We will not claim UTM attribution for signed-out social in-app browsers without reading Tracked Visits limits.
4. We will not invent affiliate payouts on UTM parameters.

Common mistakes

1. Exporting the studio-wide wishlist summary instead of per-game daily rows.
2. Reading UTM Total Visits as if they were all convertible Tracked Visits.
3. Changing utm_campaign spelling mid-fest and splitting your own data.
4. Uploading private CSVs to random “analyzers” that are not local-first.
5. Skipping Test a UTM Link, then blaming Steamworks.
6. Comparing Traffic Breakdown to UTM totals without the docs’ discrepancy note.
7. Treating demo installs as UTM base-game conversions.
8. Letting creators use naked store links “for cleaner URLs.”
9. Waiting until Oct 19 noon to build the creator sheet.
10. Confusing this fest-week toolkit with the post-fest velocity listicle.

Discord paste

Fest-week wishlist analytics (free stack)
Four-tool minimum: Steamworks Wishlist CSV + UTM Analytics + local chart + UTM builder
AppID:
CSV date:
Net wishlists (fest window to date):
Top utm_source:
Receipt: fest_week_wishlist_analytics_receipt_v1.json as_of 2026-10-10
Steamworks UTM docs pasted: YES

Receipt - fest_week_wishlist_analytics_receipt_v1.json

{
  "receipt": "fest_week_wishlist_analytics_receipt_v1",
  "as_of": "2026-10-10",
  "primary_keyword": "steam wishlist analytics tools",
  "app_id": "REPLACE_ME",
  "four_tool_minimum": {
    "steamworks_wishlist_csv": false,
    "steamworks_utm_analytics": false,
    "local_csv_chart": false,
    "utm_link_builder": false
  },
  "tools_in_use": [],
  "fest_window": {
    "press_preview_start": "2026-10-08",
    "next_fest": "2026-10-19/2026-10-26"
  },
  "notes": "Steamworks is source of truth; charts are conveniences",
  "outbound_docs": [
    "https://partner.steamgames.com/doc/marketing/utm_analytics",
    "https://partner.steamgames.com/doc/marketing/upcoming_events/nextfest/2026october"
  ]
}

Key takeaways

1. Fest week needs a free wishlist + UTM stack now — not only post-fest velocity tooling.
2. Steamworks Wishlist Action Summary CSV is volume ground truth.
3. UTM Analytics is campaign ground truth — with Tracked Visits and privacy limits.
4. Adopt a four-tool minimum before buying anything.
5. Prefer local CSV charts (IndiePilot free page / HowToMarketAGame) over mystery uploads.
6. Kedolo or hand-built UTM tags every creator link before open.
7. Traffic vs UTM totals will disagree — document it once.
8. Open-source alert daemons are optional; CSV discipline is not.
9. Keep a creator UTM sheet so Tool 2 has clean dimensions.
10. Do not confuse this URL with hour-one funnel or post-fest velocity posts.
11. File fest_week_wishlist_analytics_receipt_v1.json and paste Discord daily.
12. Cite UTM Analytics and October Next Fest next to claims.

FAQ

What are the best free Steam wishlist analytics tools for Next Fest week?

Start with Steamworks Wishlist Action Summary CSV, Steamworks UTM Analytics, one local CSV chart (IndiePilot free chart or HowToMarketAGame), and a UTM link builder. Expand to the other tools in this list only if you still have unanswered questions.

Does Steamworks include UTM wishlist conversion data?

Yes. UTM Analytics reports wishlist, purchase, and activation conversions for tracked (signed-in) visits, with privacy thresholds and timing delays documented by Valve.

Can I trust third-party wishlist charts?

Only as conveniences on top of your Steamworks export. Prefer tools that process CSVs locally. Never treat a third-party chart as more authoritative than partner data.

Why do my UTM visits not match my traffic report?

Steamworks documents that UTM Analytics and Traffic Breakdown track different things and are affected by cookie preferences. Record the discrepancy and keep moving during fest week.

Do demo installs count as UTM conversions for the base game?

Steamworks states demo/DLC downloads that do not include the base game are not currently counted as conversions for base-game UTM links.

How is this different from the post-fest wishlist velocity listicle?

That URL owns daily velocity after fest. This URL owns the free toolkit during Next Fest week (tagging + CSV charts + UTM).

How is this different from the hour-one funnel evening?

Hour-one funnel is a tutorial ritual for wishlist → demo launch → quit rows. This is a tool listicle for fest-week measurement options.

Do I need Wishlist Pulse?

Only if someone can own hosting and alerts. Otherwise CSV + local chart is enough for most micro-studios.

When should I export during fest week?

Pick one local hour and repeat daily. Consistency beats perfect timing.

Where do store page and demo ops fit?

Measurement does not replace the final nine days LIVE/OPT-OUT lock. Ship the demo verb first, then measure.

Should we upgrade Unity to “fix” weird wishlist numbers?

No. Wishlist CSV noise is not an editor bug. Pin the demo branch — Stop Upgrading Unity Mid Steam Next Fest Week - Pin 6.3 LTS — and keep measuring with the tools above.

Closing

Fest week rewards teams that can answer three questions without folklore: how many net wishlists, which tagged sources moved, and what we will not claim. The free stack above is enough. Steamworks stays the source of truth; charts stay conveniences; UTM stays honest about Tracked Visits.

Install the four-tool minimum, file the receipt, and paste Discord before the open-hour argument starts.