utm_ parameters, and the wishlists, purchases and activations that follow.
Tag your Steam links
Steam records a link only when it points to your app page (store.steampowered.com/app/<app ID>) or a sale page, and it has utm_source or utm_campaign. Example:
utm_campaign and utm_content values that you use in your other links. Then the Steam rows line up with your website and short link data for the same campaign and creator.
Export the CSV from Steamworks
You need the View Marketing Traffic Data permission for the game in Steamworks.1
Open UTM Analytics
Sign in to Steamworks. Open your game, then Marketing & Visibility, then the UTM Analytics tab.
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
Click the download button. 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
Open Settings, then Integrations. Under Steam, choose the CSV file and enter the Steam app ID if the file has no app ID column.
2
Preview
Click Preview. Check the totals, the sample rows and the column mapping. Valve does not publish the exact column names, so the import matches columns by name (for example “UTM Source”, “Total Visits”, “Wishlists”) and never by position. Change a mapping in the Columns list if it is wrong, then preview again.
3
Fix or skip bad rows
Rows with errors are listed with their line numbers (for example a negative count or a date that is not valid). Fix the file, or select Import without these rows.
4
Import
Click Import. The import appears in Import history.
1,234, and dates such as 2026-09-01, 2026/09/01, Sep 1, 2026 and 09/01/2026. For a date like 03/04/2026, the import detects the order from the other rows; if it cannot, choose the date format in Options. A “Total” row is skipped. Rows with the same day and UTM values are added together. A file can have at most 20,000 rows and cover at most 366 days, and one import is for one app.
Re-imports
For each app and day, the report uses only the latest import that covers that day. Import the same period again and the new numbers replace the old ones; nothing is counted twice. Steam finalizes conversions 4 days after the visit, so import the last week again after a few days. If an upload fails, nothing is replaced.Read the report
Open Explorer, then Steam (or the link in the Steam section of Integrations). Choose the date range, an app ID, and how to group: 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.
Connect the Steamworks API (optional)
The automatic Steam sync is in early access. Check the first totals against your Steamworks reports. The Steam UTM Analytics CSV import works today.
1
Create a Financial API key
In Steamworks, open Users & Permissions, then 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. ManaLens checks the key with Steam before it saves it. The key is stored encrypted and is never shown again.
3
Sync
Click Sync now. The first sync reads the last 90 days. After that, the server syncs once a day when the daily sync is turned on.