Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
62 changes: 39 additions & 23 deletions docs/capabilities/analytics/journeys-dashboard.md
Original file line number Diff line number Diff line change
@@ -1,38 +1,54 @@
# Journeys Dashboard

Once you’ve implemented [Devvit Journeys](./devvit-journeys.md), you’ll be able to see how users are engaging with your app. You’ll find Journeys analytics on the App Details page, under the Analytics tab.
Once you’ve implemented [Devvit Journeys](./devvit-journeys.md), you’ll be able to see how users are engaging with your app. You’ll find Journeys analytics on the App Details page, under the Analytics tab.

## Metrics

Journey metrics are displayed in a dedicated section below the existing engagement metrics.

![Journeys-1](../../assets/analytics/journeys-dashboard.png)

## Understanding your data
You can download a CSV of your daily Journey metrics over a 30-day lookback period.

### Understanding your data

Journey analytics data is aggregated into a single record per app per UTC day. This data helps you understand the user’s experience of your app. At a high level:
Journey analytics data is aggregated into a single record per app per UTC day. This data helps you understand the user’s experience of your app. At a high level:

* **Start Rate**: Are users engaging with my app?
* **Completion Rate**: Are users successfully finishing the game?
* **Sessions per User**: Are users coming back?
* **Median Session Duration**: How much time are users spending in my app?
* **Journey Progress & Interaction Events**: Where are users engaging or getting stuck?
- **Start Rate**: Are users engaging with my app?
- **Completion Rate**: Are users successfully finishing the game?
- **Sessions per User**: Are users coming back?
- **Median Session Duration**: How much time are users spending in my app?
- **Journey Progress & Interaction Events**: Where are users engaging or getting stuck?

## Journeys insights
### Journeys insights

Raw event counts show overall Journey activity and usage volume.
Raw event counts show overall Journey activity and usage volume.

Rate- and duration-based metrics help developers evaluate Journey adoption, engagement, and completion, making it easier to identify trends and diagnose issues.

| Metric | What it tells you |
| ----- | ----- |
| **utc\_day** | Lets you analyze app performance over time and identify trends, regressions, or the impact of releases. |
| **app\_ready\_count** | Shows how often the app was successfully loaded and available to users. Serves as the baseline for measuring adoption. |
| **journey\_start\_count** | Indicates how many times users began your game. Helps measure interest and discoverability of your app’s entry points. |
| **journey\_progress\_count** | Reveals how actively users move through your app. Sudden drops may indicate friction or confusing steps. |
| **journey\_interaction\_count** | Measures user engagement within your app. Helps identify whether users are actively interacting or passively abandoning flows. |
| **journey\_end\_count** | Shows how many users reached an end state. Useful for understanding overall throughput and completion volume of your game. |
| **start\_rate** | Measures the percentage of app loads that result in a user starting the game. Helps evaluate whether users are discovering and choosing to engage with your app. |
| **completion\_rate** | Measures the percentage of times a user has started your game and successfully reached completion. Helps identify drop-off problems and assess the effectiveness of your app’s design. |
| **sessions\_per\_day** | Shows how frequently users engage with your app on average. Helps distinguish between occasional use and repeat engagement. |
| **median\_session\_duration\_seconds** | Indicates how long users typically spend in your app. Helps assess game complexity, engagement depth, and the impact of changes to the game flow. |
| Metric | What it tells you |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **utc_day** | Lets you analyze app performance over time and identify trends, regressions, or the impact of releases. |
| **app_ready_count** | Shows how often the app was successfully loaded and available to users. Serves as the baseline for measuring adoption. |
| **journey_start_count** | Indicates how many times users began your game. Helps measure interest and discoverability of your app’s entry points. |
| **journey_progress_count** | Reveals how actively users move through your app. Sudden drops may indicate friction or confusing steps. |
| **journey_interaction_count** | Measures user engagement within your app. Helps identify whether users are actively interacting or passively abandoning flows. |
| **journey_end_count** | Shows how many users reached an end state. Useful for understanding overall throughput and completion volume of your game. |
| **start_rate** | Measures the percentage of app loads that result in a user starting the game. Helps evaluate whether users are discovering and choosing to engage with your app. |
| **completion_rate** | Measures the percentage of times a user has started your game and successfully reached completion. Helps identify drop-off problems and assess the effectiveness of your app’s design. |
| **sessions_per_day** | Shows how frequently users engage with your app on average. Helps distinguish between occasional use and repeat engagement. |
| **median_session_duration_seconds** | Indicates how long users typically spend in your app. Helps assess game complexity, engagement depth, and the impact of changes to the game flow. |

You can download a CSV of your daily Journey metrics over a 30-day lookback period.
## Progress funnel

The Progress funnel shows how far started Journeys progress through your app. It appears below the daily metrics table when progress data is available.

![Journeys-2](../../assets/analytics/journeys-progress-funnel.png)

The chart combines Journey starts across the dates with progress data. Its summary shows the number of starts included, the UTC date range, and how many days in that range have progress data. Progress is counted from the day a Journey starts and the following day (UTC); dates without progress data are omitted.

- The line shows the share of all Journeys started that reached each progress milestone you’ve set in your app. “All starts” is the 100% baseline.
- The bars show the share of all Journeys started that dropped off between the previous milestone and the current one. Taller bars indicate more drop-off.
- Hover over a milestone to see the number of Journeys reached and its share of all starts. Hover over a drop-off bar to see the count and share that dropped off since the previous milestone.

If progress data is not yet available for the included dates, the chart explains that and daily activity remains available in the table above. If no Journeys reached a milestone above 0%, the chart reports that there are no positive milestones to show.
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Direct Launch for Games

Direct launch opens a game in expanded mode when a player starts it from a supported discovery surface.

This reduces friction between discovering a game and playing it: players land on an interactive screen right away, which makes it easier to try a game from **Daily Games**, **Featured**, **Play Again**, or **Category** surfaces.

## **Version requirements**

- **Preferred:** Devvit CLI `0.15.3` or higher.
- **Minimum allowed:** Devvit CLI `0.14.6` or higher.

## **Default and direct launch behavior**

By default, a game plays in the feed.

Direct launch opens the game in [expanded mode](https://developers.reddit.com/docs/capabilities/server/launch_screen_and_entry_points/view_modes_entry_points#switching-between-view-modes) when a user opens it from Featured, Recent, or Category surfaces.

:::note
You’ll want to make sure your game supports and is designed for expanded mode before enabling direct launch in your app.
:::

## **Configure devvit.json**

1. Add the reserved `_direct_launch` entrypoint under `post.entrypoints`.
2. Point its `entry` to the screen that is best for immediate interaction. It can point to the same screen as another entrypoint if that screen is appropriate for direct launch.

```json
{
"$schema": "https://developers.reddit.com/schema/config-file.v1.json",
"name": "syllo-app",
"post": {
"dir": "dist/client",
"entrypoints": {
"default": {
"entry": "splash.html"
},
"_direct_launch": {
"entry": "play.html"
}
}
}
}
```

In this example, the default entrypoint remains `splash.html`, while Direct Launch starts at `play.html`.
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# View Modes, Launch Screens, and Entry Points
# Overview

Devvit’s interactive framework gives you powerful ways to shape how users experience apps, from launch screen to expanded screen viewing. With view modes, HTML-based launch screens, and multiple entry points, you can design apps that feel native and respond to how users interact across the Reddit platform.

Expand All @@ -12,6 +12,10 @@ View modes define how your app appears:

This is an example of an inline launch screen:

<img src={require('../../../assets/quiz_planet_inline_screen.jpg').default} alt="Inline launch screen" style={{maxWidth: '350px', height: 'auto'}} />
<img
src={require("../../../assets/quiz_planet_inline_screen.jpg").default}
alt="Inline launch screen"
style={{ maxWidth: "350px", height: "auto" }}
/>

**Entry points** act as a router that organizes your app across different view modes. Each entry point specifies the initial HTML file for the specific context. A user might experience your app inline, when it’s embedded in a post, or launch it in expanded mode for a larger, full-screen mobile experience.
1 change: 1 addition & 0 deletions sidebars.ts
Original file line number Diff line number Diff line change
Expand Up @@ -220,6 +220,7 @@ const sidebars: SidebarsConfig = {
"capabilities/server/launch_screen_and_entry_points/launch_overview",
"capabilities/server/launch_screen_and_entry_points/view_modes_entry_points",
"capabilities/server/launch_screen_and_entry_points/launch_screen_customization",
"capabilities/server/launch_screen_and_entry_points/direct-launch-games",
],
},
],
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -1,38 +1,54 @@
# Journeys Dashboard

Once you’ve implemented [Devvit Journeys](./devvit-journeys.md), you’ll be able to see how users are engaging with your app. You’ll find Journeys analytics on the App Details page, under the Analytics tab.
Once you’ve implemented [Devvit Journeys](./devvit-journeys.md), you’ll be able to see how users are engaging with your app. You’ll find Journeys analytics on the App Details page, under the Analytics tab.

## Metrics

Journey metrics are displayed in a dedicated section below the existing engagement metrics.

![Journeys-1](../../assets/analytics/journeys-dashboard.png)

## Understanding your data
You can download a CSV of your daily Journey metrics over a 30-day lookback period.

### Understanding your data

Journey analytics data is aggregated into a single record per app per UTC day. This data helps you understand the user’s experience of your app. At a high level:
Journey analytics data is aggregated into a single record per app per UTC day. This data helps you understand the user’s experience of your app. At a high level:

* **Start Rate**: Are users engaging with my app?
* **Completion Rate**: Are users successfully finishing the game?
* **Sessions per User**: Are users coming back?
* **Median Session Duration**: How much time are users spending in my app?
* **Journey Progress & Interaction Events**: Where are users engaging or getting stuck?
- **Start Rate**: Are users engaging with my app?
- **Completion Rate**: Are users successfully finishing the game?
- **Sessions per User**: Are users coming back?
- **Median Session Duration**: How much time are users spending in my app?
- **Journey Progress & Interaction Events**: Where are users engaging or getting stuck?

## Journeys insights
### Journeys insights

Raw event counts show overall Journey activity and usage volume.
Raw event counts show overall Journey activity and usage volume.

Rate- and duration-based metrics help developers evaluate Journey adoption, engagement, and completion, making it easier to identify trends and diagnose issues.

| Metric | What it tells you |
| ----- | ----- |
| **utc\_day** | Lets you analyze app performance over time and identify trends, regressions, or the impact of releases. |
| **app\_ready\_count** | Shows how often the app was successfully loaded and available to users. Serves as the baseline for measuring adoption. |
| **journey\_start\_count** | Indicates how many times users began your game. Helps measure interest and discoverability of your app’s entry points. |
| **journey\_progress\_count** | Reveals how actively users move through your app. Sudden drops may indicate friction or confusing steps. |
| **journey\_interaction\_count** | Measures user engagement within your app. Helps identify whether users are actively interacting or passively abandoning flows. |
| **journey\_end\_count** | Shows how many users reached an end state. Useful for understanding overall throughput and completion volume of your game. |
| **start\_rate** | Measures the percentage of app loads that result in a user starting the game. Helps evaluate whether users are discovering and choosing to engage with your app. |
| **completion\_rate** | Measures the percentage of times a user has started your game and successfully reached completion. Helps identify drop-off problems and assess the effectiveness of your app’s design. |
| **sessions\_per\_day** | Shows how frequently users engage with your app on average. Helps distinguish between occasional use and repeat engagement. |
| **median\_session\_duration\_seconds** | Indicates how long users typically spend in your app. Helps assess game complexity, engagement depth, and the impact of changes to the game flow. |
| Metric | What it tells you |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **utc_day** | Lets you analyze app performance over time and identify trends, regressions, or the impact of releases. |
| **app_ready_count** | Shows how often the app was successfully loaded and available to users. Serves as the baseline for measuring adoption. |
| **journey_start_count** | Indicates how many times users began your game. Helps measure interest and discoverability of your app’s entry points. |
| **journey_progress_count** | Reveals how actively users move through your app. Sudden drops may indicate friction or confusing steps. |
| **journey_interaction_count** | Measures user engagement within your app. Helps identify whether users are actively interacting or passively abandoning flows. |
| **journey_end_count** | Shows how many users reached an end state. Useful for understanding overall throughput and completion volume of your game. |
| **start_rate** | Measures the percentage of app loads that result in a user starting the game. Helps evaluate whether users are discovering and choosing to engage with your app. |
| **completion_rate** | Measures the percentage of times a user has started your game and successfully reached completion. Helps identify drop-off problems and assess the effectiveness of your app’s design. |
| **sessions_per_day** | Shows how frequently users engage with your app on average. Helps distinguish between occasional use and repeat engagement. |
| **median_session_duration_seconds** | Indicates how long users typically spend in your app. Helps assess game complexity, engagement depth, and the impact of changes to the game flow. |

You can download a CSV of your daily Journey metrics over a 30-day lookback period.
## Progress funnel

The Progress funnel shows how far started Journeys progress through your app. It appears below the daily metrics table when progress data is available.

![Journeys-2](../../assets/analytics/journeys-progress-funnel.png)

The chart combines Journey starts across the dates with progress data. Its summary shows the number of starts included, the UTC date range, and how many days in that range have progress data. Progress is counted from the day a Journey starts and the following day (UTC); dates without progress data are omitted.

- The line shows the share of all Journeys started that reached each progress milestone you’ve set in your app. “All starts” is the 100% baseline.
- The bars show the share of all Journeys started that dropped off between the previous milestone and the current one. Taller bars indicate more drop-off.
- Hover over a milestone to see the number of Journeys reached and its share of all starts. Hover over a drop-off bar to see the count and share that dropped off since the previous milestone.

If progress data is not yet available for the included dates, the chart explains that and daily activity remains available in the table above. If no Journeys reached a milestone above 0%, the chart reports that there are no positive milestones to show.
Loading
Loading