How do I know if my game is getting refunded?

Look at your refund rate, when refunds happen, and why. The direct sign is a high refund rate (a large share of buyers refunding). A sign is refunds concentrated in the early playtime, within the refund window (like Steam's ~two-hour limit), since a bad early experience converts directly into a refund while the player is still eligible. And signs include refund reasons or reviews citing crashes, bugs, or technical problems, and refunds spiking after a bad update (which makes more players hit problems in the window). To find the causes, capture crashes (especially first-session) and track per version: this reveals whether early-experience crashes are driving refunds and whether a bad update caused a refund spike. If your refund rate is high, refunds concentrate in early playtime, refund reasons cite technical issues, or refunds spike after updates, your game is getting refunded, and the causes are often a bad early experience (crashes, poor performance) in the refund window, which is preventable. The key insight is that the refund window overlaps with the early game, so early-experience problems (especially crashes) convert most directly into refunds, capturing first-session crashes is how you find the early-experience problems driving the refunds, so you can fix them. So a refund problem is usually concentrated early (in the window) and often technical (crashes, bad experience), both of which you can find (via crash data) and fix to reduce refunds.

Why do players refund my game?

A large share of refunds come from technical problems experienced in the refund window, the early playtime (e.g. Steam's first ~two hours), since a bad early experience converts directly into a refund while the player is still eligible. A crash early on is one of the most direct refund triggers: the player encounters it, concludes the game is broken or unreliable, and refunds while they can. Poor performance, game-breaking bugs, and a rough or confusing first impression similarly push players to refund before the window closes, deciding the game isn't worth keeping. Of course some refunds are about fit (the game wasn't what the player expected), which is harder to prevent and more about clear marketing, but the technical refunds are both common and preventable. The reason these refunds concentrate early is the refund window: players can refund within a limited early playtime, so problems they hit in that window (crashes, performance, bugs, a bad first impression) convert to refunds, while the same problems later (past the window) don't cost refunds. This is why early-experience problems, especially crashes, are disproportionately costly for refunds: they hit in the window and convert directly. The dangerous part is that crash-driven refunds can be partly silent (the player crashes, refunds, and may not detail why), so capturing crashes (especially first-session) is how you see the technical problems driving the refunds. So players refund your game largely because of technical problems (crashes, performance, bugs, a bad first impression) experienced in the early refund window, plus some fit-based refunds, and the technical ones are preventable: capturing first-session crashes reveals the early-experience problems driving the refunds, so you can fix them (and update-introduced problems, found via per-version tracking) to reduce refunds, by making the early experience, the refund window, crash-free and compelling.

How do I reduce refunds?

Nail the early experience (the refund window), fix the technical problems that drive refunds, and catch issues fast, since many refunds come from a preventable bad early experience. Because the refund window overlaps with the early game, focus on making the first hours crash-free and compelling: capture first-session crashes from the field and eliminate them (since a crash in the refund window maps almost directly to a refund), ensure good first-launch performance on real devices (a stuttering early experience drives refunds), and get players to the fun fast (so the early experience is compelling enough to keep, not refund). Fix the broader technical problems that drive refunds, crashes, performance, game-breaking bugs, prioritizing the ones players hit early (in the window), since those convert to refunds fastest, capture them from the field, rank by impact, and fix the worst. Catch issues fast: monitor crash rate and alert on spikes (and track per version) so a refund-driving crash or bad update is caught in minutes and fixed before more players hit it in their refund window and refund, a bad update that makes players hit problems in the window can spike refunds, so catching it fast limits the refunds. So you reduce refunds by focusing on the early experience (the refund window): make the first hours crash-free and compelling (eliminate early crashes, ensure performance, get to the fun fast), fix the technical problems that drive refunds (prioritizing early-window ones), and catch issues fast (monitoring, per-version tracking) so refund-driving problems are fixed before they spread. The key is that refunds concentrate in the early window and are often technical, so concentrating prevention there, making the early experience crash-free and compelling, and catching/fixing the technical problems players hit early, directly reduces refunds. Capturing first-session crashes is the essential first step, since the early-experience crashes that drive many refunds are otherwise invisible (and convert silently to refunds), so seeing them is what lets you fix the early-experience problems costing you refunds. This is similar to reducing uninstalls and improving the first impression, with the added urgency that the refund window makes early-experience problems convert directly to lost sales, so the early experience deserves disproportionate attention for refund reduction.

Signs Your Game Is Getting Refunded

Quick answer: Watch for a high refund rate, refunds in early playtime (the refund window), refund reasons citing crashes, and refunds spiking after a bad update. Many refunds come from a preventable bad early experience.

A refund is a player deciding your game isn't worth keeping, often over a technical problem early on. Here are the signs your game is getting refunded.

A High Refund Rate

The direct sign is a high refund rate, a large share of buyers refunding the game. If your refund rate is high (or higher than comparable games), players are buying, trying, and rejecting the game, often over problems they hit early, in the refund window where refunds are easy.

Bugnet captures the crashes and technical problems behind refunds, so you can fix the causes. A high refund rate is the direct sign, and pairing it with crash data (especially first-session) is how you find the causes, since many refunds come from a bad early experience (crashes, performance) in the refund window, which crash data reveals.

Refunds Concentrated in the Early Playtime

A sign is refunds concentrated in the early playtime, within the refund window (e.g. Steam's ~two-hour limit). Since refunds are available early, a bad early experience, especially a crash, converts directly into a refund. Refunds clustering in the first hours point at early-experience problems driving them.

Bugnet captures first-session crashes with breadcrumbs, so early-experience problems driving refunds are identifiable. Refunds concentrated in early playtime are a sign that early-experience problems are driving them, since the refund window overlaps with the early game, a crash or bad experience there converts to a refund, so capturing and fixing the early-experience crashes addresses the refunds at their source.

Refund Reasons Citing Crashes and Spikes After Updates

Signs include refund reasons or reviews citing crashes, bugs, or technical problems (the game being broken), and refunds spiking after a bad update (which makes more players hit problems in the window). If players are refunding over technical issues, or refunds jump after an update, technical problems are driving the refunds.

Bugnet tracks crashes per version, so a refund spike after a bad update is connectable to the issues. Refund reasons citing crashes and spikes after updates are signs technical problems drive the refunds, and capturing the crashes (and tracking per version) connects the refunds to their technical causes, so you can fix them, especially the early-experience and update-introduced ones that convert most directly to refunds.

Watch for a high refund rate, refunds in early playtime (the refund window), refund reasons citing crashes, and refunds spiking after a bad update. Many refunds come from a preventable bad early experience.