> For the complete documentation index, see [llms.txt](https://sdk.metamarket.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sdk.metamarket.tech/use-cases/engagement-data-and-operational-insights.md).

# Operational Data

This page describes what the platform records internally as a game runs, and where studio-facing reporting is headed. It is not a partner-facing data product today; there is no self-serve stream or query API, and the durable store and reporting tools are planned. Two things are worth separating here up front. Authoritative player and economy state, a balance, a level, an inventory, is read directly and is current at read time; you read it whenever you need the current value. Around that state, the engine writes operational records to its log stream as activity happens. Those records are what this page is about.

## What the platform records today

The engine emits quest-lifecycle events, such as renewal and expiry, as structured records, and it writes an operational log stream around the rest of a game's activity: actions as they are reported, rewards issued, and currency and inventory movements. (A richer failed-quest state with follow-up triggers is a separate mechanic on the [Roadmap](/releases-and-reference/roadmap.md), not part of what is recorded today.) These records are useful for operational monitoring and for tracing recent activity during an investigation.

What they are not, today, is a durable, queryable history with retention and integrity guarantees. Most of the stream lives in application logs, which suit investigation but are not built for large-scale querying, and there is no built-in analytics product on top yet.

## Using the records today

Today these records live in the platform's own logs; there is no partner-facing stream, schema, or export contract yet. A studio works with them through the MetaMarket team, which pulls a slice for a specific investigation, or, where a deployment grants log access, against the platform's log output. That covers watching a live release and following up on a specific issue, without a dedicated analytics product.

## What is coming

Reporting tools depend on a durable, queryable event store with defined retention, and that store is the next step for this data. Dashboards and reward-performance reporting build on it directly; segmentation, experiment management, and anomaly detection sit further out. The [Roadmap](/releases-and-reference/roadmap.md) carries the ordering.

The same actions, quests, and rewards that run a game's [engagement and loyalty](/use-cases/engagement-and-loyalty-use-cases.md) loops produce these records. They start the moment your first mechanic runs, so [Evaluate MetaMarket](/evaluate-and-integrate/evaluate.md) is the step that gives you something to read back.