From One Reddit Post to 400 Demo Downloads - Traffic Sources We Logged in Fourteen Days

This is the kind of story that spreads in Discord DMs and gamedev Discords in screenshot form - one post, two weeks, about four hundred demo downloads, and a spreadsheet that finally answers “where did people actually come from?” It is not a guarantee you can paste into your own launch plan. Reddit is volatile, moderators are human, and your game’s hook matters more than any UTM string. What is reusable is the logging habit, the link discipline, and the way traffic decays after the first forty-eight hours.

We will walk through what we measured, how the sources split, and what we would do again on the next build. If you want a longer funnel view that includes store pages, our prototype to Steam page case study with real metrics pairs well with this piece. For store-side discovery without paid UA, the Steam discovery and tags write-up is still the checklist we reach for.

Context - what was live before the post

The demo was a browser-first HTML5 build on itch.io plus a small optional download for people who preferred a zip. The Steam page existed but was not the primary call to action in the thread - we wanted low friction and instant play for Reddit scrollers. We had already run friends-and-family tests, so the build was not crashing on the title screen (a surprisingly high bar on the web).

Pro tip: Before you chase virality, fix first interactive frame and mute-by-default audio on web. Those two issues eat Reddit traffic faster than a bad capsule on Steam.

The post itself - timing, tone, and proof

We posted in a genre-aligned subreddit during evening hours in the US and EU overlap, on a weekday. The title was factual, not hype - what the demo is, how long a run takes, and that it is free. The body included:

• A two-sentence pitch and a bullet list of controls
• One primary link with UTM parameters (utm_source, utm_medium, utm_campaign)
• A short gameplay clip hosted off-site (no autoplay spam in the thread)
• Explicit disclosure that we are the developers (most communities expect that)

We did not post the same link in five subs the same hour. We waited to see moderation feedback and comment velocity before cross-posting elsewhere days later.

Common mistakes

• Dumping a store link when the thread asked for web playable builds.
• Arguing in comments instead of patching a bug and replying with a changelog line.
• Using a link shortener that hides the destination - moderators and users both distrust that.

What we logged so the numbers were trustworthy

We used three layers - itch.io referrer and download stats, UTM-tagged landing URLs, and a tiny first-run telemetry ping (with a plain-language privacy note in the demo). If you are still deciding what to track, the first ten telemetry events article is a sane starting list - we only needed session start and build version for this experiment.

Pro tip: Create one UTM campaign per community (reddit-showcase, discord-pinned, etc.) before you post. Retrofitting UTMs after the spike means you are already guessing.

Fourteen-day traffic shape - spikes, tail, and “dark social”

The downloads were not evenly spread. Roughly half of the four hundred landed in the first three days, driven mostly by the Reddit thread, people who opened the thread from mobile Reddit apps (often showing up as generic referrers), and a small burst from someone dropping the link in a Discord we did not control.

Where credit landed (rounded)

• Reddit and direct referrers tied to that thread - about 55% combined. “Direct” here includes app browsers and stripped referrers, so we treated Reddit UTMs as the tie-breaker when the referrer was empty.
• itch.io browse and related pages - about 25%. Once the game picked up a few ratings, internal discovery on itch mattered more than we expected.
• Discord and chat - about 12%, mostly as discordapp.com open-graph fetches and human pastes we could correlate with comment timestamps.
• Search and everything else - about 8%, including a few stray forum backlinks and people re-finding the page later.

After day five, daily downloads looked like drizzle - ten to twenty a day - then settled lower unless someone re-upped the thread or a YouTuber picked it up (that did not happen in this window, which is typical).

What the comments actually changed

The thread surfaced three actionable clusters - control confusion on gamepad, language in the tutorial text, and performance on integrated GPUs. We shipped a small patch within forty-eight hours and edited the top comment with “build 0.2.1 - fixes X”. That edit produced a second mini-spike smaller than day one but noticeable in the itch graph.

If you maintain a release rhythm, the solo dev QA stack workflow is how we keep those patch notes from turning into chaos.

What we would repeat on the next demo push

• One canonical URL with UTMs in the post, and plain copies for people who strip parameters (we still lose some attribution - accept it).
• A pinned comment that links to patch notes and known issues - reduces duplicate bug reports.
• A single screenshot or GIF that reads on mobile without sound - most people never unmute in the feed.
• Sleep before replying to harsh feedback - the thread is not your design doc, it is a weather report.

FAQ

Do I need itch.io for this pattern?
No, but you need one reliable host with HTTPS, clear file size, and stats. Your own site works if your analytics are honest and your zip is not behind five redirects.

Is four hundred downloads “good”?
It depends on conversion to wishlist, newsletter signups, or survey completes. Downloads are a top-of-funnel metric. Pair them with one downstream goal so you are not optimizing vanity.

Why did search show up at all?
People google your working title after seeing a GIF. If your itch page title matches the words they remember, you capture that tail.

Should I post every week in the same sub?
Usually no - you will hit spam rules and burn goodwill. Space posts around real milestones (major content, performance, localization).

What if moderators remove the thread?
Have a second community and a mailing list ready. Platform risk is real - your owned channels matter.

Closing

One Reddit post did not “make” the game - it validated interest and filled a two-week feedback window with real players. The useful artifact is not the upvote count, it is the spreadsheet that says where time is worth spending next - another sub, a trailer cut, or a store page pass.

If this helped you think about attribution and community timing, bookmark it for your next demo week and share it with a teammate who still posts raw Steam URLs without tracking.