10-07-2013, 10:47 PM
We're using the window.onLoad event to trigger our window.performance.timing.* collection beacon, and that's been working really well for us.
We're venturing into deeper territory for our RUM data to capture details from the window.performance.getEntries().* interface. To date, we've done this with an offset beyond the loadEventEnd. However, we want to get a more complete view of resources delivered to our customers, so we _also_ want to fire a beacon on the unLoad event for the page.
I understand that doing "first-view-only" tests wouldn't trigger this behavior. However, I've run a couple of samples with the repeat first and second view option enabled and I'm not seeing the request triggered.
Is that expected behavior?
We're venturing into deeper territory for our RUM data to capture details from the window.performance.getEntries().* interface. To date, we've done this with an offset beyond the loadEventEnd. However, we want to get a more complete view of resources delivered to our customers, so we _also_ want to fire a beacon on the unLoad event for the page.
I understand that doing "first-view-only" tests wouldn't trigger this behavior. However, I've run a couple of samples with the repeat first and second view option enabled and I'm not seeing the request triggered.
Is that expected behavior?