UTM Parameters not captured

  • Resolved Johan Stam

    (@johan-stam)


    1 month, 1 week ago

    We have an issue where the parameter values are captured nicely in a cookie and the value is also there when surfing to another url, but the value is not populated the hidden fields in the Gravity Form. When the url with the form is approached directly the values are populated in the form as you would suspect. So I think the form loads first and the handl utm grabber is to late to fill the hidden fields with the values. We’re using kinsta cache. Is this solvable?

    • This topic was modified 1 month, 1 week ago by Johan Stam.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Johan Stam

    (@johan-stam)

    Found in your docs how to whitelist query args and cookies if hosted by Kinsta. Seems ok now.

    Plugin Author Haktan Suren

    (@haktansuren)

    Thanks for the update @johan-stam

    If you are using the free version, this is right fix. But if you are on V3, you did not have to add the query args as exlucsions. It should have worked out of the box. Let me know please.

    Thread Starter Johan Stam

    (@johan-stam)

    I just want to add that whitelisting didn’t worked for us. It only works when the url is approached directly. If the landingspage is not the same as the actual form page you need to exclude the form page from the cache, otherwise the form page is served from the cache and the hidden fields will nog get filled with the UTM values. Our sites are hosted at Kinsta, but can imagine that this counts for more hosts with server caching in place.

    Plugin Author Haktan Suren

    (@haktansuren)

    Thanks for the more detail @johan-stam

    Are you using HandL UTM Grabber V2 (this version) or premium?

    Thread Starter Johan Stam

    (@johan-stam)

    We’re using the free version of your plugin.

    Plugin Author Haktan Suren

    (@haktansuren)

    The free version has a known issue with caching sites because it does not utilize client-side tracking. Consider upgrading to the paid version to resolve this issue.

    Thread Starter Johan Stam

    (@johan-stam)

    Think I stick to my own solution to get the values in.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.