Yes. The dataset can include etn_attendee rows for both paid and RSVP flows. A pie card grouped on payment status separates the two cleanly, and a bar of top events by attendees treats both kinds equally when the goal is to see the total expected at the door.

Eventin writes payment status and ticket price meta on each attendee row. A sum aggregation on the ticket price column filtered to completed payment status returns gross revenue, with refunds dropping out as the payment status flips on the row.

Yes. The check-in flag on etn_attendee is exposed in the dataset. A pie card grouped on that key shows the checked-in versus pending ratio in near real time, refreshed at whatever interval the dashboard is configured to use during the event.

Yes. Pro features add fields like attendee custom forms, speaker assignments, and Zoom session links. Those land as additional meta on etn_attendee or etn_event. Any meta field exposed in the dataset becomes a chartable column or filter dimension.

Yes. Every card has a filter scope that can target a specific etn_event_id, a category, or a date range. A daily pace card scoped to one event returns only that event's registration trend for the period leading up to its start date.

Yes. Charts is additive and reads the same CPTs Eventin's built-in screens read, so the plugin's own dashboards continue to work normally. SleekView simply adds a configurable, chartable surface on top that the team can build dashboards in without code.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when the box office needs the attendees behind a per-event total, or when finance needs the rows behind a daily revenue spike.

Analytics plugins track page views, not registrations. SleekView Charts reads the Eventin CPTs directly and aggregates the operational data, so the dashboard answers schedule and attendance questions rather than traffic questions, which is the picture the box office actually needs.