Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HeartBeatTimer / visit length stopped on page (not website) by firing event #14243

Closed
crnm21 opened this issue Mar 20, 2019 · 1 comment
Closed
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@crnm21
Copy link

crnm21 commented Mar 20, 2019

By my observations the HeartBeatTimer stops updating the visit length for a webpage if an event is tracked but continues to update the visit length for the overall visit (and by that, the website).

Minimum setup to reproduce this:

Load a js tracker with heartbeattimer option for a page.
Fire event for this page by js event tracking.
Wait 30 seconds with active tab.

Result:
Event is tracked.
Visit length for the page is 0 seconds.
Visit length for website/session is 30 seconds.

Expected result:
Event is tracked.
Visit length for the page is 30 seconds.
Visit length for website/session is 30 seconds.

Refiring the HeartBeatTimer after firing the event does not help (I tried this already).

@tsteur
Copy link
Member

tsteur commented Mar 20, 2019

That's expected behaviour at the moment (not saying it's the best). See eg #9539 and #9540

@tsteur tsteur closed this as completed Mar 20, 2019
@tsteur tsteur added the duplicate For issues that already existed in our issue tracker and were reported previously. label Mar 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

2 participants