bitHeads employees
Well - the "owned custom entities" approach could come into play again if you want to view the matches across the system. Although owned custom entities are owned by players (and get deleted if a player account is deleted) - they are still queryable across the system... via API or the Portal (see App > Global > Global Data > Custom Entities ).
I hope that helps!
Oh - and I should note that you can retrieve the latest retention report - as well as the retention report for a specific start date...
https://docs.braincloudservers.com/api/capi/report/sysgetlatestreport
What we don't have right now is an API to list the reports that are generated and waiting for retrieval. We are working on that for a future patch.
Also note that we currently keep daily reports for 10 days - and weekly reports for 37 days.
Thanks for the feedback Christophe! We'll take a look into those requests.
Hi,
Users with LIVE apps on brainCloud's Public BaaS (i.e., https://portalx.braincloudservers.com) should now have access to our Retention Analytics. (You can find the numbers on the App > Reports > Analytics > Retention screen.).
So - any questions on these numbers? What they mean? How they are calculated? We are happy to clarify any questions you may have.
We are also interested in your overall feedback regarding the feature.
We've already had the question of whether we could calculate the numbers on a per app-version basic... (i.e. according to the gameVersion passed into the Authenticate call). We're going to look into that. That said - the whole reason we did Retention Analytics was so that we could integrate it with a new LiveOps Events feature we're working on -- so we'll probably tackle those scenarios at the same time.
Anyway - your feedback is invaluable. So look up your numbers and hit us up with questions and/or feedback!
Paul.
Hi @tlim and @devsleeper ,
Player stats are definitely useful for keeping all-time stats.
If you want to limit stats to recent matches - you might consider using "Owned Custom Entities" for each match result. You can set a TTL for the objects so they don't stick around too long - maybe 90 days?
And then just retrieve the last 20 match results (if they exist) to sum up the totals and produce the stats.
I hope that helps!
Paul.
Hi @tlim ,
What sort of match history?
What sort of game are we talking about? Which multiplayer APIs are you using?
Paul.
Hi @LEE-JONG-GUN ,
Thanks for the feedback.
This is admittedly a tricky one.
The best route I've seen to handle it is to use our shared (i.e. parent-child) accounts feature - which involves using a parent app for the player account - and a child app for the character accounts.
Note that it does involve two live apps - but we can put your parent app on a special plan with no live fee (you just pay for API calls) - and there won't be a ton of API call from that app - cause 99% of all calls will be against the child app.
There is more info here - https://docs.braincloudservers.com/learn/key-concepts/authentication/shared-accounts/
I hope that helps!
Paul.
Thank you for sharing this information. It does not have an impact on our server-side validation.
Ah - perfect. Yeah - that sounds like a better option given the full requirements.
Glad you found it... and welcome to brainCloud!
Hi @devsleeper ,
I think I'd recommend you model "Location" as a Custom Entity collection. You can use the "entityId" as your shareable id... and include custom attributes in the "data" section of the object - like "data.includeInMatchmaking", etc...
It would probably best be an "Owned" entity - so if the user account that owns it is deleted - it is deleted as well.
I hope that helps!
Paul.
