No. SleekView queries the awpcp_ads, awpcp_categories and awpcp_payments tables in place. Nothing is copied or synced, every chart query runs against the live AWPCP tables, so the numbers always match what the Manage Ads screen shows on its own.

Yes. SleekView joins awpcp_ads to awpcp_categories on ad_category_id and resolves names. Parent and child categories are both supported as group-by targets, with the option to roll children up into their parents for cleaner top-level charts.

Yes. The Extra Fields module writes to its own table that joins back to ad_id. SleekView lets you point at that table as a secondary data source and group-by any custom field, so breed, model year, square footage or any other field becomes a chart axis.

Yes. Filter awpcp_ads by ad_enddate within a date range and aggregate with Count. A Number KPI showing ads expiring in the next seven days is one of the most useful cards AWPCP operators install on their admin dashboard for renewal outreach.

SleekView uses indexed joins and caches aggregated results per chart. A classifieds site we tested with 87,000 awpcp_ads rows across 6 years rendered the full four-card dashboard in under 800ms once the cache warmed up.

Yes. Point a chart at awpcp_payments and aggregate Sum on the amount column, grouped by payment_term_id or by month. Joined back to awpcp_ads on ad_id, you can attribute revenue to specific categories or fee plans.

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 AWPCP put them.

Yes. The is_featured column on awpcp_ads is set whether you use the free flag or the paid Featured Ads module. Group by is_featured for the share, filter by is_featured = 1 to chart only paid placements, or pivot featured share by category to find your best-selling featured slots.