# Event catalogue, test devices and purging

**Event catalogue.** The Event catalogue page lists every event name the game sent in a window (30 days by default, up to 400): how many times, from how many devices, when it was first and last seen, and its ten most common top-level property keys. Up to 500 names, busiest first. Real players only by default; the synthetic switch works as it does everywhere. MCP `get_event_catalogue` reads the same list at the normal programmatic rate.

**Test devices.** Owners and admins can mark up to 200 device IDs per game as test devices, with a label. Analytics pages leave them out by default, the way playtest sessions are left out. The Event catalogue page has a switch to count them, website analytics requests accept `test_devices=include`, and MCP analytics reads always leave them out. Bulk export, SQL, realtime and long-range history are not filtered.

**Purge an event name.** The owner can delete every stored event with one name for this game. The delete runs in the background, one purge per game at a time, and is recorded in the audit log. It cannot be undone, and daily and monthly totals already written keep their counts. Another game's events are never touched.

**Keep an event shorter.** The owner can keep one event name for fewer days than the game's retention (1 day up to one day less than the game's). Once a day, rows of that name older than its days are deleted. A game can have 50 such rules. Both actions are free.

Source: https://ravensight.io/docs/event-catalogue/
Last updated: 2026-11-15
