A bookmark that only remembers the page, not the filters or drill level, isn't really a bookmark

What it is

A bookmark that records only "which page" (URL-path level) is half a bookmark: opening it lands on the page's default state, while the filters, drill level, sort, and view layout the user had are all lost. A bookmark's value is the state, not the location — it should record "the chart I was looking at," not "the room the chart lives in."

Why it happens

Position-level bookmarks fail because analytical state is decoupled from page structure: in modern analytical surfaces, the same page in different states is entirely different evidence (a filtered versus unfiltered year-over-year table are two conclusions), and the page path carries none of that difference. A complete bookmark therefore encodes state as a first-class citizen (the serialisation checklist from the earlier card), including the easily missed view configuration — layout, chart visibility, column choice and order, zoom and focus. The acceptance standard from the user's seat is fidelity: opening the bookmark, without touching anything, the surface matches the saved moment item by item.

Where it stops holding

Recording completeness must balance two constraints: URL length (browsers and chat apps dislike very long links) motivates the "state stored server-side, link carries only an ID" pattern — the production standard anyway; and the privacy edge — state may contain sensitive filter values, filtered per recipient's permissions on share (linking to the fourth card). Not every state deserves recording either: pure appearance preferences (theme colour) are not analytical state and only add noise; the recording scope should be limited to "state that affects data presentation and conclusions."

Applying it

• Implement bookmarks as server-side state storage plus short links, with the state list matching the earlier card's acceptance checklist.
• On save, preview the recorded state items to the user and allow unchecking.
• Verification: perform five operations (two filters, one drill, one sort, one layout change), save a bookmark, reopen and verify item by item; anything missing means the recording scope is too narrow.

Related

• Same group: U6.10.1 Analytical state must be encodable as a reproducible link or snapshot · U6.10.2 After the underlying data updates, an old bookmark's conclusion may no longer hold · U6.10.4 A share-link recipient may see different data due to insufficient permissions · U6.10.5 Bookmarks need human-readable names to be findable again
• Nearby: U6.02.3 The scope of linkage needs to be controllable · U6.10.1 Analytical state must be encodable as a reproducible link or snapshot
• Search terms: bookmark state · server-side state · saved view