Skip to main content
Custom dashboards turn read-only SQL queries into reusable charts. Build one for a single site or compare selected sites across an organization, then use one date picker to update every card.

Choose a dashboard scope

A site dashboard queries one site’s analytics. Its cards use the same site-scoped virtual tables as the SQL query builder, so you do not add a site_id filter.Start from a blank dashboard or use a template:
  • Traffic overview — 6 cards
  • Content — 4 cards
  • Engagement — 5 cards
Organization dashboards respect site access for every viewer. If a dashboard includes sites someone cannot access, tinyanalytics hides those sites and shows how many were omitted without revealing their IDs or names.

Build a dashboard card

1

Create or open a dashboard

Open Dashboards at the site or organization level. Choose a template for a working set of cards, or start blank.
2

Write the query

Add a card and write a read-only SELECT against the available scoped tables. The preview shows the returned columns as you work.
3

Choose a visualization

Pick a line, area, bar, stat, horizontal bar, pie, map, calendar, or table visualization.
4

Map the result columns

Choose which query columns provide the X axis, value, label, and series. The required mapping changes with the visualization.
5

Arrange and save

Drag cards to move them, resize them from the edge, then save the dashboard. The dashboard records the layout, queries, mappings, selected site scopes, and creator.

Which visualization fits your query?

How do cards follow the date range?

Cards respond to the dashboard’s global date picker and time bucket automatically. To bucket a time series by the selected granularity, use {{bucket}} in your SQL. tinyanalytics replaces it with the matching hour, day, week, or month interval before the query runs.
Leave the date range out of a query only when the card should read across all retained data.

Who can edit an organization dashboard?

Any organization member can create a dashboard using only sites they can access. The organization’s owners and admins, plus the dashboard’s creator, can edit or delete it. The creator’s name appears on the dashboard so teammates know who owns its definition.
An organization query that calculates users across several sites can produce different semantics depending on the SQL. Use the built-in templates when you want the same sum of per-site users used by the organization overview, where a person visiting two sites counts once on each site.

Frequently asked questions

No. Cards follow the dashboard’s global date picker and time bucket automatically. If a query deliberately leaves the range out, that card reads across all retained data.
Create an organization dashboard, scope the card to All accessible sites or a selected subset, and include site_id in the query’s SELECT and GROUP BY. Map site_id as the series; the dashboard displays the corresponding site names.
tinyanalytics removes the inaccessible sites from that viewer’s results and shows how many sites were hidden. It does not reveal their IDs or names.
No. Organization dashboards stay inside the organization and follow each viewer’s site permissions. Use public dashboards for the supported site-level sharing options.

Verify

Change the dashboard date range and confirm every time-scoped card refreshes. For an organization card, compare the site names shown with the selected scope and confirm a teammate with narrower access sees only their permitted sites.

Organization overview

Read the built-in portfolio view.

SQL query builder

Write and test the queries your cards run.

Metric definitions

Understand the events and properties you can query.

Public dashboards

Share a supported site-level dashboard.