#Overview
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:
#Auto login
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 wpf_contact.
#Lead source tracking
WP Fusion’s lead source tracking uses cookies to keep track of a visitor’s UTM variables and referrer. If the visitor later registers an account or makes a purchase, these values are sent to your CRM along with the contact data.
Because many cache plugins prevent cookies from being set, you’ll need to create a cache exclusion for these cookies. The two cookies are wpf_leadsource and wpf_ref.
#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 wpf_return_to cookie.
#All cookies
A simple solution is to just bypass caching whenever any WP Fusion cookies are set. You can either add a wildcard, like wpf*, or add cache exclusions for 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.
