Methodology
On this page
On this page
Loading methodology page
SteamGamer.com separates official facts, reporting, community signals, reviews, and analysis so readers can see what is known, what is inferred, and what is still unknown.
The tracker uses no-account reports submitted to SteamGamer.com. Reports are submissions, not verified people. Partial reports help when a chart needs one date or milestone. Optional reminder signups privately link email to reports. See Privacy.
Progress charts count later milestones toward earlier stages: a shipped report also counts as a purchase. Reported totals automatically fill remaining stages through delivery after 14 full days without a saved milestone advancement following an invite, purchase, or shipment. Saving a later milestone restarts the clock; confirmations and date corrections do not. Reported dates stay unchanged. Weekly counts, Activity, timing results, and queue ranges use their own recorded evidence.
Steam Machine and Steam Frame default to a Controller-based adjustment for missing updates. Patterned extensions apply Controller reporting rates once on top of Reported totals. Machine uses the full uplift; Frame currently uses 25%. These estimates assume similar reporting behavior. We hide the extension when evidence is too weak.
Small samples can distort averages. The tracker favors medians and typical ranges, labels any fallback to a broader country result, and withholds ranges for very thin samples.
Tracker trends are not Valve data, sales totals, delivery guarantees, or counts of unique people.
Run Scores describe how a game runs on one device, using the same 1-to-5 scale: Broken, Poor, Playable, Good, and Excellent.
Steam Machine and Steam Deck results can include publicly anonymous community reports, reviewed Community observations, and cited external tests. Frame uses a separate community-report model. Each numeric score included in an aggregate has equal weight, and the evidence counts stay visible. Missing settings stay missing. We do not turn an unanswered field into a hardware claim.
Community observations keep their exact source URL and identity private. Cited tests show a safe source link. Neither creates a contributor-owned community report or account.
Steam Machine, Steam Deck, and Steam Frame evidence stays separate. Frame standalone and streamed results also stay in their own matching groups.
Guest reports allow one game at a time without Steam sign-in. Steam library reports and their settings changes require sign-in and verified game ownership for Machine, Deck, and Frame. Both are ordinary community reports with equal weight. Ownership does not verify hardware or performance. Reports need a score; settings are optional.
The library workspace loads your games when you ask. Selected reports are saved together, or none if the save fails. Unsaved drafts disappear when you reload, change device, or leave the page. We do not store your raw activity, playtime, or profile.
Library filters narrow the finder, device catalogs, and activity to owned games. They preserve device and source distinctions without verifying reports or changing score weight. Frame browsing keeps execution and streaming groups separate. Steam identity stays private.
External evidence needs useful device-specific detail, such as an FPS target, graphics preset, or output resolution. Official compatibility badges remain a separate signal. If a source no longer meets our standard, it can be withdrawn from public results without deleting the audit history.
Medians may describe different tests. Without an FPS target median, we show a reported result or Varies. Custom identifies mixed graphics when no preset median exists. Unknowns stay blank. A source-backed recipe keeps one tested setup and its result, with high, medium, or limited confidence.
Run Scores are observations, not controlled benchmarks or performance guarantees. Updates and settings can change results.
You can read and contribute tracker reports without an account. Guest Run Scores use one private link for the collection. My Steam library lists only reports linked to the connected account. Guest reports and Steam reports have separate views, and sign-in never merges them. Browsing stays public.
Steam sign-in happens on Steam's site and keeps your SteamID64 private. SteamGamer.com never asks for Steam credentials. Do not include credentials or account identifiers in reports. The forms do not ask for Steam IDs, usernames, emails, order numbers, reservation identifiers, tracking numbers, street addresses, ZIP codes, screenshots, documents, account handles, payment data, or government identifiers.
Public reports show only the details needed to understand the result. Private edit links and tokens are not included in public pages or APIs. Run Scores may have an optional anonymous public profile, but hardware tracker reports are never linked to it.
There is no public download of individual tracker reports. Public summaries may be cited with attribution to SteamGamer.com. Do not use them to identify contributors, combine them with private account data, bypass public limits, or imply that the data came from Valve.
Read the full Privacy policy. If a public report exposes something private, contact SteamGamer.com.
If something looks wrong, contact SteamGamer.com with the page or public report link and the strongest source you have. Do not send a private update link, token, or personal information.
We update pages when evidence changes or we find an error. A correction should say what changed and why. It should not hide uncertainty or imply Valve confirmed something it did not.
Editorial images may use original non-generative artwork, licensed or official assets, screenshots for source context, or existing source photos with the site's standard treatment. We do not use AI-generated artwork for article covers, heroes, thumbnails, or social images. Images must not invent test results, interfaces, product details, packaging, or availability.