No. The Hustle dashboard is still where you build modules, set targeting rules, and configure local lists. SleekView is the data view the dashboard does not give you. Build in Hustle, read and triage in SleekView. The two tools live side by side and never overwrite each other's settings.

Yes. SleekView reads the wp_hustle_* tables both versions write to. Pro features like A/B test variants and additional integration metadata write extra columns into the same tables, and SleekView surfaces them automatically as soon as you add them to your column picker. There is no schema lock-in either way.

Yes. Export the filtered slice to CSV, then upload to your tool of choice, or use SleekView row actions to push selected rows to a webhook for tools like HubSpot, Mailchimp, ActiveCampaign, or Kit. The webhook payload includes any inline tags or notes you added in the table.

No. SleekView is admin-only. It runs database queries when an admin opens the view. Front-end pop-ups, slide-ins, embeds, and the social bar continue to render and submit at the same speed Hustle delivers without SleekView installed at all.

Yes. SleekView gates access by WordPress capability. Map your marketing role to a custom capability, attach that capability to the view, and the role can read and tag entries without ever touching site admin. The view respects the same permissions everywhere it appears.

Yes. Each site has its own wp_hustle_* tables, and SleekView opens them per site, with no cross-site leakage. A network admin can switch between sites and see only the entries that belong to that site. There is no aggregated network-wide view, by design.

If your modules write referrer or page URL into Hustle's form_data field, SleekView surfaces it as a column. Hustle stores form_data as serialised meta on the entry, so the column shows the parsed value. You can then sort by page or filter to a specific URL to credit the right post.

Hustle keeps wp_hustle_entries rows even after a module is deleted, since the entries are independent records. SleekView shows them with the module column flagged as missing or with the historical module name preserved in the entry data. The opt-ins themselves do not disappear.