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

Client detection #5413

Open
sgiehl opened this issue Jul 4, 2014 · 12 comments

Comments

@sgiehl
Copy link
Member

commented Jul 4, 2014

Currently Piwik is only able to detect browsers.
Instead of detecting only browsers we should open up piwik to client based detection.
Clients can be browsers, as well as media players, mobile apps, personal information managers (like mail clients), feed readers and so on.
The DeviceDetector used by Piwik is already able to detect such clients.
As it is impossible to define short codes for all those possible clients, we might need to move away from only saving short codes (like it is actually done for browsers)

With client based detection there will be more reports possible within Piwik. So it would be nice to see which client types mostly visits a website and os on.

@sgiehl sgiehl added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014

@ThaDafinser

This comment has been minimized.

Copy link
Contributor

commented Jul 29, 2014

@sgiehl i would go further...save all client $_SERVER vars serialized in one field inside piwik_log_visit.
Pro:

  • at an upgrade you can extract them, if other table fields need to be field
  • you can update the short codes or other things at an upgrade

Con:

  • possible overflow (TEXT can be too small....i had it one time as LARGETEXT....)
  • needs a lot of space

@mattab mattab removed the c: Core label Aug 3, 2014

@mattab mattab added this to the Short term milestone Aug 3, 2014

@mattab mattab added the c: Platform label Sep 9, 2014

@mattab

This comment has been minimized.

Copy link
Member

commented Apr 7, 2015

Hi @sgiehl - great idea of a new report for Piwik.

Do you maybe have some idea on approx estimate for this issue?

@sgiehl

This comment has been minimized.

Copy link
Member Author

commented Apr 7, 2015

I think that would take a few days for implementation. We need to built a switch between the different client types and therefor adjust the table structure as we need additional information. Currently all client types other than browser will be reported as "unknown" browser, which will then be excluded from the browser reports. Maybe I can provide a detailed list of todos as soon as I have some time for that.

I would love to see that in the near future!

@mattab mattab modified the milestones: Mid term, Short term Apr 7, 2015

@mattab mattab added duplicate and removed Major labels Dec 5, 2016

@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016

@mattab mattab removed the duplicate label Dec 5, 2016

@mattab mattab added the Major label Feb 28, 2017

@bigretromike

This comment has been minimized.

Copy link

commented May 17, 2017

is near feature now 👍 ?

@bigretromike

This comment has been minimized.

Copy link

commented May 7, 2019

Hello, is there way to help with this ? Maybe sort all ShortCodes for all type of devices ?

@sgiehl

This comment has been minimized.

Copy link
Member Author

commented May 7, 2019

that might require various database changes to be able to store other client types than browsers. Guess such a change won't be doable before the next major release.

@bigretromike

This comment has been minimized.

Copy link

commented May 7, 2019

@bigretromike

This comment has been minimized.

Copy link

commented Jul 25, 2019

Looking thru gh I found: #13929 looks like you started moving from codes to names.
So could I assume the future is closer than it was year ago ?:-)

@mattab

This comment has been minimized.

Copy link
Member

commented Aug 7, 2019

Would it work to simply use different shortcodes for the new clients we want to detect?

@bigretromike

This comment has been minimized.

Copy link

commented Aug 7, 2019

@mattab I does exactly that! But I understand that the issue was that Matomo store '2 char value' and that would go out of stock if used that way for every client.
But as I remember moving from shortcodes to names was one of requirements to add a custom client detection without needing to edit manually detection library to detect other kinds of devices that are not browsers but yet are able to access pages and are excludes from browser raport (ex. media players)

@sgiehl

This comment has been minimized.

Copy link
Member Author

commented Aug 7, 2019

exactly. device detector is for example able to detect names of mobile apps. that can't be be combined with short codes in any way

@bigretromike

This comment has been minimized.

Copy link

commented Aug 7, 2019

that why you need currently overwrite detect library to include those in browser and exclude them from ex. mobile apps - then you are able to measure real traffic and how does it come to you.
And I have fingers cross that we be able to add our 'browsers' or change some settings to include those 'apps/applications/programs' that access our content thru web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.