If a user’s local machine runs out of RAM overnight and the tab is in the background, then the browser will kill the tab, and if the user comes back to the tab the next day then a pageView event will trigger (and subsequent page ping events)
If a user leaves the page open with focus on the page overnight, then page ping events will continue to trigger; the page will not trigger a new pageView event the next day (since focus will prevent most browsers from killing the page)
Would y’all say those scenarios are accurate (and the complete set of possible scenarios)?
Page ping events should only trigger if there’s activity (e.g., mouse movement, keyboard presses, regaining focus / resizing etc) if there’s activity within that heart beat period or “window of activity” between page pings. If there’s no activity in this period but the window is still in focus page pings shouldn’t fire. If the page isn’t reloaded you should still have the same page view event and the page pings should gracefully resume once the user is back active on the page the next day.