What should a visual novel measure?
Reach, choices and endings. Reach is the share of players who get to each chapter or scene. Choices are the options picked at each menu. Endings are which routes players finish and how many replay for another.
Old tutorials for Ren'Py games often send data to Google Universal Analytics. That no longer works. Standard Universal Analytics properties stopped processing hits on 1 July 2023, and the interface and API closed on 1 July 2024.
| Metric | Event | Question |
|---|---|---|
| Chapter reach | chapter_start | Where do readers stop? |
| Choice split | choice_made | Which options do readers pick? |
| Route share | route_entered | Which routes are popular? |
| Ending rate | ending_reached | How many finish, and which way? |
| Replay rate | second ending_reached | Do readers go back for more? |
Sources: Google Analytics Help, Universal Analytics is going away.
What does public data show about narrative drop-off?
Steam global achievements give a first view, for your game and your comps. VA-11 Hall-A is a bartending visual novel. On 18 November 2026, 97.5% of players had the first achievement, "Welcome to Valhalla!", and 30.3% had "Please come again", for finishing the game. So about 7 in 10 players who started did not reach the end (our arithmetic).
Endings split further. 25.1% had the good ending, 20.2% Alma's ending, 18.7% Dorothy's ending, 12.2% the curry stand ending and 8.2% the concert ending. 19.7% started a new game plus run.
This shows how many finish and which endings are common. It does not show the chapter where the rest stopped, or the choices that led to each ending. That needs your own events.
Sources: Steam Community, VA-11 Hall-A global achievements; Steamworks ISteamUserStats Web API documentation.
How do I send events from Ren'Py?
Use renpy.fetch to post a JSON event to the events endpoint. It supports GET, POST and PUT, sends a json argument as the body and works on desktop, mobile and web. Call it in the main thread, and catch FetchError, because a failed request raises it.
Ren'Py has no Manalens SDK, so build the event yourself. An app event needs channel app, a message ID, an anonymous ID and context.app with a platform. Keep the anonymous ID in persistent data, so one reader keeps one ID across sessions. A web export must be served from your project domain or an allowed origin, because the collector checks the browser Origin.
Ren'Py
init python:
import uuid, datetime
if persistent.mana_id is None:
persistent.mana_id = str(uuid.uuid4())
def mana_track(event, props):
now = datetime.datetime.utcnow().isoformat()[:23] + "Z"
body = {"events": [{"type": "track", "event": event, "channel": "app", "version": "1.0.0",
"message_id": str(uuid.uuid4()), "anonymous_id": persistent.mana_id, "original_timestamp": now,
"context": {"app": {"platform": "windows", "engine": "other", "app_version": config.version}},
"properties": props}]}
try:
renpy.fetch("https://YOUR_COLLECTOR_ENDPOINT/v0/events", json=body, timeout=2,
headers={"x-publishable-key": "YOUR_PUBLISHABLE_KEY"})
except Exception:
passSources: Ren'Py documentation, renpy.fetch; Manalens app events documentation.
How do I track chapters and choices?
Track chapters with a label callback, and choices with one line after each menu option. Ren'Py calls every function in config.label_callbacks when a label is reached, with the label name. Filter it to labels that mark chapters, routes and endings, so you do not send an event for every small jump.
For choices, call mana_track inside each menu option with a stable choice ID and the option. Use IDs, not the visible text, so a rewrite or a translation does not split your data.
Ren'Py
init python:
def mana_label(name, abnormal):
if name.startswith(("chapter_", "route_", "ending_")):
mana_track("story_node", {"label": name})
config.label_callbacks.append(mana_label)
menu:
"Trust her":
$ mana_track("choice_made", {"choice_id": "ch2_trust", "option": "trust"})
jump route_trust
"Walk away":
$ mana_track("choice_made", {"choice_id": "ch2_trust", "option": "leave"})
jump route_aloneSources: Ren'Py documentation, configuration variables.
How do I find where readers stop?
Build a funnel from the first chapter label to the ending, with up to five steps, and read the drop at each step. Then open the chapter with the biggest drop and look at what happens there: a long scene with no choice, a hard minigame, or a slow stretch of text.
Use User paths to see what readers do after a choice. It shows the common paths between custom events, so you can see which choice leads most often to an early quit or to a route that players finish.
Compare readers by choice too. If players who picked one option stop more often in the next chapter, that branch may be weaker, or the choice may have been a surprise they did not like.
Add a session view. Narrative games are often read in long sittings, so a reader who stops mid-chapter may come back tomorrow. Read the funnel with a 7 day or 30 day conversion window, not the 24 hour default, so a reader who finishes over a week still counts as finished.
Sources: Manalens funnels and user paths documentation.
How do I read comps before I write my routes?
Read the ending achievements of 3 to 5 narrative comps on the same day. Note the share that finished, the share of each ending, and the share that started a second run. This tells you how many players a long branch will reach.
In VA-11 Hall-A, 30.3% finished and 19.7% started new game plus (our reading of the same page). Fewer than 1 in 3 players saw any ending. A route that needs two full runs will reach a small group, so put your strongest scenes where most readers still are.
Hidden achievements still show in the Web API percentages, so you can read routes even when the store page hides their names. Use the share of finishers as your first target, then improve it with your own chapter data after launch.
Sources: Steam Community, VA-11 Hall-A global achievements; Steamworks ISteamUserStats Web API documentation.
How do I use the data without writing for the numbers?
Use it to find problems, not to pick the story. A rare ending is not a failed ending. Some endings should be hard to find. Fix places where readers stop without a reason you meant: pacing, bugs, unclear choices or a minigame that is too hard.
Look at counts of readers, not only shares, and wait for enough players before you change a scene. A choice split of 60 to 40 from 20 players can flip next week.
Sources: Manalens funnels documentation.
Where can I see chapter reach and choices by build?
Manalens is the analytics and growth engine built for games. Post events from Ren'Py to the events endpoint, or use the Unity or Godot SDK for other engines. Build a chapter funnel, read choice splits by property and compare readers across builds in one project.
Sources: Manalens product documentation.
Frequently asked questions
Can I still use Google Analytics in a Ren'Py game?
Old tutorials send hits to Universal Analytics, which stopped processing data on 1 July 2023. Google Analytics 4 uses a different setup, so those snippets no longer work. Send events to a tool that accepts app events over HTTP, and check that it works offline and from web exports.
Does tracking slow down a Ren'Py game?
renpy.fetch blocks the display during an interaction until the request ends or times out. Use a short timeout, send events at labels between scenes, and catch the error so a failed request never stops the story. Few events per chapter keep the cost low.
What should I name choice events?
Use one event name, such as choice_made, with a stable choice ID and an option ID as properties. Do not put the visible text in the name. Text changes with rewrites and translations, and stable IDs keep one row per choice across every build and language.
Can I track a Ren'Py web build on itch.io?
Yes. A web build runs in the browser, so the collector checks its Origin. New projects allow *.itch.zone by default, so itch.io HTML5 builds work without setup. Builds on other hosts need the host in your allowed origins. Send platform web in the app context.
Can achievement data replace my own tracking?
It gives a free first view: how many players reach the end and which endings are common, for your game and your comps. It does not show the chapter where readers stop, the choices behind each ending or the build. For those, send your own chapter and choice events.
Sources and implementation
- Ren'Py documentation: Fetching data with renpy.fetch (read 18 November 2026) ↗
- Ren'Py documentation: Configuration variables (read 18 November 2026) ↗
- Google Analytics Help: Universal Analytics is going away (read 18 November 2026) ↗
- Steam Community: VA-11 Hall-A global achievements (Valve, read 18 November 2026) ↗
- Steamworks documentation: ISteamUserStats Web API (Valve, read 18 November 2026) ↗