Page_id crosses sessions and over inflates time

[kfitzpatrick]

Hey @Colm

I did this back at the start, so don’t get individual pings, only aggregate on the unload event. So using pings for engagement does work but only if I get the unload event, which then had me go look for the max event derived_tstamp to figure it out. So the game example would apply if I don’t get the unload of the ping.

@Colm

If you want to use absolute difference between timestamps though, I think it’s still workable, you just have to aggregate by session ID as well as page view ID, and then also use session_id later when you join.

This is probably the solution we’ll go for or I might undo ping aggregation, but I need to look at the impact.