Log analytics, one of the earliest methods for server-side tracking, involves analyzing log data from your website. By using specialized software, you can import server-side logs from your web server to retrieve records that match specific criteria, helping you identify trends and analyze patterns in user behavior.
However, the information collected through server logs is more limited compared to client-side JavaScript data. Server logs don’t capture details like browser plugins, screen resolutions, or page titles, which can be valuable for analysis. Additionally, identifying visitors is more challenging because server logs don’t store information about cookies set in the user’s browser.
Lastly, maintaining log analytics is more difficult compared to newer methods like client-side and server-side tracking. Because of these challenges, log analytics is typically used by institutions that, for various reasons, cannot utilize the more convenient tracking technologies.
To learn more about data tracking methods in analytics, read this post: Server-side tracking and server-side tagging: The complete guide.
Log analytics
-

Privacy by design in practice: How “just enough” data beats “just in case” collection
While collecting more data “just in case” feels safer, according to Matt Gershoff, it’s also one of the biggest sources of unnecessary compliance risk, analytical noise, and wasted organizational resources in the analytics industry today. His approach of “just enough” data collection is more intentional, more aligned with privacy regulation, and often more analytically effective.
-

4 ways to make your analytics HIPAA-compliant: Implementation guide
Healthcare organizations have four main approaches to achieving HIPAA-compliant analytics. Each has different trade-offs in cost, technical complexity, and analytics capabilities. This guide compares all four implementation methods – from using Google Analytics with workarounds to deploying fully HIPAA-compliant analytics platforms – so you can choose the right approach for your organization’s needs and resources.
Other definitions
Recent posts from Piwik PRO blog
- Privacy by design in practice: How “just enough” data beats “just in case” collection
- 4 ways to make your analytics HIPAA-compliant: Implementation guide
- Is Google Analytics HIPAA-compliant?
- HIPAA-compliant marketing & advertising: How to run compliant campaigns in healthcare
- PHI vs PII in HIPAA: Healthcare marketing compliance guide
- Piwik PRO recognized as the Emerging Partner of the Year by Acquia
- How can healthcare organizations benefit from using a customer data platform (CDP)
- Banking website analytics for financial services: Tracking without compromising customer trust