Byte size of numeric custom parameters in UGS Analytics

UGS Analytics custom parameters may be ints and floats, but the docs don’t seem specify their actual precision in bits. Are these 32- or 64-bit values? Thanks in advance!

Hey @jeffomatic

The platform should behave just fine with 64-bit values passed through in custom parameters.

I’m interested to hear what your use-case is and what your concerns are?

Thanks for the response!

The context is that I’m thinking about sending some memory usage telemetry via an int field, and was wondering whether byte-level precision was sufficient. A signed 32-bit int would give you the ability to report ~2GB, but if you wanted more headroom, you’d either need 64 bits or a lower resolution, e.g. KBs or MBs. Sounds like I’m fine doing bytes.