What you save here is one query, which may reference saved metrics; the metric definitions live in Custom metrics.

ConsoleAll-platform analyticsBehaviorBehavior analysis

How to configure

Save from the builder. The first save asks for a name, a description, and a scene. The scene tree is at most three levels. Deleting a scene moves its analyses and boards to unfiled. Further edits save back to the same row, or you can save a copy. The list is ConsoleAll-platform analyticsBehaviorEvent analysis, with favorites, duplicates, and a model filter.

Dashboards are ConsoleAll-platform analyticsOverviewMy dashboards. A card is a saved analysis, a text block, or a divider. The board has its own date, filters, and identity; leave identity alone and each card keeps its own. A board can be the default, and it can be pinned into the web, app, or mini-program shell. Opened inside that shell, it filters to that platform.

Saving needs an analyst or above; turning sharing on or off needs an admin or the owner. An analysis share is a read-only link. A dashboard share is read-only too, and the password may be left empty.

How to read the result

The list shows the model, whether it is a favorite, and whether it is shared. Someone opening the link sees the saved query and cannot change it. The builder exports the current result as CSV. From a result you can open the people list, or create a segment that recomputes daily from the current conditions.

Limits & definitions

Shared analyses and shared dashboards show at most the last 90 days, and filters must be on the project’s share allowlist. SQL cannot compare segments, and it cannot open people or create a segment from the result. Account identity cannot do those either. Creating a monitor from a chart point only stores a draft; it does not become an alert.