Charts reads the ajde_events CPT directly. Submissions from Add Event land in the same CPT as editor-created events with a pending status flag and submitter postmeta. SleekView exposes both core EventOn keys and Add Event submitter keys as dataset columns ready for groupBy or value duty.

Yes. The dataset exposes post_status alongside the Add Event pending flag. A donut grouped by status shows pending, approved, and rejected counts. A filter scoped to pending only narrows every card on the dashboard to the live moderation queue across the calendar.

EventOn stores categories in the event_categories taxonomy. SleekView joins ajde_events to the taxonomy table on term relationships, so a bar grouped by event_categories resolves term IDs into readable category names for the chart labels without manual mapping.

Yes. Every card has a filter scope that can target a specific _evo_submitter_email value, 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 campaign isolates that campaign's contribution.

Yes. SleekView refreshes the dataset schema from the postmeta keys present on ajde_events. A new EventOn add-on that writes additional keys becomes available as columns on the next dataset refresh, no SQL or column mapping required from the editorial team.

Yes. All EventOn add-ons write to the same ajde_events CPT through postmeta. SleekView reads every key on the row, so Add Event submission counts and other add-on metrics like RSVP counts coexist in the same dataset without conflict at the underlying row level.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when the editorial lead needs the per-submission rows behind a category count or when finance needs the submitter list behind a campaign-driven submission spike.

Reporting add-ons typically build a parallel data layer fed by hooks on the EventOn submit action, which means a second moving part to keep in sync. SleekView Charts reads ajde_events directly, so the dashboard reflects the same row the moderator approves without an extra sync step or stale cache.