Ravensight

From zero to your first event, in about five minutes

Ravensight is hosted. You do not run a server, you point your game at ours.

  1. Create an account. Sign in at https://app.ravensight.io through RealitySE, the identity system Ravensight runs on. Use email and password, or one of the SSO providers: Apple, Google, Facebook, GitHub, Twitch, Xbox, or Steam.
  2. Create a project. A project is one title, and it holds one game per environment. The first time you sign in the dashboard asks who your studio is, then a name, an id and an engine for your game, creates the project with its production environment, and waits for your first event. Every feature is available right away, no upgrade required. See Projects and environments for the shape.
  3. Copy the ingest key. Each environment has its own. It is shown once on the confirmation screen and looks like gt_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. It is publishable: safe to ship inside your game binary, since it can only create sessions, read the tracking on/off switch and the AI suggestions feed, submit player reports and submit doctor reports. It cannot read analytics or manage your account. If you lose it, rotate it from Settings > Projects for a new one. For a demo, a web build anyone can open or an open-source game, use a public key instead.
  4. Add the autoload. Copy Ravensight.gd into your Godot project, e.g. res://autoload/Ravensight.gd. Open Project > Project Settings > Autoload, add the script, name it Ravensight, and enable it. Set ingest_key to the key from step 3 before Ravensight's _ready() runs: edit the default at the top of Ravensight.gd, or set it from an autoload listed above Ravensight. api_url already points at https://api.ravensight.io. Not on Godot? Install the SDK for your engine from the SDK list instead (Unity, Unreal, web, iOS, Android, C++, Odin or LÖVE), or call the HTTP API directly from anything else.
  5. Send your first event. Call track_event() from anywhere in your game.
  6. See the dashboard. Pick your game in the switcher, and the environment beside it if the game has more than one. The SDK sends events in batches, 5 seconds after the first one waits, so they typically show up within a few seconds, no restart needed.

Which environment does this key hit?

The SDK needs only the ingest key at initialization. The key alone decides which game and environment receive the events, so project and game ids do not belong in your app configuration; treat them as a release audit check instead. The free confirmation is GET /api/v1/settings with the key in X-API-Key, which returns the game's slug, name and environment (see the HTTP API), or npx ravensight-doctor --live, which from 0.4.2 prints key belongs to <name> (<slug>, <environment>). Neither counts toward your usage.

Godot, res://autoload/ravensight.gd

Ravensight.track_event("level_completed", {
    "level": 3,
    "score": 15000,
    "time_seconds": 87.4
})

Not on Godot? The same account and ingest key work against the plain HTTP API: three headers and a JSON body from any engine or client that can make a POST request.