Bug - Custom JS function variable returning false returns to empty string

[luukfiets]

Hi,

While setting up tracking for a client we've noticed that custom JS function variables returning false result in an empty string while a JS function variable returning true returns the actual boolean value true. The variables are set up like this:

The result in the debug mode:

I would expect the boolean false to return false instead of an empty string

[saranogueiraa]

We recommend to use "false" instead of false.
If you check the Marketing Consent variable, the value "false" appears as the value is currently being converted using .toString().

[luukfiets]

@saranogueiraa, currently I'm converting them with .toString() indeed, but it's hard to debug the issue if this only happens when the variable returns false and not if the variable returns true. A simple warning in the documentation OR an automatic conversion from a boolean value to the string value would be very helpful.