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

Cache/CDN Interference With Tracking

Troubleshooting / Performance

Clicks or redirects behave inconsistently after cache/CDN changes.


Where to Check in PassiveWP

WordPress Admin -> PassiveWP

Step-by-Step Fix Walkthrough

Fix Step 1: Exclude branded link and tracking paths from full-page cache.

Where to click WordPress AdminPassiveWP

What to do In WordPress AdminPassiveWP, do this in order: open the relevant panel, find the control related to "Exclude branded link and tracking paths from full-page cache.", apply one change, click Save/Run, then reload once to confirm it stuck.

How to verify Test clicks should land on the expected destination with attribution parameters intact.

Fix Step 2: Purge CDN cache after major tracking config updates.

Where to click WordPress AdminPassiveWP

What to do In WordPress AdminPassiveWP, do this in order: open the relevant panel, find the control related to "Purge CDN cache after major tracking config updates.", 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 3: Verify query parameters survive end-to-end redirects.

Where to click WordPress AdminPassiveWP

What to do In WordPress AdminPassiveWP, do this in order: open the relevant panel, find the control related to "Verify query parameters survive end-to-end redirects.", apply one change, click Save/Run, then reload once to confirm it stuck.

How to verify Test clicks should land on the expected destination with attribution parameters intact.

Fix Step 4: Retest using uncached/private sessions.

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.

Most Common Causes

  • Aggressive caching of dynamic redirect/tracking paths.
  • Cached pages serving stale scripts or link behavior.
  • Edge rules rewriting query parameters.

How to Prevent It Next Time

  • Document cache exclusions for monetization paths.
  • Run click/conversion QA after CDN config changes.
  • Avoid edge rewrites that mutate attribution params.

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?