Dub — Shared link analytics

Analytics DashboardSee it liveapp.dub.co

A public link analytics view pairs a single headline metric and trend chart with tabbed breakdowns for referrers, geography, and devices.

Dub — Shared link analytics — captured interface — Viewport capture · opening screen

Public demo · 2026-09-05Open full image ↗

Search & discovery Dashboards

Why this pattern works

Public shared analytics for d.to/try, linked from Dub’s live demo.

Design notes

Surface: Public shared analytics for d.to/try, linked from Dub’s live demo.
Navigation: Top-level site navigation remains above a compact filter and time-range toolbar.
Layout: Headline clicks metric, broad trend chart, then two-column breakdown panels.
Density: Moderate; a clear overview precedes denser breakdown rows.
Color: White and pale gray, dark text, restrained blue chart fill.
Type: Compact sans labels and a larger metric.
Pattern: Keep time range and filters adjacent to the chart they affect.
States: This is a public shared view; data changes over time. Signed-in management and empty/error states were not captured.
Don't: Do not confuse a public report with the authenticated analytics workspace.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Dub — Shared link analytics
Source: https://app.dub.co/share/dash_6NSA6vNm017MZwfzt8SubNSZ
Swipefile reference: https://swipefile.design/ref/dub-link-analytics/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Public shared analytics for d.to/try, linked from Dub’s live demo.
- nav: Top-level site navigation remains above a compact filter and time-range toolbar.
- layout: Headline clicks metric, broad trend chart, then two-column breakdown panels.
- density: Moderate; a clear overview precedes denser breakdown rows.
- color: White and pale gray, dark text, restrained blue chart fill.
- typography: Compact sans labels and a larger metric.
- pattern: Keep time range and filters adjacent to the chart they affect.
- states: This is a public shared view; data changes over time. Signed-in management and empty/error states were not captured.
- dont: Do not confuse a public report with the authenticated analytics workspace.

Useful for: Public shared analytics for d.to/try, linked from Dub’s live demo.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Public shared analytics for d.to/try, linked from Dub’s live demo.

Dub — Shared link analytics

Make it your own

Keep exploring