Understand what happens across the player journey.

 Collect gameplay events and explore player activity. Use available reports to understand how players interact with your game and inform what you improve next.
Review integrationExplore products
Event collection
Available reports
Identity and data access
Contextual draft · Release status, supported versions, and limits await owner review.

Plan the integration

Event collection

 Define a versioned gameplay event schema, such as tutorial-start and tutorial-complete.

Available reports

 Choose an available report that answers your question and document its event definitions.

Identity and data access

 Plan identity mapping, operator access, consent where applicable, and data lifecycle responsibilities.
ILLUSTRATIVE GAME WORKFLOW

analyze a tutorial-start and tutorial-complete event pair where the relevant report is supported.

 This example describes a game-team workflow. Service connections and game rules require explicit integration; it does not imply automatic bindings.

Scope and responsibilities

 Define event schemas and identity boundaries before collecting data. Reports, freshness, retention, exports, and deletion need documented contracts.

Related services

 Explore complementary services for your game, with integration details for each building block.
SERVICE 1

Remote Config

 Adjust game settings between releases. Explore Remote Config
SERVICE 2

Push Notifications

 Reach players beyond the current session. Explore Push Notifications

Setup prerequisites

A test workspace with access to Analytics.
Step 1: pending
A confirmed API version and documented permissions for the workflow.
Step 2: pending
Client and backend tests for successful, invalid, repeated, and interrupted requests.
Step 3: pending
Review integration availability →
YOUR NEXT CHAPTER STARTS HERE

Build the backend for your next game.

 Explore the services and plan your first player experience.
Create GameIntegration overview