build js

Wondering if it maybe would make sense to automatically reset that limit after a day or something like this. There might be other tracking cases for single page applications that are actually almost never be reloaded, like order terminals for anything

@sgiehl that's what we're trying to prevent though that they keep sending requests still after 1 day etc when there's no pagereload etc. I think in this case they could maybe set a higher limit or disable this functionality with -1 (added this feature).

I would say we could reset the counter on setVisitorId (this would maybe restore old behaviour in very few cases but not in SPA), or we could reset it when trackPageView is called and the URL is different compared to last time (but this would kind of prevent the feature from working where there is a bug so could almost just as well not merge the feature as it would only add complexity plus this behaviour be hard to document and explain).

I reckon 10K req even for a SPA is quite a bit and not that easily reached. Could also set it to 20K by default if that helps.

build js

@tsteur that was just a random thought. Guess support for -1 should be enough

Actually after thinking for 30 min about it I'm closing this PR for now. If we start resetting counter after certain time or actions things become less predictable and hard to explain/document/reproduce and it's not usable. The only nice way would be to have this in default tracking code where besides trackPageView we also have a setMax...(10000) but this bloats the embed tracking code for maybe a small problem. Generally it be hard to find for some users there is such a limit etc.