If you have a caching plugin/system enabled on your site, you will need to do a few things to ensure Groundhogg works properly.
Sometimes caching systems will cache cookies.
You will need to exclude the following cookies from Groundhogg.
groundhogg-tracking gh-referrer gh-form-impressions gh_contact_tab
Exclude REST API
Groundhogg uses the REST API for many things, and it will use it even more in 3.0, so it is important to ensure that results from the API are not cached.
The route which must be excluded is:
Exclude The Managed Page
Groundhogg uses something called the “Managed Page” to show contact areas of Groundhogg that can’t be edited.
These pages are managed in Groundhogg.
- Email Preferences page
- Unsubscribed page
- Email confirmed paged
- Email browser view
- Hosted form page
- Tracking links
And need to be excluded as they use dynamic content to show personal information to your contacts.
Most caching systems have the option to EXCLUDE a URL. Groundhogg uses a specific URL structure for the managed pages, so you only have to exclude one rule.
/gh/(.*) /gh-cron.php /aws-cron.php
Exclude the following in CometCache
^/gh/ ^/gh-cron.php ^/aws-cron.php
W3 Total Cache
Exclude the following in W3
Using SiteGround? Exclude the following.
/gh/* /gh* /aws*
Go to your LiteSpeed settings, find the excludes tab and add the following.
/gh /gh-cron.php /aws-cron.php
Known Redis Conflict
If you are on GridPane or any other server that implements Redis Caching, you may need to request that this caching protocol be turned off on your server. A known compatibility issue will cause the
gh-cron.php to fire but have no trigger action, causing your funnel steps to remain in the "running now" status.