No. SleekView reads what the Kit plugin already stores locally — cached forms, tags, sequences, and the subscribe-attempt log. The Kit plugin handles authentication against Kit's API, so credentials live in one place and SleekView simply reads the resulting local cache and event log.

No. Contacts created inside Kit's own interface — through Kit-hosted landing pages, manual imports, or third-party integrations — live entirely in Kit's cloud. SleekView surfaces only events that your WordPress site triggered, which is the slice the Kit plugin records locally.

Yes. Once the join is configured, the form, tag, and sequence columns sit next to each other on every attempt row. Group or filter by any of them — for example, all attempts that triggered the Course onboarding sequence in the last 7 days — and the answer is one click.

Yes. SleekView reads the same plugin tables and options that the free and Pro versions both write to. Pro features like landing pages or restricted content add extra columns or tables, and SleekView surfaces whatever the plugin records, so upgrades expand the visible dataset rather than break it.

Yes. Filter the table to the rows you need, click export, and the CSV matches exactly what is on screen — same filters, same columns, same sort. No accidental full-table exports, which matters when the log contains email addresses you would prefer not to circulate broadly.

Yes. SleekView is admin-only and bypasses front-end page cache entirely. Object-cache integrations cache the SleekView query results when configured, but front-end performance is unaffected because no SleekView code runs for non-admin requests at all.

If the Kit plugin caches the automation or sequence ID alongside subscribe attempts, SleekView surfaces it as a column. SleekView does not call Kit's automations API directly — that lives in Kit — but the plugin's local record of which automation a signup enrolled into is fully filterable.

Re-open SleekView's agent UI and point it at the renamed table or column. Joins are stored by name in SleekView's configuration, so a Kit plugin update that renames a table is a one-time reconfiguration rather than data loss. Existing saved views update once the new mapping is saved.