Does Steam show demo to full game conversion?

No. Steamworks shows totals for each app: units, wishlists, and for a demo the median time played. Valve shows how many players played and wishlisted after Next Fest. No report links a demo player to a later purchase of the full game.

The UTM Analytics report does not help here either. Valve says demo and DLC downloads do not count as conversions unless they include the base game, and in-game purchases do not count.

Sources: Steamworks UTM Analytics documentation; How To Market A Game (30 June 2026); How To Market A Game (26 October 2022).

What numbers does Steam give me about my demo?

Steam gives you the demo as its own app, with its own stats. You can read median time played in the product table of the demo in the Sales & Activation Reports. Players of the demo see a link to the full game in their library, and a separate demo page links back to the full game.

You can also send one notification to the players who wishlisted the full game when the demo releases. You choose the time, up to two weeks after the demo launch. Wishlist notifications have a two week cooldown per app.

NumberWherePer player?
Median time played in the demoSales & Activation Reports, demo productNo, one total
Played and wishlistedShown after Steam Next FestNo, one total
Wishlist adds and purchases of the full gameWishlist report or Web APINo, daily totals
Demo player who later boughtNot reported by SteamOnly with your own analytics

Sources: Steamworks Demos documentation; How To Market A Game (26 October 2022).

How do I measure demo to full game conversion myself?

Use one player ID in both builds. With the same user ID, an analytics tool joins the demo player and the full game player into one person. Then a funnel counts how many demo players open the full game.

A hash of the Steam ID is a good ID, because Steam gives the same player the same ID in the demo and in the full game. Ask for consent before you send it, and hash it so that the raw Steam ID never leaves the game.

  1. Add the same analytics SDK, with the same project key, to the demo build and to the full game.
  2. In both builds, after consent, call identify with the same user ID, such as a hash of the Steam ID.
  3. Set the build field to demo in the demo and to the release name in the full game, so reports can tell them apart.
  4. In the demo, track a custom event such as demo_open at launch. In the full game, track full_game_open at launch.
  5. Build a funnel with two steps, demo_open then full_game_open, with a 90-day conversion window.
  6. Read the conversion rate, and break it down by country.

Sources: Manalens identify users documentation; Manalens funnels documentation.

Why do I need custom events for each build?

Because both builds send the same automatic events. An SDK sends game_open at each launch in the demo and in the full game. A funnel of game_open then game_open would count demo players who simply launched the demo twice.

Two clear event names avoid that. demo_open happens only in the demo and full_game_open only in the full game, so the funnel counts a real move from one to the other.

In the demo build, after consent (Unity)

Manalens.Identify(hashedSteamId);
Manalens.Track("demo_open");

Sources: Manalens game events documentation; Manalens funnels documentation.

What window should the funnel use?

The longest one you can, because many demo players wait for the launch. A player who tried the demo at Next Fest can buy months later, at release or in a sale. Manalens funnels go up to 90 days.

For a demo that came out long before launch, start the funnel date range near the launch day. Then the window covers the launch week, when most wishlisters buy.

Sources: Manalens funnels documentation; Steamworks Wishlists documentation.

What does the number not tell me?

It counts only players who gave consent and launched the full game. A player who bought and never played is missing. A player who bought on another account is missing. So your rate is a floor, not the exact share.

It also cannot prove that the demo caused the purchase. Players who liked the demo were likely to buy anyway. Compare the rate across demo versions or across how far players got in the demo, not against an outside number.

Sources: Manalens identify users documentation.

How do I use the result?

Look for the step in the demo where future buyers and non-buyers part ways. If players who finish the demo convert far better than players who stop at level two, level two is where to work.

Then change one thing in the next demo build, give it a new build value, and compare the two builds with the same funnel. Keep the old build value in your reports, so that the two groups stay apart.

  • A middle step such as demo_completed, to compare players who finished the demo with players who did not.
  • Conversion for each demo build value, one funnel per build.
  • Conversion by country of the demo player.
  • Time from demo to full game, from the median time of the funnel step.

Sources: Manalens funnels documentation.

How do I set this up?

Manalens is the analytics and growth engine built for games. Install the Unity or Godot SDK in both builds, identify players with the same ID, and build a two-step funnel with a 90-day window. A user counts once across installs, so you see the share of demo players who open the full game.

Sources: Manalens product documentation.

Frequently asked questions

Can I see which demo players bought my game on Steam?

No. Steam reports totals per app, such as median time played and, after Next Fest, the number of players who played and wishlisted. It does not link a demo player to a purchase. You need your own analytics with the same player ID in both builds.

What ID should I use in the demo and the full game?

Use an ID that is the same for one player in both builds, such as a hash of the Steam ID. Hash it so the raw ID never leaves the game, send it only after consent, and use the same analytics project in both builds.

Does a demo download count in the Steam UTM report?

No. Valve says demo and DLC downloads do not count as UTM conversions unless they include the base game. The UTM report counts wishlists, purchases and activations of the main app within 72 hours of a tracked visit. Measure demo play with an SDK in the demo build instead.

Is my measured conversion rate exact?

No, it is a floor. It counts only players who gave consent and launched the full game. Buyers who never played, or bought on another account, are missing. Use it to compare demo versions and progress groups, not as an exact share.

How long after the demo do players buy the full game?

It varies, and many wait for the launch or a sale. Read the median time of the funnel step from demo_open to full_game_open. Use the 90-day window, and set the date range near launch day if the demo came out long before release, so the launch week is inside it.

Sources and implementation