Hi @Cyberway Thank you for the forum post. Taking these in order:
1. Yes, those numeric values are Cursor user IDs. They’re the internal identifier for the account that generated each usage event, so nothing in your export is malformed.
2. Why some rows show an ID instead of an email. The usage export fills in the User column by matching each event’s owner against your team’s current member list at the time you run the export. Events owned by someone who has since left the team, or whose membership record doesn’t resolve cleanly, fall back to the raw ID. That’s why an export can come back with a mix of emails and numbers.
3. Mapping the IDs to people today. There isn’t a place in the dashboard that translates a user ID back to an email or name, so the two practical options are:
The quickest way to get emails on every row is the Admin API: create a key at cursor.com/dashboard under API Keys, then call `POST /teams/filtered-usage-events`, which returns a `userEmail` field on each event, including for members who have left. Details and a sample request here: Admin API | Cursor Docs
Otherwise, email [email protected] with the date range and the specific numeric IDs you need resolved, and we can send back the matching emails directly.
I tried contacting [email protected], but the response I received was from an AI assistant. I also provided the numeric ID, but it did not solve my problem.
It replied by suggesting that I use /teams/filtered-usage-events, but after trying to export the data, I found that the exported data does not include the numeric ID.