Yes. Cart66 Cloud's data lives on Cart66's servers, so an API key is required to fetch subscriptions, transactions, and subscribers. SleekView reuses the key the WordPress plugin already holds where possible, or you can paste a separate key with read and write scopes.

Each table has its own refresh schedule. Subscriptions and transactions default to a five-minute pull plus webhook updates where Cart66 supports them. Subscriber rollups (LTV, churn buckets) refresh hourly to keep API usage modest. Tighten the intervals if your team needs near-realtime; relax them for huge stores to stay well within rate limits.

Yes. Inline cancellation calls Cart66's cancel-subscription API with the parameters you choose (immediate vs end-of-period, prorate vs no prorate). SleekView reflects the new state once Cart66 confirms; it never marks the local cache as cancelled until the API responds.

Yes if a subscriber's email matches a WordPress user. SleekView joins on email by default and exposes both sides as columns: WordPress role, registration date, last login, plus Cart66 subscription state and MRR. For subscribers without WordPress accounts, the WP-side columns are simply empty.

Yes. Promo codes used at checkout become a column on the transactions table, so a 'sales attributed to LAUNCH25' view is one saved filter. Code-level rollups (uses, gross sales, net of refunds) are derived views you can save alongside the transaction-level view.

Each retry attempt is a row in the dunning history with timestamp and outcome. A 'recovered subscriptions' view filters to dunning sequences that ended successfully, useful for quantifying the value of dunning automation versus letting subscriptions churn passively.

SleekView itself shows the data; alerts are a SleekAI add-on territory. For now, save a view of trials ending in 3 days, scope it to the role that handles trial outreach, and that role checks it as part of their daily routine. WordPress dashboard widgets surface the count for at-a-glance triage.

No. SleekView reads from Cart66's API at scheduled intervals, the same way any third-party integration would. Cart66's dashboard runs on its own infrastructure; SleekView's polling is a small fraction of typical API budgets and is configurable per table to keep usage in line with your account's rate limits.