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

Jump to bottom

Server-Side handling of visit-interval, first-visit and previous-visit #7702

Closed
d4rken opened this issue Apr 18, 2015 · 2 comments
Closed

Server-Side handling of visit-interval, first-visit and previous-visit #7702

d4rken opened this issue Apr 18, 2015 · 2 comments
Labels
wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.

Comments

@d4rken
Copy link
Member

d4rken commented Apr 18, 2015

http://developer.piwik.org/api-reference/tracking-api

Why does the Tracker not autonomously fill in "_idvc" (visit count), "_viewts" (previous visit) and "_idts" (first visit)?

The Tracker should have everything necessary to set these values as long as he can uniquely identify the user.

Was this a performance/scalability decision? Or was the idea to allow tracking of these values if the Tracker could not uniquely identify the user?

Also see matomo-org/matomo-sdk-android#18
@mattab
Copy link
Member

mattab commented Apr 20, 2015

Hi @d4rken

In the Javascript client, _idvc, _viewts and _idts are stored in the first party cookie in the visitor browser.

Piwik has the data internally to process the values for those attributes, but technically Piwik cannot process those values in a performance efficient manner (You guessed right that it was performance/scalability reason). To process the values Piwik would need to look back in time for the visits by this visitor and look when was the first visit, how many visits there were, etc. this would be too slow and not scale. for performance reasons we expect the parameters to be set by Tracking API clients (when they can do so)

Hope it helps

@mattab mattab closed this as completed Apr 20, 2015
@mattab mattab added the wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it. label Apr 20, 2015
@d4rken
Copy link
Member Author

d4rken commented Apr 20, 2015

If anyone stumbles across this issue, #4750 is interesting too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mattab @d4rken