See which campaigns brought visits and wishlists.

Store traffic for a demo game

Over the last 7 days, Pebblewick, the fictional demo game, had 41,735 store visits (1.88% click-through · typical 1.49%) and 7,118 wishlists (17.06% per visit · typical 8.00%–15.00%). A rate above its typical range says the store page converts better than usual, whatever the number of visits.

What you see

• The funnel: impressions, store visits, wishlists and, after launch, purchases, each against last week, with click-through and per-visit rates against their typical range.
• Store traffic over time as visits, wishlists or conversion, with campaigns, unnamed spikes and store page changes marked.
• Sources over the last 7 days: visits, share, change against last week, impressions and click-through for each Steam traffic source.
• UTM links over the last 30 days: wishlists, visits, wishlists per visit and, after launch, purchases for each link.
• Conversion by country: the countries with the highest and lowest conversion.
• Campaigns: the wishlists each campaign most likely added with a low-to-high range, split into direct and indirect, the organic wishlists beside them, the budget and cost per wishlist, how long the effect lasted after the paid window, and wishlist spikes that match no campaign.

How a campaign's wishlists are counted

1. A campaign is a name and a date window, with an optional budget, type and UTM source.
2. The wishlists around the window are split into organic wishlists, which would have come anyway, and the wishlists the campaign brought, directly or indirectly.
3. The campaign's wishlists are given as a range: low, most likely and high. A wider range means the data leaves more room either way.
4. The effect often continues after the paid window, so the days after it count until the effect fades.
5. Cost per wishlist is the budget divided by the campaign's wishlists, given as a range too.
6. A campaign that cannot be told apart from the launch, or that has too little traffic data, is listed as not measured, with the reason.

Where the numbers come from

Traffic comes from the Steamworks store traffic and UTM reports. The SteamStats browser extension connects them while you are signed in to Steamworks in that browser; it never signs in for you or stores your password. They refresh daily on Indie, Studio, and Publisher, and each report covers days up to yesterday. Campaign results combine the wishlist report, which refreshes every 60 min on Indie, Studio, and Publisher, with the traffic reports.

What it does not do

• Traffic is a beta source and optional. It needs the browser extension in a Chromium browser signed in to Steamworks.
• Traffic reports arrive a day behind; today's visits are not in them.
• Campaign results count wishlists on Steam. They do not track spend or clicks on other platforms.
• Without the traffic reports, campaigns are listed but not measured.

Plans

The traffic funnel is part of Indie, Studio, and Publisher. Radar has no traffic data.

Invite-only beta · free for invited studios