Update from code changes: user flow analytics now always on - #7099
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
approved these changes
Aug 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
User flow analytics is now generally available on the dashboard analytics page, so the docs no longer need to hedge that the card may not be available for a deployment.
The User Flow card on the analytics page previously rendered only when a feature flag was enabled. That flag has been removed, so the card now always appears for every deployment. No behavior of the chart or entry-point selector changed. See https://github.com/mintlify/mint/pull/10424
Changes
Note
Low Risk
Documentation-only wording changes with no product, security, or data-handling impact.
Overview
Updates User flow copy on the user engagements analytics page to match user flow being always on in the product (feature flag removed).
In English, Spanish, French, and zh
user-engagements.mdx, the closing paragraph no longer says data appears only when User flow is available for your deployment. It now states that data appears after your documentation receives visitor traffic, with no deployment-specific caveat.Reviewed by Cursor Bugbot for commit 409b168. Bugbot is set up for automated code reviews on this repo. Configure here.