No. Pretty Links' built-in reports keep working. SleekView Charts adds a chart-card dashboard that joins the CPT with the click table in a way the native UI never does. Most teams use the reports tab for ad-hoc drill-downs and the SleekView dashboard for weekly review.

Yes. Pro features like keyword auto-linking, link splits, and category-based redirects add fields to the same CPT and config tables. Chart cards surface those as additional fields, so a split-variant Bar card or a category-based donut is one configuration step in the agent UI.

Yes. Pretty Links categories are a taxonomy on the CPT, so a per-card filter scopes the dashboard to one program (affiliate, newsletter, podcast, internal). Saved dashboards can be cloned per category with minimal effort.

Yes. A Bar card with a custom expression on unique clicks divided by total clicks per link surfaces unique-click rate. Useful for flagging bot-heavy traffic where a webinar link sits at 44% unique while organic links sit at 78%.

No. SleekView Charts only renders inside WP Admin and never touches the redirect path visitors hit. Pretty Links' redirect controller and click logging keep running unchanged. Front-end performance is identical to running Pretty Links alone.

Yes. Pretty Links stores redirect type in post meta, and a donut grouped by redirect type renders the distribution. Useful before an SEO audit to confirm legacy 302s have been upgraded to 301s for ranking equity.

Yes. Each card supports an export-data action that downloads the aggregated rows as CSV. Useful for handing finance a top-links revenue table or for sharing trend data with an external dashboard that doesn't read WordPress directly.

The dashboard reflects whichever cleanup rule Pretty Links enforces. If clicks cascade-delete with the post, the chart counts drop accordingly. If they persist as orphans, an orphan-click filter surfaces them so editors can decide whether to archive or remove them manually.