Event Espresso writes registrations to esp_registration, transactions to esp_transaction, tickets to esp_ticket, and attendees to esp_attendee. The plugin's Reports tab shows headline numbers but stops short of letting an organizer slice them by ticket type, by event, or by week without an add-on.

SleekView Charts reads those tables directly. Registration date, status, transaction amount, payment method, and ticket type promote to columns that any chart card can group or aggregate on. The dashboard answers the questions an event business actually runs: weekly revenue, paid versus pending, registration volume per event, ticket mix.

Because reads use standard SleekView dataset joins, attendee meta, custom registration questions, and price modifiers all appear alongside core columns. The chart dashboard sits next to the table and kanban views built from the same dataset.

Event Espresso is a strong transactional engine: it captures registrations, processes payments, enforces capacity, and ties everything back to a registrant record. What it does less well is the weekly review where an organizer wants to ask one composite question (paid registrations per ticket tier per event over the last fourteen days) without leaving WordPress. SleekView Charts treats the Espresso tables as a normal SleekView dataset and lets that question render as a four-card dashboard.

Saved views become the rituals of the role: Monday revenue review, mid-week capacity check, Friday close-out. The plugin keeps owning the registrations; SleekView just makes the reporting layer look like the operations a real event business runs.