No. Calendarize It still owns the rich front-end views. SleekView Charts is an admin-side dashboard that reads the same tribe_events data and aggregates it into chart cards. The two work side by side so editors get aggregates and visitors still get the styled public views.

By category name from the Tribe taxonomy term. Calendarize It color codes the same terms on the front-end, so the dashboard mix and the public color mix describe the same distribution under different visual treatments.

Yes when the events carry view-mode meta. Calendarize It writes meta on events that should appear in specific public views. Cards can filter on that meta so the dashboard scopes to one view configuration when the team is iterating on a particular layout.

Yes. Calendarize It builds on top of Tribe, so the underlying tribe_events CPT is the same. A dashboard built for Calendarize It works against a plain Events Calendar install, with the view-mode filters simply unused if those fields are not populated.

Yes. Joins to tribe_venue and tribe_organizer through _EventVenueID and _EventOrganizerID expose those records as columns. A bar card grouped on either resolves the linked post ID into a readable venue or organizer title for the chart label.

Yes when recurring events are present. Tribe expands each recurrence into a separate event post with its own start date, so the weekly area card counts each occurrence and the curve reflects the real programming density rather than just parent rules.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when the team needs the actual list of events behind a category slice or a thin week in the density curve.

Analytics plugins typically track page views, not the underlying schedule. SleekView Charts reads the events CPT directly and aggregates planning data, so the dashboard answers programming questions about the schedule itself rather than traffic to the public calendar pages.