Start here
gameglow is game analytics for Unity, Godot and Construct 3.
Using an AI agent? Connect it to the gameglow MCP server and it does the whole setup: see AI agents (MCP). Agents that read docs can start at https://app.gameglow.io/llms.txt. Every page is also plain markdown: add .md to its address, for example https://app.gameglow.io/docs/godot.md.
Setting up by hand? Pick your engine. Each quickstart takes about ten minutes and ends with your first event on the dashboard.
What you get
With no tracking code, the SDK records:
- sessions and playtime
- frame rate, hitches and memory
- crashes, reported on the next launch
- whether the player is active or idle
- device details such as platform, GPU, screen and input device
Add one-line calls for funnels, zones, saves, timings and your own events. Optional in-game bug reports and feedback are one switch each.
How it works
- You add the SDK to your game and give it one SDK key.
- Once the player agrees to analytics, the SDK sends events in small batches every 15 seconds. Runs inside the editor send at once.
- The dashboard at https://app.gameglow.io shows players, retention, funnels and insights, and your agent can read the same data.
Access during the beta
If sign-up is invite-only, use Request an invite on the sign-in page. The Unity and Godot SDKs are in a private GitHub repo during the beta. Add your GitHub username when you request your invite, or under Account → SDK access if you already have an account. We add you to the repo. Construct needs no access. If git says Permission denied (publickey) or Repository not found, you have no access yet (see Troubleshooting).
All pages
For agents
The index is https://app.gameglow.io/llms.txt, and https://app.gameglow.io/llms-full.txt has every page in one file. The MCP server is https://app.gameglow.io/mcp.
Machine-readable: this page as .md, and the agent index as /llms.txt