Included platform analytics
- Play starts from public play pages and Sandbox previews.
- Session duration measured from wrapper-level play sessions, excluding inactive/unfocused time where available.
- Load success and load failure signals for the wrapper and game iframe.
- Boosts: player interest signals inside Buncha Games.
- Reports and private player feedback.
- Device, viewport, referrer, and basic source signals where available.
- Listing and Testing Grounds visibility signals that help you understand whether players are finding and launching the game.
What SDK analytics adds
- Lifecycle events such as game ready, game start, pause, resume, and game end.
- Level or stage progress events.
- Custom events you define, such as area_entered, boss_defeated, tutorial_complete, skin_previewed, boost_used, or room_created.
- SDK Events explorer views for event-type totals, calls per play, recent calls, trend, and safe payload-field summaries.
- Wallet, IAP, ad, and entitlement callbacks when those features are enabled for your game.
Custom event examples
Custom events are discovered after successful calls are received. Use short event names and simple payloads that describe gameplay state without sending secrets or private player data.
const buncha = window.buncha ?? window.galaxy;
buncha?.game?.start?.({ mode: "survival" });
buncha?.level?.complete?.("forest_1", { timeSeconds: 84, attempt: 2 });
buncha?.analytics?.event?.("area_entered", { areaId: "shrine_grove" });
buncha?.analytics?.event?.("boss_defeated", { bossId: "forest_king", phase: 2 });
buncha?.game?.end?.({ score: 1200 });How to use analytics
Start with the default platform analytics to confirm players can find, load, and play the game.
Add SDK events for the moments only your game can know: level completion, mode selection, room creation, tutorial progress, premium-item previews, and major failure points.
Use custom events sparingly. A handful of well-named events is usually more useful than hundreds of noisy hooks.