Community members discuss an issue where URL parameters (specifically UTM variables) in Typebot are being erased or emptied after being initially set. The variables appear to work momentarily but then become empty, even though they're being passed correctly in the URL.
One community member discovered that variables need to be not just used but explicitly read in the flow to persist. As a workaround, they suggested adding a script that accesses these variables to prevent them from being erased. The issue appears to be inconsistent, with some users unable to reproduce it on the main Typebot.io instance, while others experience it on self-hosted instances.
Another community member confirmed experiencing the same issue with a UTM variable named "hostname", noting that it worked previously (as of February 12th) but stopped working unexpectedly. They confirmed that the script workaround resolved the issue, and interestingly, the fix persisted even after removing the workaround script.
Here: First I ran with the flow connected to the first block and called url?utm=A Then I ran with the flow connected to the second block and called url?utm=B Results:
Actually looks like the variable must be not just used, but read. I say that because this variable was used, never read, and is also empty in the results page:
Hey @Baptiste, I ran into this exact same issue. Oddly enough, this was working fine for me the last time I tested it on February 12th and there has been no changes to the typebot since before that date. But I was just doing some final testing as we are about to go live and sure enough, the UTM variable I'm using (hostname) is empty now. Using the script workaround provided here has resolved it for me. Of note, I removed the script workaround and it continued to work. Very strange.
