List of Pley Analytics Events

C# API References: Analytics Kit

Must-have Events

These events must be triggered in the correct place for your game to function.

Event	Description	Properties
`game_loaded`	`AnalyticsKit.GameLoaded();` should be called whenever the game finishes the initial loading, and the game is interactable for the player. Call this method whenever the loading screen is complete.	-
`user_interacted`	`AnalyticsKit.UserInteracted();` should be called whenever the player takes their first meaningful action in the game, such as clicking a button or taking their first game action.	-
`user_engaged`	`AnalyticsKit.UserEngaged();` should be called whenever the user is considered engaged. It is recommended to fire this event after about 5 minutes of uninterrupted gameplay.	-
`gameplay_analytics_initialized`	`Analyticskit.Initialize(AnalyticsKit.Config);` should be called on startup, after the player data has been loaded. (C# API Reference )	`username`, `level`, `application_version`, `custom_user_id`, `currencies[]`
`gameplay_tutorial_started`	`Analyticskit.TutorialStarted();` should be called whenever the first tutorial instructions are displayed on the screen. Used to track the new user journey. (C# API Ref )	-
`gameplay_tutorial_advanced`	`Analyticskit.TutorialAdvanced(String);` should be called when a tutorial step is completed. Used to track the new user journey (C# API Ref ).	`tutorial_step`
`gameplay_tutorial_completed`	`Analyticskit.TutorialCompleted();` When the player completes the tutorial. (C# API Ref ).	-
`gameplay_started`	`Pley.AnalyticsKit.GameplayStart();` Whenever active gameplay starts, including on first start.	-
`gameplay_stopped`	`Pley.AnalyticsKit.GameplayStop();` When the game is paused, menus are opened, UI screens are shown, etc. Not during gameplay.	-
`loading_started`	`Pley.AnalyticsKit.LoadingStart();` When a loading screen starts.	-
`loading_stopped`	`Pley.AnalyticsKit.LoadingStop();` When a loading screen finishes.	-

Automatic Events

These events are available but require no implementation.

Event	Description	Properties
`game_load_started`	Triggers as soon as the loading begins (before the game code executes). This occurs after the "start"-button is clicked or the game automatically starts.	-
`playable_loaded`	Triggers when the Web Playable completes its initialization. When playable_loaded fires, the game takes over and continues loading. Web Playable loads the necessary assets (cached or downloaded) for the game and game engine to launch.	-
`purchase_started`	Tracks purchases.	-
`purchase_completed`	Tracks purchases.	product_id, product_name, amound_usd
`game_crashed`	Records crash data. All crashes can be found in the Game Manager Crash Log.	-
`ad_shown`	Triggers when a user successfully views an ad to completion.	-
`show_ad_requested`	Triggers when the game requests an ad. It is not guaranteed an ad is provided.	-
`auth_completed`	Triggers when the user logs in through Pley. Type tracks Signup/Login, and method tracks social login method.	type, method
`PageView`	Triggers whenever a user views a page on a Gamesite. Contains which URL or subpage the user viewed. Only sent by the Pley Gamesite.	url

Optional Events

These events are optional, and must be implemented in the game through the Pley SDK AnalyticsKit.

Event	Description	Properties
`gameplay_tutorial_skipped`	When the player skips the tutorial.	-
`gameplay_premium_spent`	When the player spends premium currency.	`name`, `amount`, `source`, `new_balance`
`gameplay_premium_gained`	When the player gains premium currency.	`name`, `amount`, `source`, `new_balance`
`gameplay_resource_spent`	When the player spends game currency.	`name`, `amount`, `source`, `new_balance`
`gameplay_resource_gained`	When the player gains game currency.	`name`, `amount`, `source`, `new_balance`
`gameplay_offer_shown`	When the player is shown an offer, deal, liveOps, or promotion.	`offer`
Custom Event	Set any game-specific custom event you need, and deliver it to your analytics services. (API Reference)	`name`,`parameters[]`