Fast and lightweight: optimized database queries, no external dependencies, and reliable tracking with server-side caching<\/li>\n<\/ul>\n\nQuantely Analytics itself does not use JavaScript tracking, set cookies, or communicate with external analytics services. It processes data locally from Quantely Activity. Data collection, including optional visitor identification, is handled by Quantely Activity and depends on its configuration.<\/p>\n\n
Privacy<\/h3>\n\n
Quantely Analytics processes analytics data locally within your WordPress installation.<\/p>\n\n
Data stored may include:<\/p>\n\n
\n- Pageviews<\/li>\n
- Sessions<\/li>\n
- Visitor identifiers, depending on Quantely Activity configuration<\/li>\n
- Aggregated traffic statistics<\/li>\n
- Diagnostic information about how analytics data is processed<\/li>\n<\/ul>\n\n
Quantely Analytics does not send analytics data to external services.<\/p>\n\n
Quantely Analytics depends on Quantely Activity for activity collection and optional visitor identification.<\/p>\n\n
Dependencies<\/h3>\n\n
This plugin requires Quantely Activity. Without Quantely Activity, Quantely Analytics cannot record or process activity data.<\/p>\n\n\n
\n- Upload the plugin files to the
\/wp-content\/plugins\/quantely-analytics<\/code> directory, or install the plugin through the WordPress plugins screen.<\/li>\n- Activate the plugin through the Plugins screen.<\/li>\n
- Make sure Quantely Activity is installed and active.<\/li>\n
- Open the Quantely menu in the WordPress admin to view Analytics.<\/li>\n<\/ol>\n\n\n
\nDoes this plugin work without Quantely Activity?<\/h3><\/dt>\nNo. Quantely Analytics depends on Quantely Activity for activity collection. Without Quantely Activity, Quantely Analytics cannot record or process activity data.<\/p><\/dd>\n
Does Quantely Analytics use cookies?<\/h3><\/dt>\nQuantely Analytics itself does not use cookies. Optional visitor identification is handled by Quantely Activity and depends on its configuration.<\/p><\/dd>\n
Does Quantely Analytics use JavaScript tracking?<\/h3><\/dt>\nNo. Quantely Analytics processes activity data server-side from Quantely Activity. It does not add its own JavaScript tracking layer.<\/p><\/dd>\n
Does this plugin send data to external services?<\/h3><\/dt>\nNo. Quantely Analytics does not send analytics data to external services.<\/p><\/dd>\n
Why do I not see visitor statistics?<\/h3><\/dt>\nVisitor statistics require visitor identification in Quantely Activity. This can be based on a visitor cookie or on the configured cookieless fallback. If both are disabled, Quantely Analytics uses actor-key grouping for visitor metrics. These visitor metrics remain available, but should be treated as weak and may closely resemble session metrics.<\/p><\/dd>\n
What kind of statistics does Quantely Analytics provide?<\/h3><\/dt>\nThe first public release focuses on sessions, visitors, engagement, device breakdowns, channel breakdowns, monthly traffic development, and diagnostic insight into how statistics are constructed.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.5<\/h4>\n\n\n- Added Quantely Insights extension visibility in Overview, Diagnostics, and Data settings.<\/li>\n<\/ul>\n\n
1.0.4<\/h4>\n\n\n- Fixed Analytics overview Top 10 pages so it uses core session pageview data and does not depend on the Insights page archive.<\/li>\n
- Added the post-rebuild action hook used by extensions after core session\/pageview rebuilds complete.<\/li>\n
- Improved terminology and notifications.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Renamed Dashboard to Analytics.<\/li>\n
- Renamed Sessions to Assembly.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Tested with WordPress 7.0.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Initial public release<\/li>\n<\/ul>","raw_excerpt":"Lightweight web analytics built entirely inside WordPress.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/312290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=312290"}],"author":[{"embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/erravi"}],"wp:attachment":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=312290"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=312290"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=312290"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=312290"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=312290"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=312290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}