Vlad S.

I don't like this behavior, I've run into it several times, and it always ends up sending me on a lengthy workaround that could be easily avoided if the exposed API matched the internal one (whatever is used by the UI)

it's the same with the event export API: in the interface, you can list columns that are user properties (like the email) and export them to CSV (you can also use them to filter your output) but when you use the API you need to make a separate call to get the user property...

I think this is expected... the first event time is a property calculated from events, so it involves a join with the events collection, which the API doesn't do

I don't know about images, but everything we render inside a canvas in our app doesn't get captured... I don't think it's surprising, since it would probably take a lot more effort to capture all such edge cases and make sure they work correctly

but that's a good idea... it doesn't fully account for the "started job a" -> "completed job b" scenario, but it's close

How many times does an average user do this event?

it's a very long tailed distribution... the average is probably once per week, with a LOT of users not doing it ever and several doing it hundred times a day

might just need to download all the events and parse them offline