-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Mobile Analytics #1274
Comments
Steve Kamerman's plugin for Piwik using Tera-WURFL: http://github.com/kamermans/MobileAnalytics/ |
ZendFramework 1.11.0 added Zend_Http_UserAgent with adapters for the WURFL (Wireless Universal Resource File) API, Tera-WURFL, and DeviceAtlas. |
This plug-in needs to be extended with mobile carrier reporting (recognized by either IP range or URI parameter, etc.) |
eistrati: that's part of #1823 ... possibly using something like ip2location.com's db19. |
vipsoft: No, I mean the carrier identification based, whenever is possible. Read this thread for example... http://mobiforge.com/forum/designing/mobile-web-design/carrier-ip-addresses |
vipsoft: Ah, I see now... ip2location.com offers identification based on IP address, while I was also referring to carrier's HTTP headers that are passed in WAP. So, the more complex is carrier identification, the better, but my point was that it's currently missing in this plug-in and needs to be extended. Thoughts? |
eistrati: the gurfl database (linked to in that article) is dead; I'm not aware of any open source alternative as for carrier identification using carrier-specific http headers... this is non-standard between carriers, and with increasing privacy concerns, may prove to be a diminishing source of data in the future. Are you aware of any existing code/databases that we can leverage? otherwise I think the amount of research and data collection required might be out of the project's scope |
vipsoft: I'm made some improvements to the way how mobile users are calculated as unique visitors that I really think you should update with your core functionality. Email me to eugen AT kargo DOT com and I'll send you details. |
eistrati, can you please explain quickly here what your modifications are? Do they improve how Piwik works, or how the Mobile Analytics plugin http://github.com/kamermans/MobileAnalytics/ work? |
matt: I got eistrati's email; the change is somewhat mobile-specific -- it adds mobile-carrier specific http headers to the browser config hash; I'll attach it to this ticket when I get to a desktop; I'm thinking it would be better to implement it within this plugin via a new tracker hook |
yes I agree, anything mobile specific would be better as new hook with the logic in the Mobile plugin. |
I installed this plugin with Piwik 1.8.4. When Setting-> Mobile Analytics tab. I am getting this error. If any one make it this plugin work for 1.8.4. Please do let us know the steps. Thanks in advance. Backtrace: |
Moving out of plugins until it can be fixed. |
more detailed user agent parsing: manufacturer / device / operating system (eg iPhone, iPod, iPad; Android - HTC Dream, Droid, Nexus One; Palm Pre, Pixi) is now done! See the DeviceDetection plugin. we have released the project as open source project: https://github.com/piwik/device-detector |
Mobile Analytics
Segments visitors using mobile devices, or devices on wireless networks
Provide additional reports:
Increase perceived tracker responsiveness #1320 is nice-to-have because mobile users may experience more latency (or perceived delays) due to wireless network, device constraints (e.g., cpu, memory, OS, browser), middleware, ...
The text was updated successfully, but these errors were encountered: