Charts reads the dedicated Pro tables. SleekView connects to em_bookings, em_tickets, em_tickets_bookings, and em_locations directly so the dataset has the columns Pro actually writes rather than a postmeta shadow copy. Joins to em_events resolve event_id into a readable title.

Yes. A bar card grouped by ticket_id and summing booking_price returns revenue per ticket. The dataset joins em_tickets so the chart shows the ticket name instead of the numeric ID Pro stores on the booking row. Filtering by event scope narrows the chart to one event when needed.

Events Manager Pro stores booking_status as small integers where 0 is pending, 1 is confirmed, 2 is rejected, 3 is cancelled, and 4 is awaiting payment. SleekView maps those values to labels when the dataset is configured so the donut chart shows readable status names rather than the raw integer codes.

Yes. Every card has a filter scope that can target a single event_id, a category, or a date range on booking_date_created. The filter applies on top of the aggregation, so a daily pace card scoped to one event shows only that registration trend.

The revenue card sums booking_price for rows in confirmed status only by default. Refunded or cancelled bookings flip booking_status to 2 or 3 and drop out of the sum on the next refresh, so the chart matches what actually cleared rather than the gross requested amount.

Yes. The free plugin writes the same em_bookings, em_tickets, and em_events tables. Pro adds gateway and form features on top, but the underlying schema is shared, so a dataset built for Pro renders against the free plugin with the gateway-specific cards disabled.

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 registrations behind their event.

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