Paperform's analytics live at paperform.co: response counts, partial completion rates, payment totals. SleekView already mirrors submissions into a local WordPress table so admins can filter and tag without leaving the site. With Charts, that same table doubles as a reporting source.

Each cached submission row carries form ID, submitted-at, payment status, total, and the answer fields you've pivoted out as columns. Aggregate those columns into Number, Area, Bar, and Pie cards and the dashboard tells you how the embedded forms are actually performing this week without flipping between WordPress and Paperform.

The dashboard is honest about its scope. Partial-submission analytics still belong to Paperform; their dashboard is the source of truth for funnels and abandoned drafts. What SleekView Charts shows is what the WP-side cache holds: completed submissions, their payment state, and the metadata your team uses for triage.

Embedding Paperform on WordPress already means your customers complete the transaction on your domain, so the reporting should live there too. SleekView Charts uses the local cache the team already triages from, which means there's one source the dashboards, the response table, and the WP-side tags all agree on. Revenue and submission-volume KPIs sit next to the orders, posts, and users they relate to, not in a separate tab on a separate domain.

That makes weekly reviews faster and removes the temptation to keep a parallel spreadsheet just for cross-form comparisons. The dashboard never claims to replace Paperform's funnel analytics, since partials and abandoned drafts stay at paperform.co where they belong.