Discover URL state and query IDs
How Celiq saves and shares Discover views using short query IDs instead of long URL parameters.
When you build a view in Discover — selecting fields, applying filters, and choosing a grain — Celiq saves that state automatically and represents it as a short URL:
/discover/ecommerce/orders_analysis?qid=uIo8BOtVi33r8x6giv4cC8The qid parameter is an opaque query ID, similar to the qid in Looker Explore URLs. It replaces the old approach of encoding fields and filters directly in the URL as query parameters.
Why this matters
Before: URLs looked like/discover/ecommerce/orders_analysis?fields=created_at%2Corders_count%2Ctotal_revenue&grain=week
- Long and unreadable
- Exposed internal field names
- Broke when shared if field names changed
/discover/ecommerce/orders_analysis?qid=uIo8BOtVi33r8x6giv4cC8
- Short and shareable
- Stable — the ID persists even if field names change
- Works as a bookmark or Slack link
How it works
When you change fields, filters, or grain in Discover, Celiq saves the current view state server-side and updates the URL. This happens automatically — there is no save button.
The saved state includes:
- Selected attributes and metrics
- Applied filters
- Time grain
Sharing a Discover view
Copy the URL from your browser address bar and send it to a teammate. When they open the link, they see the exact same view you were looking at — same fields, same filters, same grain.
Note: The recipient must have access to the same workspace and the same Reveal. If they don't have permission to see a field (via Data Keys), the query will run with that field hidden.
Legacy URLs
Old-style ?fields= URLs from before June 2026 still work. Celiq reads the field list and restores the view. The URL updates to the new ?qid= format on your next field change.