Considerations for Sending User Properties as JSON Objects

·

I'm planning on sending a user property that's a list of JSON objects; my understanding is that this is supported, but the support is limited. Is there something I need to know before implementing this?

🎫1

2 comments

Thena
APP
·
·
Hi Vlad- Julianne from Mixpanel Support here. The biggest thing to be aware of is that the number of objects analyzed in the list is limited. Projects with fewer than 100 million events per month can include up to 20 objects per list. For projects exceeding this threshold, the system supports only the first 5 objects in each list. Any objects beyond those limits won't be returned during analysis. Nested object values won't be selectable on their own- only the top level will populate in the query builder. I'd recommend sending some test data and ensuring that it works with the questions you're interested in answering!
Vlad S.
·
·
ok, so sending objects in lists should theoretically be fine as long as the lists are not too long (they won't be) and the objects have no nesting (they don't); is there something to be aware for user properties vs. event properties in this format?