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

Delayed Javascript execution #120

Open
Zodiac1978 opened this issue Jan 1, 2019 · 2 comments
Open

Delayed Javascript execution #120

Zodiac1978 opened this issue Jan 1, 2019 · 2 comments

Comments

@Zodiac1978
Copy link
Member

Reported via Twitter: https://twitter.com/e_demonki/status/1050707047057158149

ich lasse das Script von Statify erst laufen nachdem gescrollt und 10 wahlweise 30 Sekunden vergangen sind. So weiß ich, dass auch ein bisschen gelesen wurde... :)

Is this something we should explore?

@stklcode
Copy link
Contributor

stklcode commented Jan 2, 2019

For JS tracking a delay would be easy to add, just another parameter to the JS arguments and wrap the call into a setTimeout block.
Adding a "scroll" event listener is not much magic either.
So far for the technical point...

Timeout seems legit to me. It adds another filtering layer for "real" users (assuming bots don't stay on a single page for 10s) and potentially removes manual search or skimming. Might be worth the effort.

For scroll-detection however I'm not convinced. Not applicatble for short pages (while "short" potentially means a whole lot of text on reasonably sized desktop monitors).

Finally if both would be added, there must be a clear decision when to track. After scrolling OR or AND timeout? Is scroll-detection without timeout a reasonable use-case?

@patrickrobrecht
Copy link
Member

+1 for the timeout - that's something which we can make configurable (default set to 0 for backwards compatibility).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants