Skip to main content
Steam’s UTM Analytics report counts store page visits from links with utm_ parameters, and the wishlists and purchases that follow. Import it to see which videos, posts and creators bring Steam players. Steam records a link only to your app page (store.steampowered.com/app/<app ID>) or a sale page, with utm_source or utm_campaign:
Use the same utm_campaign and utm_content values as your other links, so Steam rows line up with your website data.

Export the CSV from Steamworks

You need the View Marketing Traffic Data permission for the game.
1

Open UTM Analytics

In Steamworks, open your game, Marketing & Visibility, UTM Analytics.
2

Choose the period

Choose the dates. Do not filter by UTM values: an import replaces all earlier rows for the same app and days (see Re-imports).
3

Download the .csv file

If the file has no date column, export one day at a time and set the date when you import.

Import the CSV

You need the owner, admin or editor role.
1

Choose the file

In Settings, Integrations, Steam, choose the CSV file. Enter the Steam app ID if the file has no app ID column.
2

Preview

Click Preview and check the totals, sample rows and column mapping. Columns are matched by name (for example “UTM Source”, “Total Visits”, “Wishlists”). Fix a wrong mapping in Columns and preview again.
3

Fix or skip bad rows

Rows with errors are listed by line number. Fix the file, or select Import without these rows.
4

Import

Click Import. The import appears in Import history.
File rules:
  • Comma, semicolon or tab separators, quoted cells, a byte order mark, and thousands separators such as 1,234 are accepted.
  • Dates such as 2026-09-01, 2026/09/01, Sep 1, 2026 and 09/01/2026 are accepted. If the order of 03/04/2026 is unclear, choose the date format in Options.
  • A “Total” row is skipped. Rows with the same day and UTM values are added together.
  • At most 20,000 rows and 366 days, for one app.

Re-imports

For each app and day, only the latest import that covers that day counts, so nothing is counted twice. Steam finalizes conversions 4 days after the visit, so import the last week again after a few days. A failed upload replaces nothing.

Read the report

Open Explorer, Steam. Choose the date range, an app ID, and a grouping: source, medium, campaign, content, term, or campaign and content.
  • Visits: store page visits with UTM parameters.
  • Trusted visits: visits without bots and search crawlers.
  • Tracked visits: visits by people logged in to Steam in that browser. Only these can convert.
  • Wishlists, Purchases, Activations: actions on the same app within 72 hours of a tracked visit.
  • Wishlist rate and Purchase rate: wishlists or purchases per tracked visit.
Steam attributes only a small part of wishlists and purchases (Gamesight sees less than 10% of traffic attributed). Clicks in a social app’s browser followed by a wishlist in the Steam client are not counted, and Steam hides UTM combinations with few visits. Compare campaigns with each other; do not read the numbers as totals.

Connect the Steamworks API (optional)

The automatic Steam sync is in early access. Check the first totals against your Steamworks reports. The CSV import works today.
Valve’s Financial Web API gives all wishlists and sales, not only those from UTM links. You need the owner or admin role and a verified MFA session.
1

Create a Financial API key

In Steamworks, open Users & Permissions, Manage Groups, and create a Financial API Group. Copy the Web API key from the group page. Valve recommends that you allow only trusted IP addresses for this key.
2

Connect

In Settings, Integrations, Steam, paste the key and the app IDs for this project, then click Connect Steam. The key is checked, stored encrypted and never shown again.
3

Sync

Click Sync now. The first sync reads the last 90 days. After that, it runs once a day when the daily sync is on.
The key can read every app on your partner account, but Manalens keeps only the app IDs you enter. Wishlist days are GMT; sales days are Pacific Time. Sales are in USD.

Sources