Hello!
We're enthralled by the Snowflake add-on and the analysis we will be able to achieve with it. One overarching question we have is whether there are any suggested best practices for querying player data along with the PLAYFAB_ARCHIVE_SHARED view.
So far, we are thinking of these options. Any suggestions are much appreciated.
Thanks
Answer by Brendan · Jun 09, 2018 at 01:45 AM
Well, if 1 means setting up queries that would run on-demand as a response to players on a website, I'd advise against it (since that would mean that an abusive player could drive up your query costs). If you just mean generating daily reports, that's a great use case.
In general, events aren't the best place to manage player data, if you mean all the savegame info for a player. Best to just use the data systems (in particular, Entity Objects and Files) as designed.
But the initial best practice is to make sure to always specify your Title ID, and preferably a timestamp, when querying. That'll help make sure your queries are optimized to your title specifically.
Thanks Brendan,
This is indeed for daily studio reports, nothing a player would be using.
An example of what we may look to accomplish is to run retention reports grouped by information present in Player Data (e.g. male vs female if we were to ask for that information and store it as Player Data)
I understand the storing the data as Entity Objects and Files, but how to utilize that data joined with a report of events so I can say number of logins where Player Data gender = male. I believe just ingesting that data into Snowflake seems the best option versus events for sure. Is there any PlayFab centric way this may be accomplished in the Event History?
Appreciate the help again!
Sorry, but data simply isn't part of the event system. And events are specifically what you're using for analytics. To get that data into Snowflake so that you can query on it, you would need an event (either one of ours, or a custom event).
Store world objects? 1 Answer
Where/How to save players personal data? 1 Answer
Stay logged in when the scene changes 1 Answer
How to block data operations on player objects until azure function finished? 1 Answer
Title exceeded limit Player Data Value size when we calculate it as 6800 bytes 1 Answer