Re: Inflated pageview numbers from repeated (not intentionally refreshed) pageviews

Thanks for the swift reply!

I was afraid of that. I'm not too familiar with the live server setup and asking for web logs is rather painful (and I probably can't reveal too much details with the implementations). From what I have seen of the web logs multiple requests have been fired, coinciding with the visitor logs.

Mainly, I was interested if anyone had found similar issues - and if there was a work around. As it affects mainly Safari users, it seems to be an browser issue. With a range of third-party scripts on the page I'm starting to edge towards the hunch that some 'inbetween-state' causes the browser to refresh (for a different case of unexpected refreshes: I found that empty img tags can cause duplicate requests).

I am pushing for the use of the latest _paq method, though it would be good if it also magically solved this issue.

Edit: I've considered using the heartbeat, but I have been expressly been instructed to *avoid* extra requests.. bleeeh
Also, I wondered if I store a custom variable on user interaction (scroll, focus, mouse, etc) so it can flag that on exit that a pageview was not 'interactive enough'.. Not sure how/if it can be done