No. It runs alongside. The default WPUF Transactions and Subscribers screens keep working, and SleekView adds a free-form chart dashboard that reads the same custom tables. Sites use both, with the SleekView dashboard tuned to the team's specific questions while the WPUF screens handle row-level admin work.

Yes. Each chart card targets one data source, so one card reads wpuf_transaction while another reads wp_posts with the WPUF form filter, and the canvas can hold cards from any source side by side. The result is one screen with revenue, subscriber, and submission charts in a single view.

WPUF marks the transaction type on wpuf_transaction. Filter the card to type equals pay_per_post or subscription, and the chart only counts matching rows. Build two cards side by side to compare the two revenue streams on the same dashboard.

Yes. Each card supports filters, and a dashboard-wide filter applies to all cards. Build a per-form dashboard by setting a filter on the WPUF form id, and every card on the canvas re-renders against just the submissions and transactions linked to that form.

Yes. SleekView's chart aggregation runs on the indexed columns the WPUF Table view already uses, so a transactions table with hundreds of thousands of rows aggregates in well under a second for typical groupings. Saved layouts can also cache aggregation results between reloads.

Yes. A Pie slice, Bar column, or Area band can be clicked to open the matching filtered Table view. The drill-through preserves the active dashboard filter, so the row-level list shows exactly the transactions, subscribers, or posts the chart segment represented.

Yes. Pay-per-post charges land in wpuf_transaction just like pack purchases, and coupon usage is stored as transaction meta. Build a Bar of redeemed coupons by code and an Area of pay-per-post revenue per day next to the core subscriber and form charts.

Yes. Save a dashboard, gate it by capability, and finance, content ops, and admins each load the layout tuned to their workflow. The same underlying tables drive every layout; the chart cards on the canvas vary per role.