Why can I not see which visitor wishlisted?
Because Steam protects player privacy. Valve says Steam IDs and personal information are never included, data comes only as totals, small UTM combinations are hidden, and some users are not tracked because of browser or cookie settings. Steam has also stopped supporting Google Analytics on store pages.
So the join between one visitor and one wishlist does not exist. The goal is to connect everything around it: the visit before the Steam click, and the game install after the purchase.
Sources: Steamworks UTM Analytics and Google Analytics documentation.
What can I connect, and how sure is each link?
Four methods, from aggregate to certain. Use the strongest one you can.
| Method | What it connects | Certainty |
|---|---|---|
| Tagged Steam buttons | Your site page to Steam wishlists, as totals | Aggregate only |
| Install network match | A first launch to a website visitor on the same network in the last 72 hours | Likely; high, medium or low confidence |
| Handoff link from the game | A game install to the browser that opens the link | Certain, within 10 minutes |
| Same user ID on both sides | Every browser and install of a signed-in player | Certain |
Sources: Steamworks UTM Analytics documentation; Manalens identify users and install attribution documentation.
How does a handoff link from the game work?
The game opens a page on your website with the player's anonymous ID in the URL. The Unity SDK's LinkUrl() and the Godot SDK's link_url() add a mana_hid parameter with the ID and the time. The web SDK removes it from the address bar and sends one identity_handoff event. Reports then count the browser and the install as one player, with no sign-in.
Rules protect against shared links. The link works for 10 minutes. If links from one install open in more than 3 browsers, none of them join. If one browser opens links from two or more installs, it joins none. Before consent, the SDK returns the URL unchanged.
Unity (C#)
Application.OpenURL(Manalens.LinkUrl("https://example.com/wiki"));Sources: Manalens identify users, Unity SDK and Godot SDK documentation.
How do I identify a signed-in player on both sides?
Call identify with the same stable user ID on the website and in the game. Use an ID from your own account system, not an email address. Earlier anonymous events of that browser or install join the user.
If several accounts sign in on one browser, that browser's anonymous events stay unassigned rather than going to the last account. A user counts once in users, funnels, retention and attribution, while Overview visitor counts stay one per browser or install. Call reset() on logout, so the next player on a shared computer starts as a new visitor.
Sources: Manalens identify users documentation.
How does install matching work when there is no link?
The collector makes a keyed hash of the project and the network address for each website visitor and keeps it for 72 hours. When the game opens for the first time, it looks for website visitors with the same key. With one to three candidates, it picks one: the same operating system first, then the same UTC offset, then the same language, then the most recent.
The match has a confidence of high, medium or low, and the report can count only stronger matches. It never merges the two profiles, so a wrong match cannot move events to another player. Offices, schools, VPNs and mobile carriers often have more than three visitors, so they get no match.
Sources: Manalens install attribution documentation.
What about privacy?
The IP address is not stored or logged; only a keyed hash that differs per project. Match keys are deleted 72 hours after the last website event. Visitors without consent in the SDK consent mode get no key, and bots get none. An owner or admin can turn install matching off, which deletes the keys at once. Add this use to your privacy policy if it describes IP addresses.
Sources: Manalens install attribution documentation.
Which method should I start with?
Start with the ones that need no player action, then add the certain ones.
- Tag every Steam button on your site with the page and the campaign.
- Install the web SDK on your site and the Unity or Godot SDK in the game. Install matching starts after the project receives its first app event.
- Add LinkUrl() or link_url() to every link the game opens: the wiki, the newsletter page, the Discord page.
- If players have accounts, call identify with the same user ID on your site and in the game.
- Read Match precision on the Installs tab. It compares network matches with certain links, so it rises as you add certain links.
Sources: Manalens identify users and install attribution documentation.
What changes in my reports after stitching?
A joined player counts once. Users, profiles, funnels, retention, lifecycle, goals, attribution and revenue by source treat the browser and the game install as one person. Overview visitor counts stay one per browser or install.
Attribution gains the most. With a certain link, a website touch can get credit for a purchase or a session in the game. A creator link that brought a visitor to your wiki, who later bought through the game, then credits the creator.
Sources: Manalens identify users and attribution models documentation.
How do I connect my site and my game?
Manalens is the analytics and growth engine built for games. Install the web SDK on your site and the Unity or Godot SDK in the game. Add LinkUrl() to the links your game opens, and read installs by channel in Attribution.
Sources: Manalens product documentation.
Frequently asked questions
Can I find out which website visitor wishlisted my game on Steam?
No. Steam gives UTM totals only, never Steam IDs, and hides small rows. You can tag each Steam button on your site to see which pages send wishlists, and link the game install to the browser with a shared user ID or a handoff link.
Does install matching merge a website visitor with a player?
No. A network match is likely, not certain, so the visitor and the install stay two profiles. Only a certain link joins them: the same user ID on both sides, or a handoff link that the game opens within 10 minutes.
Do I need players to sign in for identity stitching?
No. A handoff link from the game joins the browser and the install without a sign-in. Signing in with the same user ID on both sides is the strongest link, and it also joins later devices and new installs of the same player.
Is install matching legal under privacy rules?
That depends on your region and your policy, so ask your own adviser. The collector stores no IP address, only a keyed hash per project, and deletes it after 72 hours. Owners can turn matching off. Describe this use in your privacy policy if it covers IP addresses.