We have several forms on our site and want to pass UTM from page to page. We are using Handl Grabber to store the cookies but it seems the aggressive caching (Kinsta nginx) is not working (we get visitors presenting cookies from our testing, for example). We’ve turned off caching now for any pages with UTM cookies, but that’s not practical.
I see the gform_field_value_parameter_name method to populate a filed with a cookie, but will this work client side and avoid this caching problem?
I can do a simple script to inject the parameters into a query string in all HREFs (this almost serves the analytics team’s needs but falls short of their GA Goals needs) except it won’t work on the Submit button (hence my hope I can get a hidden field to populate on the client side).
Hey, James. Thanks, this is interesting. Since our visitors are not logged in, and this happens in $_SESSION, that’s on the server side, yes? And so subject to page caching? (as you can tell, I’m pretty lost with what’s cached on the server side for anonymous users).
and that triggers the fresh render of the hidden field for our cookie value, which we then pass along in the Gravity Form (and possibly also to the Confirmation page URL through GF’s add query string function.
Hi Cala, if everything else is working and you just want to bust the cache for this form, try this plugin:
We (Gravity Wiz) have published an alternate solution to this here that allows you to just exclude the form from the page cache without disabling the entire page cache. With that said, Fresh Forms is still the preferred solution if performance is not an issue.