What gets logged
The Activity Log records operator-facing outcomes, not internal diagnostics. Logged events include: Subscription events- Subscription created during storefront checkout
- Subscription paused, resumed, or canceled
- Plan change scheduled
- Shipping address updated
- Next delivery skipped
- Renewal approval approved or rejected
- Force renewal requested
- Renewal succeeded or failed
- Dunning started
- Retry executed
- Case recovered or unrecovered
- Retry schedule updated manually
- Cancellation case started
- Retention offer applied
- Cancellation reason updated
- Cancellation finalized
Event record
Each log entry captures:| Field | Purpose |
|---|---|
| Event type | The specific event from the taxonomy above |
| Actor | Who or what triggered the event: user, customer, system, or scheduler |
| Previous / new state | A compact before/after summary of the relevant fields that changed |
| Changed fields | A structured diff showing field-level before and after values |
| Reason | An optional operator-facing explanation (e.g. cancellation reason, approval note) |
Admin surfaces
The Activity Log is accessible in two places: Global Activity Log page (/subscriptions/activity-log) — a cross-subscription audit view with filtering by event type, actor, and date range. Quick presets let you filter to a specific domain (Subscriptions, Renewals, Dunning, Cancellations) in one click. Clicking any row opens a detail drawer with the full event payload.
Subscription detail timeline — an embedded Activity Log section on each subscription detail page, scoped to that subscription’s history. Useful for reviewing the full lifecycle of one subscription without leaving its detail view.
One common first event in that timeline is subscription.created, recorded when a customer completes subscription checkout through the storefront.