The interaction.id provided by Datasift is a 32 character hex string that looks like a UUID. However, in thousands of consecutive messages, the first four hex digits are 1e2e, and about a third of messages have a common fifth character. In addition, many other interaction.id start with 1e2f. A UUID is guaranteed to have 122 bits at random according to my research, meaning that one and a half hex characters might not be at random. Thus, your interaction.id does not appear to conform to the requirements of the ISO standard for UUIDs.
We have already collected a lot of data from Datasift and we have read a lot of your documentation online. I’m not clear that your interaction.id is intended to be different from the ISO-specified UUID, or if so what your interaction.id is, what standard it conforms to, and how it is constructed. I’d like to find out that my understanding of UUIDs is wrong, and I realize Datasift is a major data provider. Could you please clarify on this point? Thank you.