WP Fusion generally works well with caching and cache plugins, because most of its functionality is tied to logged in users, and logged in users (normally) aren’t cached. But there are some exceptions:
If you’re using auto-login links to unlock content for contacts who follow a tracking link, you’ll need to make sure that any dynamic pages are excluded from caching. Or you can create a cache rule to bypass caching when the auto-login cookie is set. That cookie is named
Lead source tracking
Because many cache plugins prevent cookies from being set, you’ll need to create a cache exclusion for these cookies. The two cookies are
Return after login
WP Fusion includes a setting that can track when a user gets redirected away from a restricted page, and redirect them back to that page after they’ve logged in.
To do that it sets a cookie, which can be blocked by caching. If you have trouble with Return After Login, try adding a cache exclusion for the
To be safe, a good rule is to put in a cache exclusion for any WP Fusion cookies.
You can either add a wildcard, like
wpf*, or add them one by one:
wpf_contact: Used with auto-login.
wpf_guest: Used with identifying guest form submissions to the tracking scripts.
wpf_leadsource: Used with lead source tracking.
wpf_ref: Used with lead source tracking.
wpf_return_to: Used with return after login.
wpfrc: Used with abandoned cart recovery.