Charts reads em_booking and em_event directly. SleekView connects to both CPTs and exposes the postmeta keys EventPrime writes, so the dataset has em_payment_status, em_total_price, em_event_id, em_ticket_id, and em_attendee_count ready for groupBy or value duty across every card on the dashboard.

Yes. A bar card grouped by em_ticket_id and summing em_total_price returns revenue per ticket. The dataset joins the parent em_event's ticket definitions so the chart shows the ticket name instead of the numeric ID EventPrime stores in the booking row by default.

EventPrime stores em_payment_status as readable strings like paid, pending, refunded, and failed. SleekView reads those values directly so the donut chart shows the status name without any extra mapping, with refund and fail counts updating automatically as the gateway posts back to the booking row.

Yes. Every card has a filter scope that can target a single em_event_id, a category, or a date range on post_date. The filter applies on top of the aggregation, so a daily pace card scoped to one event shows only that event's booking trend through the calendar.

The revenue card sums em_total_price for rows in paid status only by default. Refunded bookings flip em_payment_status to refunded and drop out of the sum on the next refresh, so the chart matches what actually cleared rather than the gross requested amount before the gateway processed the refund.

Yes. The free EventPrime plugin writes the em_event and em_booking CPTs with the same postmeta keys. Premium add-ons layer additional fields on top, but the core schema is shared, so a dataset built for the premium tier renders against the free plugin with the add-on-specific cards disabled when those fields are absent.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when finance needs the gateway-side booking rows behind a revenue total or when a venue partner asks for the bookings behind a specific event row across the season.

Reporting plugins typically build a parallel data layer fed by hooks on em_booking writes, which means a second moving part to keep in sync. SleekView Charts reads em_booking directly, so the dashboard reflects the same row the booking screen edits without an extra sync step or stale cache between dashboard and admin views.