I didn't say a string array attribute, though you could copy-paste that into a text editor or any number of other ways to read the whole thing. Is it three, five, ten strings? OP has a vague problem so I gave a general alternative.

But I was actually thinking you could store the individual strings by indexing with either the point or prim number. Who knows if the OP's geometry can cover the length of the array though. But if that's the case then it doesn't require building secondary geometry streams...though, making an asset that does exactly this, for array value evaluation, isn't the worst idea if your workflow has you constantly building and sorting these.