Share feedback, ideas and get community help

Updated 3 months ago

What may cause the GET variable not to be set?

I'm following this instructions:
Attachment
image.png
1
V
B
M
27 comments
The variable utm_source exists.
I'm passing it by calling url?utm_source=value
I've tried with an without a disconnected block that uses them.
I just realised that it is set for a brief moment, them it's set to empty.
Attachment
image.png
I'm not setting it anywhere in the flow.
Hmm can't reproduce!
Let me isolate the problem.
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:
Attachment
image.png
Looks like Typebot is erasing variables not deliberately used in the flow.
For now I'll add a script that does nothing, just access those variables.
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:
Attachment
image.png
I just can't reproduce what you describe
Appreciate if you can provide a reproduction or even a video recording 🙏
I think your problem ins on Remember user
Attachment
image.png
Hmm no I don't think so as it would overwrite the existing result
Can't reproduce it at app.typebot.io
Only at my own instance (that is juts 11 commits behind)
I'll update it.
An update didn't help.
Not sure that is happening.
An example:
Attachment
image.png
In this case "caminho" must be "A" or "B", there's no other option.
Nevertheless, the result is empty.
To "solve" this I'm calling a script like this after each user iteration:
Attachment
image.png
That's very strange! 🤔
I really don't know what's going on
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.
Add a reply
Sign up and join the conversation on Discord