PassiveWP logo
Help CenterTroubleshooting / Performance

PassiveWP Help Center

Find setup guides, troubleshooting steps, and execution playbooks so you can get unstuck quickly.

Ctrl/Cmd + K

Database Growth Is Faster Than Expected

Troubleshooting / Performance

Database size increases quickly after tracking and automation scale up.


Where to Check in PassiveWP

WordPress Admin -> PassiveWP

Step-by-Step Fix Walkthrough

Fix Step 1: Review retention and cleanup strategy for old analytics data.

Where to click WordPress AdminPassiveWP

What to do In WordPress AdminPassiveWP, do this in order: open the relevant panel, find the control related to "Review retention and cleanup strategy for old analytics data.", apply one change, click Save/Run, then reload once to confirm it stuck.

How to verify No blocking error banner appears, and the next step is available.

Fix Step 2: Limit unnecessary test traffic in production.

Where to click WordPress AdminPassiveWP

What to do Open WordPress AdminPassiveWP, click the test/validate action in that screen, and wait for the result notice before continuing.

How to verify You should see a Connected/Success result with no red error notice.

Fix Step 3: Archive historical reports externally if needed.

Where to click WordPress AdminPassiveWP

What to do In WordPress AdminPassiveWP, do this in order: open the relevant panel, find the control related to "Archive historical reports externally if needed.", apply one change, click Save/Run, then reload once to confirm it stuck.

How to verify No blocking error banner appears, and the next step is available.

Fix Step 4: Coordinate with hosting on database optimization.

Where to click WordPress AdminPassiveWP

What to do In WordPress AdminPassiveWP, do this in order: open the relevant panel, find the control related to "Coordinate with hosting on database optimization.", apply one change, click Save/Run, then reload once to confirm it stuck.

How to verify No blocking error banner appears, and the next step is available.

Most Common Causes

  • High click volume and conversion logging.
  • Long retention windows without cleanup routines.
  • Frequent test events in staging/production mix.

How to Prevent It Next Time

  • Define data retention policy early.
  • Separate staging from production tracking where possible.
  • Monitor table growth monthly.

When to Contact Support

  • You completed every fix step and still get the same error.
  • The issue impacts revenue-critical pages or high-volume campaigns.
  • You can share timestamps, affected link/product IDs, and screenshots of the exact error state.

Was this article helpful?