Adding a First Time Filter to Data Exports

Vlad S. · 2025-10-01T21:23:40.451Z

additionally, is there a way to add a "first time" filter to exports? I really just need one event per user for my use case, but I'm not sure how to achieve that with selectors

10 comments

· Sorted by Oldest

Julianne Bozzini
APP
·
·
Hey Vlad- Julianne from Mixpanel Support here! Unfortunately, there isn't a way to add a "first time filter" or its equivalent with the Raw Export API. What question are you trying to answer with the one event per user? It may be possible to get the info with one of the other APIs.
Vlad S.
·
·
we had an implementation bug where we weren't calling identify properly on a subset of users, meaning that the events of those sessions were recorded as anonymous, and not properly connected to their user profile; however, some of those events held enough information in their properties for us to determine who the user was, and retroactively identify them... we really needed only one such event per anonymous id; instead we ended up downloading all those events, which were quite numerous, and then filtering them down to one on our end
Vlad S.
·
·
I thought that, since "first time" is an option in the UI, it would also be an option in the API
Vlad S.
·
·
ideally, there would be an API endpoint that would have the same functionality as the "events" tab and the associated filters, although maybe those are not implemented using an API call but a mixture of API and client-side filtering?
Julianne Bozzini
APP
·
·
That makes sense! If you're able to create an Insight report of the users (ie based on a cohort definition or other identifying feature) then you could use the Query API to export just the relevant info.
Vlad S.
·
·
it was about 12k users, would I be able to show that many categories in an insights report?
Vlad S.
·
·
in any case, I did what I needed, I managed to filter the events down to something around 200k events, download them all, extract the anonymous ids and user ids from them, and send the approximately 12k identify events needed
Julianne Bozzini
APP
·
·
Glad you were able to get it working! In case you run into a similar issue again, the Query API is currently limited to 10k segments, but you can download a CSV of up to 50k segments from the report itself through the UI.
🤔1
Vlad S.
·
·
oh I think that would have worked, thanks!
Vlad S.
·
·
(although having written the export/transform/load scripts I now can use them for some other data repair tasks I've been putting off)
🙌1

Julianne Bozzini
APP
·
·
Hey Vlad- Julianne from Mixpanel Support here! Unfortunately, there isn't a way to add a "first time filter" or its equivalent with the Raw Export API. What question are you trying to answer with the one event per user? It may be possible to get the info with one of the other APIs.
Vlad S.
·
·
we had an implementation bug where we weren't calling identify properly on a subset of users, meaning that the events of those sessions were recorded as anonymous, and not properly connected to their user profile; however, some of those events held enough information in their properties for us to determine who the user was, and retroactively identify them... we really needed only one such event per anonymous id; instead we ended up downloading all those events, which were quite numerous, and then filtering them down to one on our end
Vlad S.
·
·
I thought that, since "first time" is an option in the UI, it would also be an option in the API
Vlad S.
·
·
ideally, there would be an API endpoint that would have the same functionality as the "events" tab and the associated filters, although maybe those are not implemented using an API call but a mixture of API and client-side filtering?
Julianne Bozzini
APP
·
·
That makes sense! If you're able to create an Insight report of the users (ie based on a cohort definition or other identifying feature) then you could use the Query API to export just the relevant info.
Vlad S.
·
·
it was about 12k users, would I be able to show that many categories in an insights report?
Vlad S.
·
·
in any case, I did what I needed, I managed to filter the events down to something around 200k events, download them all, extract the anonymous ids and user ids from them, and send the approximately 12k identify events needed
Julianne Bozzini
APP
·
·
Glad you were able to get it working! In case you run into a similar issue again, the Query API is currently limited to 10k segments, but you can download a CSV of up to 50k segments from the report itself through the UI.
🤔1
Vlad S.
·
·
oh I think that would have worked, thanks!
Vlad S.
·
·
(although having written the export/transform/load scripts I now can use them for some other data repair tasks I've been putting off)
🙌1