Renewal Statistics Report

Overview

The Renewal Statistics Report tracks and analyzes subscription renewal patterns and outcomes across different issue groups. It provides detailed breakdowns of subscription statuses, renewal rates, and conversion metrics across various dimensions.

Key Components

Data Dimensions

The report segments data across multiple dimensions:

  1. Customer Type
    • B2C (Business to Consumer)
    • Concierge
  2. Subscription Stage
    • Conversion (First-time renewals)
    • Renewal (Subsequent renewals)
  3. Subscription Level
    • Premium
    • Standard
  4. Purchase Type
    • Self
    • Gift
  5. Processing Method
    • AR (Auto Renewal)
    • Manual

Status Tracking

The report tracks various subscription statuses:

  1. Active Statuses
    • Renewed
    • Renewed by Merge
    • Renewed by Resubscribe
    • Extended by Merge
    • Manually Adjusted
  2. Inactive Statuses
    • Cancelled
    • Merged
    • Expired
    • Awaiting Renewal
    • Pending Cancellation

Implementation Details

Data Collection

  • Processes data by issue groups sequentially
  • Maintains start sizes for each segment
  • Tracks status changes and outcomes
  • Groups data by SKU for detailed product-level analysis

Reporting Process

  1. User selects start and finish issues
  2. System processes each issue group in sequence
  3. Collects and aggregates statistics for each dimension
  4. Generates summary and detailed breakdowns

Usage

  1. Report Generation
    • Enter report title
    • Select start issue
    • Select finish issue
    • Generate report
  2. View Options
    • Summary view showing key metrics
    • Detailed breakdowns by dimension
    • Issue-by-issue analysis

Technical Notes

  1. Data is stored in dedicated statistics tables
  2. Processing happens asynchronously to handle large datasets
  3. Uses WordPress action hooks for extensibility
  4. Integrates with WooCommerce data structures

Known Limitations

  1. Processing is sequential and may take time for large date ranges
  2. Currently limited to issue-based expiry groups
  3. Requires user to have ‘customer_screens’ capability