Skip to content

Commit 8ea33c8

Browse files
authored
Update Devvit Journeys documentation
Removed note about the experimental status of Devvit Journeys and updated the implementation instructions.
1 parent b879a15 commit 8ea33c8

1 file changed

Lines changed: 11 additions & 5 deletions

File tree

versioned_docs/version-0.13/capabilities/analytics/devvit-journeys.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,6 @@ Devvit Journeys adds a telemetry stream to your app that tracks the entire lifec
88

99
A journey has a defined start and end point. Progress is tracked throughout and ends with a completion status. You can also attach optional game-specific data (like win/loss results or scores) at the end.
1010

11-
:::note
12-
This is currently an experimental feature, and you'll need to [apply](../analytics/analytics-overview.md#how-to-apply) for a spot in our beta program to implement Devvit Journeys.
13-
:::
14-
1511
## Journey map
1612

1713
A journey map is a structured, instrumented flow that tracks a player’s progression through a specific experience in your game. Think of your journey map as a series of checkpoints (events) in your game, with:
@@ -147,7 +143,17 @@ Telemetry is restricted by a server-side allowlist. Only approved apps can emit
147143

148144
## Getting started
149145

150-
Follow these steps to implement journey tracking in your app.
146+
Here's how to implement journey tracking in your app.
147+
148+
### Permissions
149+
150+
Set Journeys permissions to `true` in `devvit.json`.
151+
152+
```
153+
"permissions": {
154+
"journeys": true
155+
},
156+
```
151157

152158
### Server events
153159

0 commit comments

Comments
 (0)