> ## Documentation Index
> Fetch the complete documentation index at: https://docs.manalens.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Demo project

> A read-only project with sample data from a made-up game studio. Open it from the intro page or the project menu to see every report before you install the SDK.

The demo project shows ManaLens with data, before you send your own. It belongs to **Brightmoss Games**, a made-up indie studio with a marketing website and a game, **Driftlight**. The data tells the whole story, from a website visit to a purchase in the game.

## Open the demo

* On the getting-started page, click **View demo project**.
* In any project, open the project menu (the project name at the top) and click **Demo project**.

A yellow bar at the top of each page says that you are in the demo.

## What you can do

You can open every report: Overview, Activity, Users and profiles, Attribution, Dashboards, Links, Live, Explorer search and the Steam report. Filters, segments that are already saved, date ranges, breakdowns and CSV exports of the demo all work.

You cannot change anything. Every change is refused with `403 DEMO_READ_ONLY`:

* No new or changed dashboards, charts, links, segments, alerts, goals or customer properties.
* No project settings, Publishable key, Secret key, allowed origins, API keys, revenue or Steam connections. The API does not show the Publishable key, the allowed origins, the alerts or the keys of the demo.
* No **Ask AI** and no **SQL** queries. They run paid model calls and free-form queries. A viewer of your own project cannot run them either.

The demo does not use your plan or trial, and it is not in your workspace.

## What is in the data

About 5,000 website visitors and 1,300 players over the last 90 days:

| Part | Events |
| - | - |
| Website | Page views on `/`, `/devlog/*`, `/press`, `/wishlist`, `/download`, `/support` and `/store/soundtrack`; `wishlist_clicked`, `download_clicked`, `newsletter_signup`, `supporter_checkout` and website `purchase` events with `revenue` |
| Acquisition | Organic search, direct, Reddit, TikTok ads (campaigns every six weeks), YouTube creators through [short links](https://docs.manalens.dev/features/short-links.md), a newsletter, the Steam store page, social sites, press and AI assistants |
| Identity | A free account on the website (`identify` with traits) is the same `user_id` that the player logs in with in the game, so a website visit and the game are one user |
| Game | The [app event conventions](https://docs.manalens.dev/sdks/app-events.md#event-conventions): `game_open`, `session_start`, `session_end`, `level_start`, `level_complete`, `level_fail`, `resource`, `purchase`, `error`, `app_unclean_exit` and `referral_code_redeemed`, on Windows, macOS and Linux, from Steam and itch.io |
| Builds | A new build every two weeks. Every third build has a save-system crash, and a hotfix follows three days later, so [Game health](https://docs.manalens.dev/guides/game-health.md) shows a crash spike |
| Revenue | In-game purchases with `revenue`, and a \$5 monthly supporter subscription as Stripe billing rows |
| Steam | Daily wishlists, sales and UTM Analytics rows |

Player retention is about 35% on day 1, 14% on day 7 and 6% on day 30. Weekends are busier than weekdays.

The dashboard **Driftlight: website to game** has the full funnel (home page, download, first game open, level 3 complete, purchase), a wishlist funnel, player retention, user paths, crash-free sessions and players, errors by build, top errors, revenue and level progression.

> [!NOTE]
>
> In a retention chart, the first days of the date range include players who started before the range, so those cohorts look higher. This is how retention cohorts work in any project with older data.

## Dates stay current

The data is generated from a fixed seed, so it is the same on every run, and it follows the clock. On the hosted service the API adds new demo events through the normal event queue every 15 minutes and deletes demo rows older than 120 days, so the last 90 days are always full.

## Run it yourself

The generator is `apps/api/src/demo-data.ts`. From the repository root:

```bash theme={null}
# Counts only, no services
pnpm demo --dry-run

# Postgres rows (project, dashboard, links) and 90 days of Tinybird rows
node --env-file=apps/api/.env --import tsx scripts/demo/demo.mjs --seed --load --local-workspace <Tinybird Local workspace>
```

`--load` writes with the Tinybird Events API, because the collector stamps `received_at` with the current time and refuses game events older than 7 days. `--reset` replaces the demo rows that are there. To keep the dates current, set `DEMO_REFRESH_ENABLED=true` on the API. It is off by default.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.