I've been reading through the plans, service descriptions and API and have come up with some general questions to better understand how I plan and build my game to work with PlayerIO.
Sessions: According to documentation: Session time is measured from the first connect to the last api request.
What counts as the last API request? I’d assume a call to any PlayerIO server/backend service would count. But, let’s say the player doesn’t use any of these, just the initial connection. They connect to PlayerIO when the game starts, play for 15 minutes, then close the app. Would the session length be zero if no other API’s are called? Or, does PlayerIO automatically ping the user on periodic intervals to check and see if they are still in the game?
If PlayerIO automatically pings, what are the intervals at which it does this? What about the case of a mobile game where the player plays for a few minutes, then minimizes the app, then returns? Are these multiple sessions or tracked as one long session?
PayVault:
1. Is the usage of PayVault required in order to track revenue with PlayerInsights, or can a custom event be added to track when purchases occur?
2. Does the usage of PayVault require a corresponding player object within BigDB, or is PayVault handled separately? Specifically, my concern boils down to BigDB object count representing the theoretical “max users” each PlayerIO plan can support. Let’s say I use another service to handle my user authentication/player data storage instead of BigDB. Can I still use PayVault?