How to retrieve player data from Unity Cloud Save for Analytics?

Hi everyone!

I’m working on a Unity WebGL project where I’ve been saving player-specific data (like player name, button presses, and time taken for puzzles…) using Unity Cloud Save. However, Unity Cloud Save currently stores data separately for each player. How can I retrieve and aggregate data from all players at once to analyze things like who entered the game first, who presses the button the fastest, etc.? Any insights on how to approach this?

(moved thread to Unity Services category)

Sounds like a job for Leaderboards because that’s about logging fastest, smallest, most, etc.
You can also use Cloud Code to perform queries on Cloud Save.

Thank you for your response. If I understand correctly from what I check out with leaderboard, it seems like Leaderboards can only save one score per player. However, I don’t just want to save one score; I also want to store other types of data, such as the player’s name, which button they pressed, whether their answer was correct or not, and so on. Does this also work with Leaderboards, or can you suggest another tool?

Hi @nguyenngoclan1401

Unity Cloud Save is designed for storing individual player data, meaning it doesn’t support querying or aggregating data across multiple players. If you’re looking to analyze trends like first-time logins, button press frequency, or puzzle completion times across your entire player base, Unity Analytics is the better tool for the job.

While Unity Analytics provides some built-in events, these don’t automatically track specific player actions like button presses or time taken to complete puzzles. To gather this type of data, you’ll need to send custom events. Custom events allow you to track specific in-game actions and attach relevant parameters—like when a player enters the match (matchEntered), when they press a button (buttonPress), when they solved a puzzle (puzzleCompleted), etc.

Once these events are sent to Unity Analytics, you can analyze them across all players to determine things like who entered first or who pressed a button the fastest.

However, keep in mind that tracking frequent actions like button presses can generate a large volume of events, which may become overwhelming. If your project has a lot of button interactions, consider only logging key moments (e.g., first press, last press, or presses within a specific time frame) rather than every single input, or consolidating many button presses actions into a single event, or only tracking important button presses vs all button pressed. Judging by your opening message, I’d say you’ve already got this ironed out, but just in case!

1 Like