Why this is difficult: A click is not the same thing as a Steam visit
An ad platform counts the click on its own link. Steam counts what happens when a browser or app reaches a tagged Steam page. Between those two events, a redirect can fail, a social app can open an embedded browser, a player can be logged out, or a privacy setting can prevent the visit from being recorded in the same way.
The player may still be real and interested. They may open the Steam app later, search for the game, or return on another device. Steam’s report is valuable precisely because it tells you what remained observable, but it is not a complete record of every person influenced by the campaign.
What Steam measures: Read the traffic funnel from broadest to narrowest
Total visits
- Visits to a supported Steam app or sale page whose URL carried UTM parameters. Ask: how much tagged traffic arrived?
Trusted visits
- A subset of total visits after Steam excludes bots and search crawlers. Ask: how much traffic looked human?
Tracked visits
- Visits for which the user was also logged in to Steam, excluding abnormal behavior such as repeated visits at a high rate. Ask: how much traffic was eligible for conversion reporting?
Tracked conversions
- Wishlists, purchases, or activations of the same App ID attributed to tracked visits within Steam’s conversion window. Ask: what happened after the tagged visit?
A useful mental model: Every stage answers a different question
Imagine a campaign that sends people from an external platform to a Steam store page. The numbers narrow as Steam removes traffic it cannot treat as human or connect to a signed-in user. That narrowing is not necessarily a failure; it is information about what kind of audience the campaign reached.
| Stage | Question it answers | What can be lost |
|---|---|---|
| Platform clicks | Did someone click the platform’s link? | The click may not reach Steam or may be counted differently by the platform. |
| Total visits | Did tagged traffic reach the Steam page? | Redirects, broken links, blocked navigation, and unsupported destinations. |
| Trusted visits | Did the traffic look human to Steam? | Bots and crawlers are removed from the trusted subset. |
| Tracked visits | Could Steam associate the visit with a signed-in user? | Logged-out, cross-browser, cross-device, and privacy-limited journeys. |
| Tracked conversions | Did an eligible visitor wishlist, purchase, or activate? | Later rediscovery and outcomes outside the 72-hour window. |
Reporting timing: Recent conversion numbers are provisional
Steam attributes a wishlist, purchase, or activation when the user takes that action within 72 hours of clicking the UTM link, even if they visit other pages in between. Steam says conversion totals are finalized four days after the visit.
Wait until the conversion window has closed before judging a campaign. A daily number can change for several days, so always record whether the data you are comparing is finalized.
Reconciling reports: Different reports answer different questions
Do not treat a gap between platform clicks and Steam visits as proof of click fraud or broken tracking. The platform counts its own click event; Steam counts tagged visits to a supported destination. The two reports can also apply different time zones, filters, privacy rules, and attribution windows.
- Use the platform report to understand delivery and outbound-click volume.
- Use Steam Total Visits to understand how much tagged traffic reached the store page.
- Use Trusted Visits to assess how much of that traffic looked human to Steam.
- Use Tracked Visits and tracked conversions to assess the part of the journey Steam could connect to a signed-in user.
- Use direct traffic and Steam Search as reminders that people can act on marketing without following the tagged link all the way through.
Manual workflow: Build the comparison in a spreadsheet
- Choose a fixed campaign window and record the time zone, destination App ID, and link taxonomy.
- Export the platform’s click report and Steam’s UTM report for the same window.
- Record total, trusted, and tracked visits separately; do not collapse them into one traffic number.
- Wait for conversions to finalize before calculating wishlist, purchase, or activation rates.
- Compare sources on both volume and the proportion of traffic that remained trackable.
- Write the conclusion as recorded attribution and list the competing explanations before deciding what to test next.
Failure modes: An untracked visit is not an unimportant person
A low tracked-visit rate may mean the campaign reached people who were less connected to Steam, but it may also reflect an in-app browser, a cross-device journey, a privacy choice, or a link flow that made it difficult to sign in. Treat the metric as a diagnostic signal, not a verdict on the audience’s interest.
- People may see a link and later search for the game manually.
- Cross-browser, cross-device, and in-app journeys can break the observable chain.
- Privacy choices and browser configuration can prevent some users from being tracked.
- Steam may hide low-volume UTM combinations to protect privacy.
- An attributed conversion may have happened without the campaign; attribution alone does not estimate incrementality.
How Coal helps: Automate collection and reconciliation, not the judgment
You can run this method with recurring Steamworks and ad-platform exports plus a campaign registry spreadsheet. Coal collects Steam traffic and campaign data into the same operating view, reducing repeated export and reconciliation work.
The definitions, denominators, and evidence discipline still belong to the team. Coal can make the comparison easier; it cannot turn an observable path into a complete account of marketing impact.