Activity Log
The Activity Log provides a complete audit trail for every event that occurs on a subscription or customer account. It records who made what change, when, and why.
Accessing the Activity Log
- Subscription level: Go to a subscription’s details page → Activity Log tab
- Account level: Available on the customer account page
Activity Log Fields
| Field | Description |
|---|---|
| Timestamp | When the event occurred |
| Event | Description of what happened |
| Event Type | Category of the event (e.g., Plan Change, Cancellation, Payment) |
| Category | Broader classification for filtering |
| Severity | Event importance level |
| Actor | Who triggered the event (user name and ID) |
| Reason | Why the change was made (if provided) |
| Entity ID | The affected entity’s identifier |
| Account ID | The associated customer account |
| Correlation ID | Tracking ID to link related events across services |
| Related Entities | Other entities involved in the event |
| Metadata | Additional event-specific data (expandable) |
Severity Levels
| Level | Color | Usage |
|---|---|---|
| INFO | Blue | Routine events: subscription created, plan changed, invoice generated |
| WARNING | Yellow | Attention-worthy events: payment retry, approaching expiry, dunning entry |
| CRITICAL | Red | Urgent events: payment failed, subscription cancelled, dunning escalated |
Filtering
The activity log supports filtering by:
- Category — Narrow to specific event categories (e.g., only billing events, only status changes)
- Severity — Show only warnings and critical events to focus on issues
Pagination
Activity logs are paginated at 20 entries per page with previous/next navigation.
What Gets Logged
Every subscription lifecycle event is captured:
- Subscription creation
- Plan changes (upgrade/downgrade)
- Billing frequency changes
- Addon additions and removals
- Pause and resume events
- Cancellation with reason and policies
- Renewal and reactivation
- Invoice generation and payment events
- Dunning entry and recovery
- Status transitions
- Manual amendments
Each entry includes the full context — who did it, what changed, and the metadata needed for compliance auditing.