Charts reads the postmeta the add-on writes. Every field defined in Attendee Information is stored as postmeta on each tc_tickets_instances row, and SleekView exposes those keys as dataset columns so you can groupBy dietary, session, shirt size, or any other custom field on the same level as core ticket columns.

Yes. The dataset joins tc_tickets through ticket_type_id, so a card can filter to one ticket type or one event scope. A bar grouped by ticket_type_id with the ticket name resolved through the join returns attendees per ticket type for the active event.

The dataset joins tc_orders on the order_id meta key. Filtering the join to orders with completed status keeps refunded, pending, and failed orders out of the attendee count. Switching the filter scope returns the gross count including refunds when finance needs that number.

Yes. Every card has a filter scope that can target a single ticket_type_id or event, 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 registration curve.

Yes. SleekView refreshes the dataset schema from the postmeta keys present on tc_tickets_instances. A field added in the Attendee Information settings becomes a column available for groupBy or value duty on the next dataset refresh, no SQL or column mapping required.

Yes. The free Tickera plugin writes the tc_tickets_instances CPT, and the Attendee Information add-on writes its custom field values as postmeta on the same rows. SleekView reads both layers, so the dashboard works on a free Tickera install with the add-on enabled.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when catering needs the per-attendee dietary rows behind a count or when finance needs the joined tc_orders rows behind a completed attendee total.

Reporting add-ons typically build a parallel data layer fed by hooks on the ticket instance save action, which means a second moving part to keep in sync. SleekView Charts reads tc_tickets_instances and its postmeta directly, so the dashboard reflects the same row the ticket detail page edits without an extra sync step or stale cache.