Skip to main content
The Console Billing page shows usage by organization and project. Usage is grouped by API calls, storage, CDN egress, game logs, push devices, and realtime usage.

​
What to Watch

ItemMeaningHow to Reduce It
API callsSDK and Web API request volumeCache values repeatedly read on the same screen.
Storage bytesPublic Storage and runtime data sizeRemove old files, unused save slots, and large JSON payloads.
CDN egressPublic Storage download trafficCheck hashes and download only changed files.
Game logsplayer.InsertGameLog event volumeRemove logs and payload fields that are not used operationally.
Push devicesRegistered push tokensRefresh stale tokens on logout, account switch, and token rotation.
Realtime usageNotification/chat polling and acknowledgementsStop polling when the screen is closed or increase intervals.

​
Operating Procedure

  1. Open Billing in Console.
  2. Select the month and project.
  3. Find the highest usage categories.
  4. Review SDK call sites and Console settings for that feature.
  5. Compare usage after the next aggregation cycle.

​
Feature Tips

  • Check hashes or versions before downloading public files or game configs.
  • Call ranking Top, Me, and AroundMe only when the screen needs them.
  • Standardize game log event names and payload schemas.
  • Prefer the default user data record, create multiple records only when needed, and prune old large payloads first.
  • Use short polling intervals only while realtime screens are foregrounded.
For billing commitments and included quota, use the latest plan shown in Console or your agreement.