How does Manalens stitch identities?

Each event that carries both an anonymous_id and a user_id links that browser or game install to the user. Reports that follow players use the user_id on the event first, then the one user that the anonymous_id links to, then the anonymous_id itself. So activity from before login joins the user's history.

If several users signed in on one shared browser, its anonymous events stay unassigned. They are not given to the last user.

Sources: Manalens core concepts documentation.

Can I stitch players who never sign in?

Yes, with a link from the game. The Godot SDK's link_url() and the Unity SDK's LinkUrl() add mana_hid=<anonymous ID>.<unix seconds> to a URL on your website. The web SDK then sends an identity_handoff event with the game's anonymous ID and removes the parameter from the address bar. The link works for 10 minutes.

Sources: Manalens Godot SDK, Unity SDK and data collection documentation.

What does an example look like?

Example: a player reads your devlog on your website (anonymous ID A), then buys the game. In the game (anonymous ID B), they open your wiki from the menu with link_url(). The handoff joins A and B. If they later sign in to your launcher with user ID player_42, both IDs join that user, and the devlog visit shows in the same history as their play sessions.

Sources: worked example; Manalens identify users guide.

Why does identity stitching matter for indie PC and web games?

Without it, your website campaign data and your game data are two separate worlds. With it, you can see which source brought players who keep playing, not only visitors. Other tools work in a similar way: Mixpanel merges a device ID and a user ID when one event carries both, and says the merge can take up to 24 hours to show in all reports.

Sources: Mixpanel documentation: Identifying users.

Frequently asked questions

Does identity stitching need a login?

No. A link from the game also works. The Godot SDK's link_url() and the Unity SDK's LinkUrl() add the game's anonymous ID to a link to your website, and the web SDK joins the two IDs. The link works for 10 minutes. A login with identify joins IDs across devices.

What happens on a shared PC?

If several users signed in on one shared browser, its anonymous events stay unassigned. Manalens does not give them to the last user who signed in. So one player's history does not take the events of another player, and reports that follow players use only the events that clearly belong to each user.

Which ID do reports use first?

Reports that follow players use the user_id on the event first. If the event has no user_id, they use the one user that the anonymous_id links to. If there is no such user, they use the anonymous_id itself. So activity from before login joins the history of the user.

Sources and implementation