Kinsta is my webhost
If you are on Kinsta, you need to contact Kinsta support and let them know that you want to whitelist the following QUERY ARGS & COOKIES to prevent caching.
utm_campaign
utm_source
utm_term
utm_medium
utm_content
gclid
first_utm_campaign
first_utm_source
first_utm_term
first_utm_medium
first_utm_content
handl_original_ref
handl_landing_page
handl_ip
handl_ref
handl_url
organic_source
gaclientid
HandLtestDomainName
//and all the custom parameters created by you
QUERY ARGS
utm_campaign
utm_source
utm_term
utm_medium
utm_content
gclid
//and all the custom queries you are capturing
Usually, this process takes couple of hours to complete. Hoever, you may want to wait longer for changes to completely take effect.
Still having problems? Let us know, clicking the chat bubble at the bottom right of the page.
Customer Provided Feedback
"I have found that the guide you have about Kinsta and the custom cache rules where we need to ask Kinsta to implement specific rules to let Handl work, are not enough. I'm sharing with you a screenshot from the Kinsta dashboard which shows that Kinsta Edge Caching (saving HTML on Cloudflare Edge PoPs) is not compatible with custom cache rules, and thus Handl customers with Kinsta should also turn off Edge Caching. It's logical since Handl rewrites HTML based on query parameters and custom cookies and the HTML in Cloudflare edge are static and not even triggering the HandL plugin."
This feedback was provided by a customer and included in our documentation as is.