Yes, the add-on is what writes the integration usermeta keys SleekView reads (subscriber_id, last_synced_at, applied_tag_ids). Without it the LifterLMS progress table still exists, but the join to Kit subscribers is empty, so cards referencing sync activity fall back to LifterLMS-only counts.

Yes. Page-level filters propagate to every card, so picking a date range, a course post_id, or a membership tier recomputes every Number, Pie, Bar, and Area on the dashboard. Saved views per launch keep historical numbers stable.

Yes. The integration writes a sync_status meta_key when an API call fails. A Pie card grouped on that value gives the share of succeeded versus failed syncs over a window, and a Number card counts failures in the last 24 hours for an at-a-glance health check.

Yes. The add-on retained the convertkit slug across the rebrand to Kit, and the usermeta keys it writes did not change. SleekView reads the same column names regardless of which release of the add-on is installed.

Reads run against the live tables on dashboard load, so a sync event just written by the integration appears immediately on the next refresh. Heavier aggregates (per-tag totals across the catalogue year-to-date) opt into a configurable cache.

Yes. Each card exports its underlying aggregated rows as CSV or JSON. Useful for marketing ops reviews that need to combine the WordPress-side sync volume with Kit's own click and open numbers.

Yes. SleekView Charts reads the same usermeta rows the SleekView Table view writes to, so a manual re-sync recorded against a user recomputes the dashboard on the next load. The LifterLMS hooks fire normally so downstream actions continue to run.

Yes. Each subsite has its own LifterLMS tables and integration usermeta, and SleekView Charts reads the current subsite. Cross-site aggregation is not supported, but per-site dashboards behave as expected and can be scoped per role.