No. SleekView reads the acadp_listings custom post type and its postmeta in place. Nothing is copied or synced, every chart query runs against the live wp_posts and wp_postmeta tables, so the numbers always match what the ACADP admin screens show on their own.

Yes. Any custom field ACADP writes to postmeta, including the unlimited custom fields tied to categories, is selectable as a group-by or filter. SleekView lists every meta key present on the acadp_listings CPT in the chart builder.

Yes. Both taxonomies are first-class group-by targets. SleekView joins wp_term_relationships and wp_terms behind the scenes, so charts render with the term name and slug instead of internal IDs. Nested categories and locations are flattened to their lowest level by default.

Yes. Filter acadp_listings by _expiry_date postmeta within a date range and aggregate with Count. A Number KPI showing listings expiring in the next seven days is one of the most useful cards site owners install on their admin dashboard.

SleekView uses indexed wp_postmeta joins and caches aggregated results per chart. A directory we tested with 28,000 acadp_listings across 4 years rendered the full four-card dashboard in under 700ms once the cache warmed up.

Yes. Filter by the _featured postmeta flag set to 1 and the charts will only show paid featured listings. Useful for proving featured-placement ROI to sellers or for splitting the dashboard into free vs paid views side by side.

No. Charts are rendered inside wp-admin behind the manage_options or your configured capability by default, and aggregations like Count, Sum and Average never expose individual rows. Contact emails and phone numbers stay where ACADP put them.

Both work. Fee plan IDs are written to acadp_listings postmeta and WooCommerce orders are queryable from wp_posts where post_type = 'shop_order'. SleekView can chart paid listings, plan distribution, and revenue per plan from those rows directly.