# What data Ravensight holds

Every kind of data Ravensight stores for a studio, how long it is kept, and the [MCP tools](https://ravensight.io/docs/mcp/) that read or write it. Each read is checked against your studio, your role and your token on every call, so a tool only ever returns your own studio's records.

Every tool below costs one programmatic call, 100,000 weighted events on the shared event meter, and needs a studio that has funded a prepaid balance. A tool marked (write) also needs a token an owner allowed to write. This list is generated from the code that stores and serves the data. Any agent can read it, free, as the MCP resource `ravensight://data-products`, or as [JSON](https://ravensight.io/docs/data-products.json).

## Player data

| Data | What it holds, and its tools | Kept |
| --- | --- | --- |
| Events | Every event your game sends, with its properties, per game. `compare_builds`, `explain_metric_change`, `explore`, `export_events`, `get_data_quality`, `get_dimension_breakdown`, `get_distribution`, `get_economy`, `get_engagement_matrix`, `get_funnel`, `get_ad_revenue`, `get_hardware`, `get_health`, `get_level_map`, `get_ltv_forecast`, `get_metrics`, `get_monetization`, `get_overview`, `get_progression`, `get_property_breakdown`, `get_realtime`, `get_retention`, `get_retention_split`, `list_builds`, `query_levels`, `query_players`, `run_sql`, `get_event_catalogue` | Kept 90, 180, 400 days per game (default 90) |
| Test devices and event retention | The devices your team marked as test hardware, shorter retention for chosen event names, and the record of event purges. | Test devices: kept until deleted. Event retention rules: kept until deleted. Event purges: kept 400 days. |
| Lifetime rollups | Daily and monthly totals kept after raw events expire, so lifetime numbers survive retention. `get_history` | Kept until deleted |
| Player journeys | How players move between levels, where they get stuck and the most common paths. Available where journey graphs are configured. `get_journeys`, `find_bottlenecks`, `get_top_paths` | Rebuilt from events, kept as long as they are |
| Player feedback | Bug reports and feedback players send from inside the game. `search_feedback` | Kept until deleted |
| Saved views, dashboards and segments | The views, dashboards, segments and report schedules your team has saved. `list_views`, `list_dashboards`, `get_dashboard`, `list_report_schedules`, `list_segments` | Kept until deleted |
| Monitors and anomalies | Metric monitors and the daily anomalies they found, with expected bands. `list_anomalies` | Monitors: kept until deleted. Anomalies: kept 180 days. |
| Error issues | Distinct errors your game raises, grouped, with who they hit, resolve and ignore status, alerts, and stacks made readable from your uploaded symbol files. `list_error_issues`, `get_error_issue`, `list_symbol_files` | Error issues: kept until deleted. Error alerts: kept 90 days. Symbol files: newest 10 builds per game, each file kept 90 days. Error events: kept 90, 180, 400 days per game (default 90). |
| Experiments and remote config | Experiments, their results, and the remote config values your game reads, including scheduled values and staged rollouts. `list_experiments`, `get_experiment_results`, `list_remote_config`, `list_config_schedules` | Kept until deleted |

## Commercial

| Data | What it holds, and its tools | Kept |
| --- | --- | --- |
| Sales ledger | What each title earned, per storefront, period, currency and region. `list_sales`, `summarize_sales`, `get_sales_playbook`, `get_launch_curve`, `preview_sales_import`, `record_sales` (write), `import_sales_csv` (write) | Kept until deleted |
| Acquisition and attribution | Where each player came from, what each campaign cost, and the return on that spend per currency. `get_campaigns` | Kept until deleted |
| Marketing touchpoints | Ads, videos, streams, posts, press, launches and sales, with the player lift each one measured. `list_touchpoints`, `record_touchpoint` (write), `import_touchpoints_csv` (write) | Kept until deleted |
| Campaign links | Short links you share, and how many people followed each one, by source, campaign, device and day. `list_campaigns`, `get_campaign_stats` | Campaigns: kept until deleted. Campaign links: kept until deleted. Referral clicks: kept 90 days. |
| Pulse | Your posts, their snapshots and comments, and the people behind them. `list_pulse_posts`, `get_pulse_post`, `list_pulse_people`, `list_pulse_sources`, `list_pulse_links`, `list_pulse_matches`, `search_pulse_comments`, `record_pulse_post` (write), `record_pulse_interactions` (write) | Kept until deleted |
| Connections | Store connections and the history of their syncs. `list_connections` | Connections: kept until deleted. Sync history: kept 90 days. |
| Publishers | Your publishers, the goals you agreed and what you owe them, as a report you can send. `list_publishers`, `get_publisher_report` | Kept until deleted |
| Market research | Your research runs with their sourced claims, and the public market facts every studio can search. `search_market_facts`, `get_market_research` | Kept until deleted |

## Development

| Data | What it holds, and its tools | Kept |
| --- | --- | --- |
| Playtest runs and findings | Playtest jobs, their persona runs and the findings each run promoted. `list_playtest_jobs`, `list_playtest_findings`, `get_playtest_report`, `get_validation_report`, `get_feature_job`, `list_feature_specs`, `get_feature_spec`, `list_game_plans`, `get_game_plan` | Kept until deleted |
| Playtest memory | What earlier playtests of a game, cloud and local, learned about playing it, which the next one reads. `list_playtest_memory`, `delete_playtest_memory` (write) | Kept until deleted |
| Punch list and blue tape | The work to finish before handover and the small first-impression annoyances, one item each, with where each came from. `list_punch_list`, `list_blue_tape`, `add_punch_item` (write), `add_blue_tape` (write), `close_list_item` (write), `promote_blue_tape` (write) | Kept until deleted |
| Depth readings | A private reading of how deep each game is on four axes, kept over time, with the evidence behind each one. `get_depth_reading` | Kept until deleted |
| Design and reference documents | Briefs, design documents and the reference files you uploaded. `list_design_docs`, `get_design_doc`, `upload_reference_doc` (write) | Kept until deleted |
| Code briefs and integration status | What the last code scan understood about your repositories, and how the integration is doing. `get_code_brief`, `get_integration_status` | Kept until deleted |

## Studio memory

| Data | What it holds, and its tools | Kept |
| --- | --- | --- |
| Studio memory | What your studio has learned: confirmed patterns, facts and what each game taught you. `search_studio_context`, `get_game_brief`, `get_starting_context`, `add_studio_fact` (write) | Newest 200 per game; confirmed facts and patterns are always kept |
| Brainstorms | Brainstorm boards, their cards and the evidence each card cites. `list_brainstorm_sessions`, `get_brainstorm_board`, `create_brainstorm_session` (write), `add_brainstorm_card` (write) | Kept until deleted |
| Strategy matrices | Decisions laid out as player segments against directions and lenses, each score with its evidence, plus the predictions each decision made and what happened. `list_strategy_matrices`, `get_strategy_matrix`, `diff_strategy_scenario`, `list_strategy_decisions`, `create_strategy_matrix` (write), `add_strategy_segment` (write), `add_strategy_direction` (write), `set_strategy_score` (write), `record_prediction_outcome` (write) | Kept until deleted |
| Investigations | Investigations and the evidence attached to each. `list_investigations`, `get_investigation` | Kept until deleted |
| Digests | The weekly digest per game and for the whole studio. `get_latest_digest`, `get_studio_digest` | Kept until deleted |

## Operations

| Data | What it holds, and its tools | Kept |
| --- | --- | --- |
| Export deliveries | Every export delivery to your own storage, and whether it succeeded. `list_export_deliveries` | Kept 180 days |
| Ingest keys and traffic | Ingest keys and their policies, where traffic comes from, and the addresses you blocked. `list_public_keys`, `suggest_public_key_policy`, `list_traffic_sources`, `list_ip_blocks`, `update_public_key_policy` (write), `block_ip` (write), `unblock_ip` (write) | Ingest keys: kept until deleted. Blocked addresses: each record carries its own expiry. Traffic records: each record carries its own expiry. |

Source: https://ravensight.io/docs/data-products/
Last updated: 2026-11-15
