Here’s the breakdown of the process:
- A visitor lands on your website and the browser sends a request to the web server for site loading.
- The web server logs this information in its files.
- These logs are transferred to the Piwik PRO server.
Since web-log analytics is different from the conventional tracking code, the data collected may vary. However, it stands out as a secure choice, especially for businesses handling sensitive data like banks, healthcare or government entities.
Let’s look at the pros:
- No need to install a tracking code on your website. Data-sensitive businesses like banks, healthcare or government entities choose this method to enhance data privacy.
- Tracking blockers don’t affect data collection via web logs.
- You can import historical data anytime; file logs remain on a web server until they are deleted.
On the flip side, here are some cons:
- You need to be technically savvy and have access to the web server to use this method.
- The tracking code can collect more data, such as a page title, screen resolution, custom dimensions, ecommerce data and the like.
- Web logs are for Analytics only; Tag Manager, Consent Manager and Customer Data Platform will not work with this method.
For more about web-log analytics in Piwik PRO, see our developer documentation.