About this plugin
3+.
3 introduces experimental guest session storage and auto-pruning. Session Shredder builds directly on this already available foundation and adds behavior-based heuristics that predict which sessions are zombies (safe to prune) versus keepers (should be retained).
Highlights
) and conservative rules to identify low-value sessions.
– Configurable rules & thresholds – Tune base age, hard timeout, bounce detection, and cart-protection rules from a dedicated WooCommerce settings screen.
– Safe thresholds – Only considers sessions past a base age window and is biased towards keeping anything that shows meaningful activity or cart value.
g. hard 72h timeout, bounces with no cart value).
– Privacy-first – No PII is stored. Session IDs and countries are hashed; only coarse behavioral data is used.
3 integration – Reads from the WooCommerce session table (supports both legacy and new tables) and plays nicely with the core experimental pruning.
– HPOS compatible – Declares compatibility with WooCommerce High-Performance Order Storage (custom order tables) and never touches orders, only session data.
js visualization of active & pruned sessions per run, and a compact “Recent runs” summary.
– Logging & observability – Uses wc_get_logger() for info/error logging; integrates cleanly with existing WooCommerce logs.
Session Shredder is structured for real-world stores and designed as a companion to WooCommerce’s experimental guest session engine. It stays fully rule-based out of the box, but developers can extend it via hooks if they ever want to plug in external scoring services or AI endpoints.
Why not rely only on the WooCommerce experimental pruning?
– Core experimental pruning is largely age-based and opaque.
– Session Shredder adds behavior-aware rules (pageviews, cart value, bounce flag) on top of age.
– You get a dry-run mode to analyze impact before deleting anything.
– The dashboard gives you visibility into how many sessions were pruned per run and how many sessions remained active.
– WP-CLI commands let you script and automate analyze/prune runs.
– It works alongside WooCommerce experimental guest sessions and HPOS rather than replacing them: Woo can still prune based on its own rules, while Session Shredder adds a tunable, rule-based layer with better reporting.
How It Works
-
Feature collection
– On each page load, Session Shredder tracks session activity:
– Session age (hours since first seen)
– Pageviews count
– Cart value (numeric)
– Whether anything was added to cart
– Geolocation hash (hashed billing/shipping country)
– Simple bounce indicator (single pageview, no cart)
– Features are stored per-session in non-autoloaded options and never include raw session IDs or user identifiers.
-
Rule-based pruning
– An hourly cron ( session_shredder_cron ) scans the WooCommerce session table for candidates based on age.
– For each candidate, the plugin:
– Loads stored features
– Applies conservative rules like:
g. 72 hours)
– Single pageview and no cart value
– If the rules deem the session a low-value “zombie”, it is pruned.
-
Stats & visualization
– After each real run, Session Shredder records:
– Total pruned sessions (lifetime and today)
– A short history of recent runs, including how many sessions were pruned and how many remained active before/after each run
js line graph of active & pruned sessions per run via a secure AJAX endpoint, plus a compact “Recent runs” table.
For developers
Session Shredder exposes a small set of hooks and CLI commands so you can integrate it into more advanced workflows without forking the plugin.
Hooks
– session_shredder_features( array $features, string $session_hash )
– Filter the behavior feature array before it is stored and later used for pruning decisions.
– $session_hash is a hashed identifier of the session (no raw IDs or PII).
– session_shredder_base_age_hours( float $base_age_hours )
– Adjust the base age window (in hours) before sessions are considered as prune candidates.
– session_shredder_should_prune( bool $should_prune, array $features )
– Override or refine the core rule-based decision for a given session.
– session_shredder_feature_options_soft_limit( int $soft_limit )
– Adjust the soft cap for how many per-session feature options ( session_shredder_features_* ) are kept in wp_options before garbage collection trims the oldest entries.
– session_shredder_feature_options_gc_batch( int $batch_size )
– Adjust how many feature options are removed per garbage-collection pass when the soft limit is exceeded. Larger values clean up faster; smaller values spread work over more runs.
– session_shredder_before_run( float $base_age_hours, bool $dry_run )
– Fires before a prune run (cron, manual, or CLI) starts.
– session_shredder_after_run( int $pruned_count, bool $dry_run )
– Fires after a prune run completes (dry-run or real).
– session_shredder_pruned( int $pruned_count )
– Fires after a real prune run that actually deletes sessions; useful for logging or additional cleanup.
WP-CLI commands
If WP-CLI is available, Session Shredder registers the following commands:
– wp session-shredder analyze
– Performs a dry run using the current rules and settings.
– Outputs the total number of sessions and how many would be pruned, without deleting anything.
– wp session-shredder prune
– Runs a real prune using the current rules and settings.
– Deletes matching sessions, updates stats, and logs a summary.