Recommended dashboard structure
Use this vertical order:
Global filter bar
Date range: Today, 7 days, 30 days, 90 days, custom Compare with previous period Content type: All, Normal Article, Mango Bite, Mango Lens Category: Financial, Business, Market, and others Export report Last data refresh timestamp
Keep filters global so every card updates together. Display active filters as removable pills below the filter bar.
Use six cards maximum:
Page views
Unique visitors
Organic clicks
Search impressions
Average engagement time
Published articles
Each card should show:
Current value
Change versus previous period
Small trend sparkline
Tooltip explaining the metric
Avoid putting Cloud Run metrics in the primary KPI row. Editorial performance and infrastructure health serve different decisions.
Default chart: Page views and organic clicks over time
Recommended behavior:
Line chart for page views
Second line for organic clicks
Optional area fill only for page views
Daily granularity for 7–90 days
Hourly granularity for Today
Hover tooltip with date, value, and percentage change
Click a point to filter the article table to that period
Allow users to switch the chart metric to:
Views
Organic clicks
Search impressions
Newsletter clicks
Articles published
4. Action lists below the chart
Use ranked tables rather than more charts:
Top-performing articles
Articles losing traffic
High impressions, low CTR
Recently published articles
Articles with technical problems
Each row should link directly to the article analytics detail page. Analytics: answer “why did performance change?”
Analytics should be a deeper workspace with a persistent filter bar, a trend chart, breakdown tabs, and a sortable article table. The strongest patterns come from Dub, Patreon, Mapbox, and Resend: one dominant timeline, then segmented breakdowns and detailed rows.
Related Notes