Troubleshooting Exporting Events with Undefined User Emails in Mixpanel

speaking of exporting events, I'm looking at exporting events where the user's email is not defined and I tried the following selector strings:

not defined(user["$email"])

and

user["$email"] == undefined

but they both result in HTTP 400 Error: Bad Request Similar requests work if I replace user with properties. Am I reading the docs wrong or something? https://developer.mixpanel.com/reference/segmentation-expressions

8 comments

· Sorted by Oldest

Vlad S.
·
·
the response body is empty, btw
Vlad S.
·
·
I also tried:
not(user["$email"])
and
not(boolean(user["$email"]))
with the same result (and empty error message)
Vlad S.
·
·
is the only supported use case of the user keyword equality?
Vlad S.
·
·
also, the API docs say there's an export limit of 100000 events per request, but I got a response of >250k events in my first test, and it's making me wonder if the documentation might be out of date
Santi (.
·
·
the RAW export api only looks at properties of events so you cannot use "user[]" you need to use properties[]. This is because this API is only reading the RAW stored events that contains event properties. User properties are a different model. The segmentation expressions doc is a general one for expressions (not specifically for raw export)

the 100K limit only applies IF you use the “limit” parameter. You cannot provide a value higher than 100K for "limit". But if you do not specify a limit parameter, the API will return any number of events (unlimited) as long as the request does not time out and your destination can handle the data.
Vlad S.
·
·
the RAW export api only looks at properties of events so you cannot use "user[]" you need to use properties[].
the docs literally show an example using user["$email"] == "someone@somewhere.com"
Santi (.
·
·
can you share a link the docs showing the example? I would love to review it
Vlad S.
·
·
yep, here it is https://developer.mixpanel.com/reference/segmentation-expressions the user portion only appears in the examples table and that's that, no other explanation